From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Legacy NAND support to be removed after April 2009; please update your boards.
Date: Tue, 20 Jan 2009 13:35:25 -0600 [thread overview]
Message-ID: <4976277D.1090006@freescale.com> (raw)
In-Reply-To: <200901201932.39877.sr@denx.de>
Stefan Roese wrote:
> On Tuesday 20 January 2009, Scott Wood wrote:
> > I'll apply this, though I recommend switching to the non-legacy code
> > (which always block-skips, BTW). I'd like to see the legacy code go away
> > soon.
>
> Yes. How about setting a date for this removal? I suggest to remove it after
> the next two releases (after v2009-03/04).
OK, feature removal schedule updated.
To anyone with an interest in a board that still uses legacy NAND,
please try to get it converted over the next two merge windows.
-Scott
prev parent reply other threads:[~2009-01-20 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 15:57 [U-Boot] [PATCH] nand read.jffs2 (nand_legacy) in common/cmd_nand.c Schlaegl Manfred jun.
2009-01-20 18:09 ` Scott Wood
2009-01-20 18:14 ` Scott Wood
2009-01-20 18:32 ` Stefan Roese
2009-01-20 19:35 ` Scott Wood [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=4976277D.1090006@freescale.com \
--to=scottwood@freescale.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