From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] micrel: add support for KSZ8041RNLI
Date: Thu, 12 Dec 2013 00:28:47 +0300 [thread overview]
Message-ID: <52A8D90F.9090002@cogentembedded.com> (raw)
In-Reply-To: <20131211.135841.1810559740815410070.davem@davemloft.net>
Hello.
On 12/11/2013 09:58 PM, David Miller wrote:
>> Renesas R-Car development boards use KSZ8041RNLI PHY which for some reason has
>> ID of 0x00221537 that is not documented for KSZ8041-family PHYs and does not
>> match the documented ID of 0x0022151x (where 'x' is the revision). We have
>> to add the new #define PHY_ID_* and new ksphy_driver[] entry, almost the same
>> as KSZ8041 one, differing only in the 'phy_id' and 'name' fields.
>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>> ---
>> This patch is atop of DaveM's 'net-next.git' repo.
> Since this is just a simple device ID addition, I applied this to
> 'net', thanks.
Hm, thanks, of course. But I don't see much difference w/my 'sh_eth'
driver patch adding support for R8A7791 which you've queued for 3.14. Oh,
well, not that it matters much...
WBR, Sergei
next prev parent reply other threads:[~2013-12-11 21:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 23:20 [PATCH] micrel: add support for KSZ8041RNLI Sergei Shtylyov
2013-12-10 13:19 ` Geert Uytterhoeven
2013-12-10 17:21 ` Sergei Shtylyov
2013-12-10 19:05 ` Geert Uytterhoeven
2013-12-11 3:26 ` David Miller
2013-12-11 15:39 ` Sergei Shtylyov
2013-12-11 18:58 ` David Miller
2013-12-11 21:28 ` Sergei Shtylyov [this message]
2013-12-11 21:11 ` David Miller
2013-12-11 23:02 ` Sergei Shtylyov
2013-12-11 22:10 ` David Miller
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=52A8D90F.9090002@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--cc=linux-sh@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).