linux-kernel - Re: [PATCH] SDIO driver for Marvell SoCs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1235084497.4377.8.camel@brick>
Date:	Thu, 19 Feb 2009 15:01:37 -0800
From:	Harvey Harrison <harvey.harrison@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Nicolas Pitre <nico@....org>, drzeus-mmc@...eus.cx,
	linux-kernel@...r.kernel.org, maen@...vell.com
Subject: Re: [PATCH] SDIO driver for Marvell SoCs

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@....org> wrote:
> 
> > On Thu, 19 Feb 2009, Andrew Morton wrote:
> > 
> > > On Tue, 17 Feb 2009 23:46:21 -0500 (EST)
> > > Nicolas Pitre <nico@....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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/