From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] nand_spl: display warning message to inform the end of nand_spl
Date: Wed, 26 Feb 2014 08:37:36 -0500 [thread overview]
Message-ID: <20140226133736.GW16805@bill-the-cat> (raw)
In-Reply-To: <1393404671-6385-1-git-send-email-yamada.m@jp.panasonic.com>
On Wed, Feb 26, 2014 at 05:51:11PM +0900, Masahiro Yamada wrote:
> Now we have two different frameworks for doing the same thing.
> I'd like to propose to drop nand_spl framework.
> How about deleting it before v2014.07 release?
>
> In the interim, this commit will display a warning message
> when compiling nand_spl board.
>
> Now we have 19 nand_spl boards:
>
> MPC8315ERDB_NAND
> SIMPC8313_LP
> SIMPC8313_SP
> MPC8536DS_NAND
> MPC8569MDS_NAND
> MPC8572DS_NAND
> P1023RDS_NAND
> P1011RDB_NAND
> P1020RDB_NAND
> P2010RDB_NAND
> P2020RDB_NAND
> acadia_nand
> bamboo_nand
> canyonlands_nand
> glacier_nand
> haleakala_nand
> kilauea_nand
> rainier_nand
> sequoia_nand
>
> They must be ported to SPL before the deadline,
> otherwise they will be removed.
>
> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> Cc: Dave Liu <daveliu@freescale.com>
> Cc: Ron Madrid <info@sheldoninst.com>
> Cc: Roy Zang <tie-fei.zang@freescale.com>
> Cc: Stefan Roese <sr@denx.de>
Scott? York? I'm fine with the above date.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140226/c99451fd/attachment.pgp>
next prev parent reply other threads:[~2014-02-26 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 8:51 [U-Boot] [RFC PATCH] nand_spl: display warning message to inform the end of nand_spl Masahiro Yamada
2014-02-26 13:37 ` Tom Rini [this message]
2014-02-26 14:20 ` Stefan Roese
2014-02-26 14:27 ` Tom Rini
2014-03-04 19:16 ` [U-Boot] [U-Boot, RFC] " Tom Rini
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=20140226133736.GW16805@bill-the-cat \
--to=trini@ti.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