From: Guennadi Liakhovetski <lg@denx.de>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: Steve.Glendinning@smsc.com, netdev@vger.kernel.org,
Ian.Saturley@smsc.com
Subject: Re: [PATCH, RFC] Extend smc911x to support LAN921x chips
Date: Sat, 11 Oct 2008 22:30:57 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0810112223160.4965@axis700.grange> (raw)
In-Reply-To: <87k5cfoz7b.fsf@macbook.be.48ers.dk>
On Sat, 11 Oct 2008, Peter Korsgaard wrote:
> >>>>> "Guennadi" == Guennadi Liakhovetski <lg@denx.de> writes:
>
> Hi,
>
> Guennadi> On Sat, 11 Oct 2008, Peter Korsgaard wrote:
> >> >>>>> "Guennadi" == Guennadi Liakhovetski <lg@denx.de> writes:
> >>
> >> It looks good, but you should definately split out the arm and cleanup
> >> stuff from the new IDs.
>
> Guennadi> You mean remove the new IDs? Why?
>
> No, just have them in seperate patches - They are independent of each
> other, so no need to put in the same patch.
No, they are not independent. smc91x.c is comparing the ID read from the
hardware with the table, which someone strangely enough for me put in the
header. So, even if one were to split them, you would have to make it a
patch series and make the patch for .c depend on the one for .h adding
IDs. So, no, these two belong into one patch.
> >> What's this for? Isn't that handled just above?
>
> Guennadi> I think, there's a bug in the code there. The break above
> Guennadi> terminates the loop, yes, but then it falls through in the
> Guennadi> switch statement to the default case and overwrites the
> Guennadi> just found PHY.
>
> Ahh, the good old break-only-escapes-the-innermost-scope. That's a
> good fix, but please send it seperately from the patch adding the new
> IDs.
Ok... it is a simple enough fix, so, one could put them both in one patch
and be done with them, just explaining both in the patch description, but
ok, I can make it a separate patch too...
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office@denx.de
next prev parent reply other threads:[~2008-10-11 20:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 15:26 Extend smc911x to support LAN921x chips - differences? Steve.Glendinning
2008-09-09 16:18 ` Guennadi Liakhovetski
2008-09-09 20:08 ` Peter Korsgaard
2008-10-10 23:33 ` [PATCH, RFC] Extend smc911x to support LAN921x chips Guennadi Liakhovetski
2008-10-11 7:22 ` Peter Korsgaard
2008-10-11 9:00 ` Guennadi Liakhovetski
2008-10-11 16:48 ` Peter Korsgaard
2008-10-11 20:30 ` Guennadi Liakhovetski [this message]
2008-10-12 7:38 ` Peter Korsgaard
2008-10-11 21:10 ` [PATCH] smc911x: Fix external PHY detection Guennadi Liakhovetski
2008-10-11 22:07 ` David Miller
2008-10-12 7:43 ` Peter Korsgaard
2008-10-11 21:13 ` [PATCH] smc911x: Add support for LAN921{5,7,8} chips from SMSC Guennadi Liakhovetski
2008-10-11 22:08 ` David Miller
2008-10-11 22:59 ` [PATCH v2] " Guennadi Liakhovetski
2008-10-12 7:54 ` Peter Korsgaard
2008-10-13 4:05 ` 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=Pine.LNX.4.64.0810112223160.4965@axis700.grange \
--to=lg@denx.de \
--cc=Ian.Saturley@smsc.com \
--cc=Steve.Glendinning@smsc.com \
--cc=jacmet@sunsite.dk \
--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