From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] Noisily disable the legacy NAND subsystem.
Date: Sat, 4 Apr 2009 18:36:54 +0200 [thread overview]
Message-ID: <20090404163654.GE32409@game.jcrosoft.org> (raw)
In-Reply-To: <20090401214106.GA11189@ld0162-tx32.am.freescale.net>
On 16:41 Wed 01 Apr , Scott Wood wrote:
> Legacy NAND is marked for feature removal after April 2009 (i.e. this
> upcoming release). There are still several boards that reference it
> (though many do so only for disk-on-chip support which has been silently
> disabled for a while now). These boards will now fail to build
> with #error, though the code is still there if the user removes #error.
>
> The plan is to remove the code outright in the next release, along with
> any board code that refers to it (such as board/esd/common/auto_update.c).
>
> Also, remove the legacy NAND API description from README.nand.
>
> Signed-off-by: Scott Wood <scottwood@freescale.com>
> ---
> Now with doc updates, restoration of a missing changelog line,
> and clarification of the error message in cmd_doc.c.
>
> Applied to u-boot-nand-flash.
Scoot you brake the rm9200dk
could you convert your #error in #warning for this release
as it's said in the commit message it will be remove for the next release
it will be nice to have this kind of #error at the beginning to the merge to
allow people to fix it
Best Regards,
J.
next prev parent reply other threads:[~2009-04-04 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 21:41 [U-Boot] [PATCH v2] Noisily disable the legacy NAND subsystem Scott Wood
2009-04-04 16:36 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-04-04 17:51 ` Wolfgang Denk
2009-04-04 21:20 ` ksi at koi8.net
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=20090404163654.GE32409@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=u-boot@lists.denx.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