From: Thomas Gleixner <tglx@linutronix.de>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [patch] generic nand driver for SoCs
Date: Tue, 01 May 2007 15:09:00 +0200 [thread overview]
Message-ID: <1178024940.5791.300.camel@localhost.localdomain> (raw)
In-Reply-To: <acd2a5930705010603s36f4b0c8l43b04bd970ac8b1c@mail.gmail.com>
On Tue, 2007-05-01 at 17:03 +0400, Vitaly Wool wrote:
> On 5/1/07, Thomas Gleixner <tglx@linutronix.de> wrote:
> > > +#ifdef CONFIG_MTD_PARTITIONS
> > > +static const char *part_probe_types[] = { "cmdlinepart", "RedBoot", NULL };
> > > +#endif
> > > +
> > Hmm, this should be provided by the platform as well.
>
> Really? I don't think platform code can call parse_mtd_partitions --
> nothing is set up at that moment yet. Please correct me if I'm missing
> something.
I meant the list of probe types which should be done.
tglx
next prev parent reply other threads:[~2007-05-01 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 12:24 [patch] generic nand driver for SoCs Vitaly Wool
2007-05-01 13:00 ` Thomas Gleixner
2007-05-01 13:03 ` Vitaly Wool
2007-05-01 13:09 ` Thomas Gleixner [this message]
2007-05-01 13:11 ` Vitaly Wool
2007-05-01 14:17 ` Stefan Roese
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=1178024940.5791.300.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=vitalywool@gmail.com \
/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