From: Jonathan McDowell <noodles@earth.li>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add Amstrad Delta NAND support.
Date: Fri, 19 May 2006 10:01:42 +0100 [thread overview]
Message-ID: <20060519090142.GB7570@earth.li> (raw)
In-Reply-To: <20060518165728.GA26113@wohnheim.fh-wedel.de>
On Thu, May 18, 2006 at 06:57:28PM +0200, Jörn Engel wrote:
> On Thu, 18 May 2006 17:09:41 +0100, Jonathan McDowell wrote:
> > + omap_writew(0, (OMAP_MPUIO_BASE + OMAP_MPUIO_IO_CNTL));
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Could that be done in a macro?
Is there any benefit to doing so?
> > + udelay(0.04);
>
> Floating point in the kernel?
Not quite. udelay is a macro on ARM so this ends up as an integer before
it ever hits a function call. In an ideal world I'd use "ndelay(40);"
but that would result in a delay of over 1µs as ARM doesn't have ndelay
defined so we hit the generic fallback.
> > + ams_delta_mtd = kmalloc (sizeof(struct mtd_info) +
> ^
> > + sizeof (struct nand_chip), GFP_KERNEL);
>
> Remove space
>
> And please create a structure containing both struct mtd_info and
> struct nand_chip. Then use sizeof(that structure)...
This format is used throughout the drivers/mtd/nand/ directory. I'd
suggest it'd be more appropriate to have a separate patch that did this
for all of them if it's desired, rather than having each driver do its
own thing.
Agreed on all the spacing comments you raised; hangovers from toto.c
that I used as a base.
J.
--
I am a passenger.
next prev parent reply other threads:[~2006-05-19 9:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 16:09 [PATCH] Add Amstrad Delta NAND support Jonathan McDowell
2006-05-18 16:57 ` Jörn Engel
2006-05-19 9:01 ` Jonathan McDowell [this message]
2006-05-19 9:32 ` David Vrabel
2006-05-19 10:01 ` Jonathan McDowell
2006-05-19 10:03 ` Jörn Engel
2006-05-19 10:26 ` David Woodhouse
2006-05-20 0:10 ` Segher Boessenkool
2006-05-20 14:10 ` Jonathan McDowell
2006-05-21 17:12 ` David Woodhouse
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=20060519090142.GB7570@earth.li \
--to=noodles@earth.li \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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