From: Thomas Koeller <thomas.koeller@baslerweb.com>
To: Ulrich Eckhardt <eckhardt@satorlaser.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] eXcite nand flash driver
Date: Thu, 8 Feb 2007 11:20:25 +0100 [thread overview]
Message-ID: <200702081120.26026.thomas.koeller@baslerweb.com> (raw)
In-Reply-To: <200702080920.12723.eckhardt@satorlaser.com>
On Thursday 08 February 2007 09:20, Ulrich Eckhardt wrote:
> Just some cosmetic notes ...
>
> On Thursday 08 February 2007 01:57, Thomas Koeller wrote:
> > @@ -216,10 +216,26 @@ config MTD_NAND_DISKONCHIP_BBTWRITE
> > Even if you leave this disabled, you can enable BBT writes at module
> > load time (assuming you build diskonchip as a module) with the module
> > parameter "inftl_bbt_write=1".
> > -
> > +
>
> This just inserts whitespace.
No, it actually _removes_ whitspace.
>
> > tristate "NAND support for OLPC CAFÉ chip"
>
> The accent on the E might cause problems, but I'm not sure.
This has been in there before.
>
> > +#define io_readb(__a__) __raw_readb((__a__))
> > +#define io_writeb(__v__, __a__) __raw_writeb((__v__), (__a__))
>
> I would have used an inline function. Also, aren't there functions to use
> IOs already? What's the reason here?
>
> > +/* prefix for debug output */
> > +static const char module_id[] = "excite_nandflash";
>
> I'd have used
>
> static const char* module_id = "excite_nandflash";
>
> except if you need the sizeof it to capture the length.
Then I'd have used
static const char * const module_id = "excite_nandflash";
but what is the advantage of doing so?
>
> > +static inline const struct resource *excite_nand_get_resource
> > + (struct platform_device *d, unsigned long flags, const char
> > *basename){ + const char fmt[] = "%s_%u";
>
> Here, too, is no need for a local buffer, just use a pointer.
>
> > +/* excite_nand_probe
> > + *
> > + * called by device layer when it finds a device matching
> > + * one our driver can handled. [...]
>
> "... when it finds a device our driver can handle."
Right.
>
> Otherwise I'd say it looks very clean, better than quite some other stuff I
> have seen.
>
> Uli
>
Thanks for your comments!
_______________________________
Thomas Köller, Software Developer
Basler Vision Technologies
An der Strusbek 60-62
22926 Ahrensburg
Germany
Tel. +49 (0) 4102 - 463 390
Fax +49 (0) 4102 - 463 390
mailto:thomas.koeller@baslerweb.com
http://www.baslerweb.com
Vorstand: Dr.-Ing. Dietmar Ley (Vorsitzender) · John P. Jennings · Peter Krumhoff · Aufsichtsratsvorsitzender: Norbert Basler
Basler AG · Amtsgericht Ahrensburg HRB 4090 · Ust-IdNr.: DE 135 098 121 · Steuer-Nr.: 30 292 04497
_______________________________
next prev parent reply other threads:[~2007-02-08 10:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 0:57 [PATCH] eXcite nand flash driver Thomas Koeller
2007-02-08 8:20 ` Ulrich Eckhardt
2007-02-08 10:20 ` Thomas Koeller [this message]
2007-02-08 13:50 ` Josh Boyer
2007-02-08 13:55 ` Artem Bityutskiy
2007-02-08 15:48 ` Thomas Gleixner
2007-02-10 10:22 ` Thomas Koeller
2007-02-11 15:44 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2007-02-10 10:21 Thomas Koeller
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=200702081120.26026.thomas.koeller@baslerweb.com \
--to=thomas.koeller@baslerweb.com \
--cc=eckhardt@satorlaser.com \
--cc=linux-mips@linux-mips.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