linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: "Modi, Geet" <geet.modi@ti.com>
Cc: "Nagalla, Hari" <hnagalla@ti.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Sharma, Vikram" <vikram.sharma@ti.com>,
	"Strashko, Grygorii" <grygorii.strashko@ti.com>
Subject: Re: [EXTERNAL] Re: [PATCH net-next] net: phy: add support for TI DP83561-SP phy
Date: Tue, 16 Nov 2021 17:14:49 +0100	[thread overview]
Message-ID: <YZPY+WSLVcTtkDwm@lunn.ch> (raw)
In-Reply-To: <722B4304-CE9B-436C-A157-48007D289956@ti.com>

On Tue, Nov 16, 2021 at 03:58:27PM +0000, Modi, Geet wrote:
> Hello Andrew,
> 
>  
> 
> We being Texas Instruments are conservative and don't promote meaningless
> marketing as well. Please note DP83561-SP is a Radiation Hardened Space Grade
> Gigabit PHY. It has been tested for Single Event Latch up upto 121 MeV, the
> critical reliability parameter Space Designs look for.

That statement i have no problems with, it is clearly factual.

> The dp83561-sp is a high reliability gigabit ethernet PHY designed

is clearly Marketing, who would design a low reliability gigabit
ethernet PHY? It is meaningless.

So please use your text from above in the commit message, it nicely
describes what this PHY is in engineering terms.

   Andrew

  parent reply	other threads:[~2021-11-16 16:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 10:20 [PATCH net-next] net: phy: add support for TI DP83561-SP phy hnagalla
2021-11-16 13:53 ` Andrew Lunn
     [not found]   ` <722B4304-CE9B-436C-A157-48007D289956@ti.com>
2021-11-16 16:14     ` Andrew Lunn [this message]
2021-11-16 17:26       ` [EXTERNAL] Re: [EXTERNAL] " Modi, Geet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YZPY+WSLVcTtkDwm@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=geet.modi@ti.com \
    --cc=grygorii.strashko@ti.com \
    --cc=hnagalla@ti.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vikram.sharma@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).