public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@nokia.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "dedekind@infradead.org" <dedekind@infradead.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 4/4] onenand init: Pass configuration data from board-*.c files
Date: Thu, 30 Apr 2009 08:53:34 +0300	[thread overview]
Message-ID: <49F93CDE.3000105@nokia.com> (raw)
In-Reply-To: <20090429215037.13138.62993.stgit@localhost>

Tony Lindgren wrote:
> Pass configuration data from board-*.c files.
> 
> Also remove support for the OMAP_TAG_PARTITION tag.
> If the partition info is passed, it should be passed from
> cmdline, and probably should be done in a generic way
> in the drivers/mtd.
> 
> Signed-off-by: Tony Lindgren <tony@atomide.com>
> ---

NAK

This would break all our flashing infrastructure.

  parent reply	other threads:[~2009-04-30  5:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29 21:49 [PATCH 0/4] Generic gpmc-onenand initialization, v2 Tony Lindgren
2009-04-29 21:50 ` [PATCH 1/4] onenand init: Rename board-n800-flash.c to gpmc-onenand.c Tony Lindgren
2009-04-29 21:50 ` [PATCH 2/4] onenand init: Build gpmc-onenand.o based on CONFIG_MTD_ONENAND_OMAP2 Tony Lindgren
2009-04-29 21:50 ` [PATCH 3/4] onenand init: Rename n800_* functions to gpmc_onenand_* functions Tony Lindgren
2009-04-29 21:50 ` [PATCH 4/4] onenand init: Pass configuration data from board-*.c files Tony Lindgren
2009-04-29 21:54   ` [PATCH 5/4] onenand init: Debug patch to print out the onenand partitions from bootloader Tony Lindgren
2009-04-30  5:53   ` Adrian Hunter [this message]
2009-04-30 14:01     ` [PATCH 4/4] onenand init: Pass configuration data from board-*.c files Tony Lindgren

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=49F93CDE.3000105@nokia.com \
    --to=adrian.hunter@nokia.com \
    --cc=dedekind@infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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