From: Artem Bityutskiy <dedekind@infradead.org>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: DaVinci <davinci-linux-open-source@linux.davincidsp.com>,
David Brownell <david-b@pacbell.net>,
Linux MTD <linux-mtd@lists.infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
dwmw2@infradead.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch/RESEND 2.6.30-rc2 2/3] NAND: minor davinci_nand cleanup
Date: Sun, 31 May 2009 15:48:18 +0300 [thread overview]
Message-ID: <1243774098.11172.123.camel@localhost.localdomain> (raw)
In-Reply-To: <87vdnjsay6.fsf@deeprootsystems.com>
On Fri, 2009-05-29 at 17:15 -0700, Kevin Hilman wrote:
> David Brownell <david-b@pacbell.net> writes:
>
> > From: David Brownell <dbrownell@users.sourceforge.net>
> >
> > Make the DaVinci NAND driver require platform_data with
> > board-specific configuration. We can't actually do any
> > kind of sane job of configuring it otherwise.
> >
> > Also fix the comment about picking the "best" ECC mode.
> >
> > We can't do those any more; that relied on knowing what kind
> > of CPU we're using (they don't all support 4-bit ECC), and
> > current policy is that drivers not have cpu_is_*() checks.
> >
> > Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
>
> AFAICT, this still hasn't been merged yet. In case it helps:
>
> Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
>
> > ---
> > RESEND 7-april version -- refreshing against current kernel
> > Seems appropriate for 2.6.30 merge, but not essential.
>
> Would be nice to see this in 2.6.31.
Yeah, it is in my l2-mtd-2.6.git tree, which means this won't be
forgotten.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2009-05-31 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 2:51 [patch/RESEND 2.6.30-rc2 2/3] NAND: minor davinci_nand cleanup David Brownell
2009-05-30 0:15 ` Kevin Hilman
2009-05-31 12:48 ` Artem Bityutskiy [this message]
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=1243774098.11172.123.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=dwmw2@infradead.org \
--cc=khilman@deeprootsystems.com \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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