From: dk-arm-linux@gmx.de (Dieter Kiermaier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [ARM] kirkwood: combine support for openrd base/client support
Date: Fri, 9 Oct 2009 16:24:34 +0200 [thread overview]
Message-ID: <200910091624.34898.dk-arm-linux@gmx.de> (raw)
In-Reply-To: <20091009140508.GD6085@chipmunk>
Hi Alexander,
> Hi,
>
> * Dieter Kiermaier <dk-arm-linux@gmx.de> [2009-10-09 16:00:44+0200]:
> >
> > [snipped]
> >
> > > +static void __init openrd_init(void)
> > > +{
> > > + /*
> > > + * Basic setup. Needs to be called early.
> > > + */
> > > + kirkwood_init();
> > > + kirkwood_mpp_conf(openrd_mpp_config);
> > > +
> > > + kirkwood_uart0_init();
> > > + kirkwood_nand_init(ARRAY_AND_SIZE(openrd_nand_parts), 25);
> > > +
> > > + kirkwood_ehci_init();
> > > +
> > > + kirkwood_ge00_init(&openrd_ge00_data);
> > > +#ifdef CONFIG_MACH_OPENRD_CLIENT
> > > + if (machine_is_openrd_client())
> > > + kirkwood_ge01_init(&openrd_ge01_data);
> > > +#endif
> >
> > shouldn't it be enough to have the if(machine_is.... statement?
> > I didn't see why you test #ifdef, too?
> >
> the struct 'openrd_ge01_data' is wrapped in
> #ifdef CONFIG_MACH_OPENRD_CLIENT too and only exists if you want the
> board support for it. So although machine_is_openrd_client() will
> exist, the compiler will barf that openrd_ge01_data does not exist; the
> alternative is to have it grumble (when you do not want the Client
> support) that there is an un-used struct floating about.
>
> I was under the impression the latter is considered worse than the
> former, I personally am not bothered either way.
>
Ah, ok. I didn't stumble over that. I just wonder why doing 2 times the same...
> > Additionally it would be nice, if you could integrate the i2c / pcie
> > init in your patch? Please see Simons patch at:
> >
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2009-October/001950.html
> >
> I knew someone was going to say that :) Will do though, so 'watch this
> space'.
>
> Cheers
>
Many thanks and have a nice weekend,
Dieter
next prev parent reply other threads:[~2009-10-09 14:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 12:39 [PATCH] [ARM] kirkwood: combine support for openrd base/client support Alexander Clouter
2009-10-09 12:41 ` Alexander Clouter
2009-10-09 14:00 ` Dieter Kiermaier
2009-10-09 14:03 ` Dhaval Vasa
2009-10-09 14:03 ` Dhaval Vasa
2009-10-09 14:05 ` Alexander Clouter
2009-10-09 14:24 ` Dieter Kiermaier [this message]
2009-10-13 3:20 ` Nicolas Pitre
2009-10-13 14:28 ` [PATCH] [ARM] kirkwood: combine support for openrd base/client?support Alexander Clouter
2009-10-09 15:24 ` [PATCH] [ARM] kirkwood: combine support for openrd base/client support Alexander Clouter
2009-10-12 6:36 ` Dieter Kiermaier
2009-10-12 7:31 ` Alexander Clouter
2009-10-12 7:46 ` Dieter Kiermaier
2009-10-12 14:46 ` Joel Stanley
2009-10-13 14:41 ` [PATCH] [ARM] kirkwood: combine support for openrd base/client ?support Alexander Clouter
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=200910091624.34898.dk-arm-linux@gmx.de \
--to=dk-arm-linux@gmx.de \
--cc=linux-arm-kernel@lists.infradead.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).