From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Ben Dooks <ben-linux@fluff.org>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
Pierre Ossman <drzeus@drzeus.cx>,
ARM Linux Mailing List <linux-arm-kernel@lists.arm.linux.org.uk>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Andrew Victor <linux@maxim.org.za>,
Ville Syrjala <syrjala@sci.fi>, Marc Pignat <marc.pignat@hevs.ch>
Subject: Re: [PATCH 3/3] at91_mci: introduce per-mci-revision conditional code
Date: Sat, 19 Jul 2008 22:04:19 +0200 [thread overview]
Message-ID: <20080719200419.GA368@game.jcrosoft.org> (raw)
In-Reply-To: <20080717110403.GH24620@fluff.org.uk>
On 12:04 Thu 17 Jul , Ben Dooks wrote:
> On Thu, Jul 17, 2008 at 11:42:01AM +0200, Nicolas Ferre wrote:
> > We used to manage features and differences on a per-cpu basis. As several
> > cpus share the same mci revision, this patch aggregates cpus that have the
> > same IP revision in one defined constant.
> >
> > Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> > ---
> > drivers/mmc/host/at91_mci.c | 21 +++++++++++++--------
> > 1 files changed, 13 insertions(+), 8 deletions(-)
> >
> > diff --git a/drivers/mmc/host/at91_mci.c b/drivers/mmc/host/at91_mci.c
> > index 4e3edf3..a95529c 100644
> > --- a/drivers/mmc/host/at91_mci.c
> > +++ b/drivers/mmc/host/at91_mci.c
> > @@ -80,6 +80,11 @@
> >
> > #define DRIVER_NAME "at91_mci"
> >
> > +#define AT91MCI_REV2 ( cpu_is_at91sam9260() \
> > + || cpu_is_at91sam9263() \
> > + || cpu_is_at91cap9() \
> > + || cpu_is_at91sam9rl())
> > +
>
> How about making it an inline function to avoid the horrible
> upper-case all throughtout?
>
How about also naming as at91mci_is_rev2() to a few more explicit?
Best Regards,
J.
prev parent reply other threads:[~2008-07-19 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 9:42 [PATCH 3/3] at91_mci: introduce per-mci-revision conditional code Nicolas Ferre
2008-07-17 11:04 ` Ben Dooks
2008-07-19 20:04 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
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=20080719200419.GA368@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=ben-linux@fluff.org \
--cc=drzeus@drzeus.cx \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=marc.pignat@hevs.ch \
--cc=nicolas.ferre@atmel.com \
--cc=syrjala@sci.fi \
/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