From: Harvey Harrison <harvey.harrison@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Nicolas Pitre <nico@cam.org>,
drzeus-mmc@drzeus.cx, linux-kernel@vger.kernel.org,
maen@marvell.com
Subject: Re: [PATCH] SDIO driver for Marvell SoCs
Date: Thu, 19 Feb 2009 15:01:37 -0800 [thread overview]
Message-ID: <1235084497.4377.8.camel@brick> (raw)
In-Reply-To: <20090219145305.01451253.akpm@linux-foundation.org>
On Thu, 2009-02-19 at 14:53 -0800, Andrew Morton wrote:
> On Thu, 19 Feb 2009 17:02:32 -0500 (EST)
> Nicolas Pitre <nico@cam.org> wrote:
>
> > On Thu, 19 Feb 2009, Andrew Morton wrote:
> >
> > > On Tue, 17 Feb 2009 23:46:21 -0500 (EST)
> > > Nicolas Pitre <nico@cam.org> wrote:
> > >
> > > > +#define mvsd_write(offs, val) writel(val, iobase + (offs))
> > > > +#define mvsd_read(offs) readl(iobase + (offs))
> > >
> > > It's rather grotty to have a macro which secretly relies upon the
> > > presence of a particularly-named local variable.
> >
> > My call. Otherwise the code becomes bloated with repeated iobase noise
> > everywhere, making many lines bust the 80 column limit imposed by the
> > checkpatch.pl. The alternative is to split those statement on multiple
> > lines making things not prettier. So, unless you want to help
> > maintaining this driver, I prefer this grottiness to remains as is.
>
> For the record: you do not get to put bad code into Linux by telling
> the person who points out that bad code that he needs to maintain a
> fixed verion. Just cut the sophomoric crap.
>
> I don't care much - we have plenty of grotty code down in drivers/
I think this is a not-so-uncommon pattern in network drivers. FWIW
Harvey
next prev parent reply other threads:[~2009-02-19 23:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 4:46 [PATCH] SDIO driver for Marvell SoCs Nicolas Pitre
2009-02-19 20:44 ` Andrew Morton
2009-02-19 22:02 ` Nicolas Pitre
2009-02-19 22:53 ` Andrew Morton
2009-02-19 23:01 ` Harvey Harrison [this message]
2009-02-19 22:14 ` [PATCH v2] " Nicolas Pitre
2009-02-19 22:58 ` Andrew Morton
2009-02-20 1:41 ` Nicolas Pitre
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=1235084497.4377.8.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=drzeus-mmc@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=maen@marvell.com \
--cc=nico@cam.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