linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: Florian Fainelli <f.fainelli@gmail.com>, Andrew Lunn <andrew@lunn.ch>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [RFC PATCH 1/3] net: phy: at803x: fix Kconfig description
Date: Thu, 31 Oct 2019 01:05:50 +0100	[thread overview]
Message-ID: <D615CB94-38A8-44E2-99CB-00FB1737FC5E@walle.cc> (raw)
In-Reply-To: <7dc930c9-0e95-7310-5e01-762276e780e6@gmail.com>

Am 31. Oktober 2019 00:32:15 MEZ schrieb Florian Fainelli <f.fainelli@gmail.com>:
>On 10/30/19 4:18 PM, Andrew Lunn wrote:
>> On Wed, Oct 30, 2019 at 04:16:01PM -0700, Florian Fainelli wrote:
>>> On 10/30/19 3:42 PM, Michael Walle wrote:
>>>> The name of the PHY is actually AR803x not AT803x. Additionally,
>add the
>>>> name of the vendor and mention the AR8031 support.
>>>
>>> Should not the vendor be QCA these days, or Qualcomm Atheros?
>> 
>> Atheros Qualcomm would work best in terms of not upsetting the sort
>> order.
>
>Yes except the company is actually named Qualcomm Atheros:
>
>https://en.wikipedia.org/wiki/Qualcomm_Atheros

Correct.. my bad. also the atheros prefix is wrong then.. because there is already a qca prefix.

but.. should i also reorder the entry in the Kconfig then? 

-michael 


  reply	other threads:[~2019-10-31  0:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30 22:42 [RFC PATCH 0/3] net: phy: at803x device tree binding Michael Walle
2019-10-30 22:42 ` [RFC PATCH 1/3] net: phy: at803x: fix Kconfig description Michael Walle
2019-10-30 23:13   ` Andrew Lunn
2019-10-30 23:16   ` Florian Fainelli
2019-10-30 23:18     ` Andrew Lunn
2019-10-30 23:32       ` Florian Fainelli
2019-10-31  0:05         ` Michael Walle [this message]
2019-10-30 22:42 ` [RFC PATCH 2/3] dt-bindings: net: phy: Add support for AT803X Michael Walle
2019-10-30 23:17   ` Andrew Lunn
2019-10-31  0:14     ` Michael Walle
2019-10-31 16:45       ` Florian Fainelli
2019-10-31 17:14         ` Michael Walle
2019-10-30 23:28   ` Florian Fainelli
2019-10-30 23:36     ` Michael Walle
2019-11-01 15:03   ` Simon Horman
2019-11-02  1:19     ` Michael Walle
2019-10-30 22:42 ` [RFC PATCH 3/3] net: phy: at803x: add device tree binding Michael Walle
2019-10-30 23:21   ` Andrew Lunn
2019-10-30 23:28   ` Florian Fainelli
2019-10-30 23:59     ` Michael Walle
2019-10-31 17:22       ` Michael Walle
2019-10-31 17:35         ` Florian Fainelli
2019-11-02  1:18           ` Michael Walle

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=D615CB94-38A8-44E2-99CB-00FB1737FC5E@walle.cc \
    --to=michael@walle.cc \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).