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: Wed, 11 Dec 2013 19:39:05 +0400 [thread overview]
Message-ID: <52A88719.4000406@cogentembedded.com> (raw)
In-Reply-To: <20131210.222639.2106376982664488750.davem@davemloft.net>
Hello.
On 11-12-2013 7:26, 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.
> You said something to Geert about "Though it's not the last version
> probably..." are you talking about this patch needing more revisions?
Well, maybe. I half-expected some criticisms. My changelog was somewhat
tautological, and I'm not sure about the ID mask, perhaps it should be
0x00ffffff to also cover the revision field. Since the ID is totally
undocumented, I'm just not very sure how to deal with it properly.
> If so, please make it explicit that you are posting something that is
> just for feedback and not applying by using "RFC" in the subject line.
At the time of sending I intended it to be applied, if no negative
comments would have been posted.
> Thanks.
WBR, Sergei
next prev parent reply other threads:[~2013-12-11 15:39 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 [this message]
2013-12-11 18:58 ` David Miller
2013-12-11 21:28 ` Sergei Shtylyov
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=52A88719.4000406@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).