public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Nicolas Pitre <nico@cam.org>
Cc: 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 14:53:05 -0800	[thread overview]
Message-ID: <20090219145305.01451253.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0902191625120.5511@xanadu.home>

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:
> > 
> > > From: Maen Suleiman <maen@marvell.com>
> > > 
> > > This supports MMC/SD/SDIO currently found on the Kirkwood 88F6281 and
> > > 88F6192 SoC controllers.
> > > 
> > > Signed-off-by: Nicolas Pitre <nico@marvell.com>
> > 
> > It would be nice to have Maen's signoff.
> 
> Sure, I can add it if this is Maen's wish.  Still, this single signoff 
> was made in conformity with option B of the Developer's Certificate of 
> Origin 1.1 as found in Documentation/SubmittingPatches.  It is actually 
> my duty at Marvell to act as such.

No, it's not required.  But "nice".

> > >
> > > ...
> > >
> > > +#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/

> > > +
> > > +		if (host->gpio_card_detect) {
> > > +			free_irq(gpio_to_irq(host->gpio_card_detect), host);
> > > +			gpio_free(host->gpio_card_detect);
> > > +		}
> > > +		mmc_remove_host(mmc);
> > > +		free_irq(host->irq, host);
> > > +		if (host->gpio_write_protect)
> > > +			gpio_free(host->gpio_write_protect);
> > > +		del_timer_sync(&host->timer);
> > > +		mvsd_power_down(host);
> > > +		iounmap(host->base);
> > > +		release_resource(host->res);
> > > +		mmc_free_host(mmc);
> > 
> > Perhaps this function and the error path ("out:") in the preceding
> > function could share code.
> 
> Well, one is marked __init and the other __exit.  Having common code 
> would mean this needs to be in a non discardable section which is a 
> waste.

OK.  

  reply	other threads:[~2009-02-19 22:54 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 [this message]
2009-02-19 23:01       ` Harvey Harrison
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=20090219145305.01451253.akpm@linux-foundation.org \
    --to=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