netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2 v4] fs_enet/mii-fec.c: fix MII speed calculation
Date: Fri, 17 Jul 2009 14:32:45 +0200	[thread overview]
Message-ID: <20090717123245.4595F832E416@gemini.denx.de> (raw)
In-Reply-To: <20090717093307.GB3150@pengutronix.de>

Dear Wolfram Sang,

In message <20090717093307.GB3150@pengutronix.de> you wrote:
> 
...
> > @@ -188,6 +209,12 @@ static struct of_device_id fs_enet_mdio_fec_match[] = {
> >  	{
> >  		.compatible = "fsl,pq1-fec-mdio",
> >  	},
> > +#if defined(CONFIG_PPC_MPC512x)
> > +	{
> > +		.compatible = "fsl,mpc5121-fec-mdio",
> > +		.data = mpc5xxx_get_bus_frequency,
> > +	},
> > +#endif
>
> Grepping through 'drivers/*' I see that #ifdefing compatible-entries is highly
> uncommon (just 3 hits). I think a guideline would be useful. Most people like
> to avoid #ifdefs at any cost, while I personally think it doesn't spoil
> readability too much here. Other opinions?

An older version of the patch tried to "hide" the ifdef in a 512x
specific header, so at least common code would remain clean, but I
agree with Grant that this current version looks cleaner globally.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"You can have my Unix system when you  pry  it  from  my  cold,  dead
fingers."                                                - Cal Keegan

  reply	other threads:[~2009-07-17 12:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1244751543-21977-2-git-send-email-wd@denx.de>
2009-07-14 13:42 ` [PATCH v2] fs_enet/mii-fec.c: fix MII speed calculation Wolfgang Denk
2009-07-15 15:18   ` [PATCH 1/2 v3] " Wolfgang Denk
2009-07-15 17:17     ` Grant Likely
2009-07-16 21:21       ` Wolfgang Denk
2009-07-16 22:37         ` Grant Likely
2009-07-16 21:42     ` [PATCH 1/2 v4] " Wolfgang Denk
2009-07-16 22:44       ` Grant Likely
2009-07-17 12:24         ` Wolfgang Denk
2009-07-17  9:33       ` Wolfram Sang
2009-07-17 12:32         ` Wolfgang Denk [this message]
2009-07-17 12:27       ` [PATCH 1/2 v5] " Wolfgang Denk
2009-07-17 14:41         ` Grant Likely
2009-07-17 16:21           ` David Miller
2009-07-17 16:48           ` David Miller
2009-07-17 12:27       ` [PATCH 2/2 v3] MPC52xx FEC: be more conservative when setting MII_SPEED register Wolfgang Denk
2009-07-17 12:59         ` [PATCH 2/2 v4] " Wolfgang Denk
2009-07-17 14:45           ` Grant Likely
2009-07-17 17:51             ` Wolfgang Denk
2009-07-17 18:31               ` Grant Likely
2009-07-16 21:42     ` [PATCH 2/2 v2] " Wolfgang Denk
2009-07-16 22:48       ` Grant Likely
2009-07-17 12:25         ` Wolfgang Denk
2009-07-17  9:47       ` Wolfram Sang
2009-07-17 12:35         ` Wolfgang Denk
2009-07-15 15:18   ` [PATCH 2/2] " Wolfgang Denk
2009-07-15 17:18     ` Grant Likely
2009-07-16 21:21       ` Wolfgang Denk

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=20090717123245.4595F832E416@gemini.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=w.sang@pengutronix.de \
    /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).