From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] OMAP3: Remove legacy NAND defines
Date: Mon, 20 Apr 2009 17:42:56 +0200 [thread overview]
Message-ID: <20090420154256.GA14865@game.jcrosoft.org> (raw)
In-Reply-To: <20090420152128.GA25461@ld0162-tx32.am.freescale.net>
On 10:21 Mon 20 Apr , Scott Wood wrote:
> On Mon, Apr 20, 2009 at 07:19:57AM +0200, Wolfgang Denk wrote:
> > Dear Jean-Christophe PLAGNIOL-VILLARD,
> >
> > In message <20090417053017.GD31923@game.jcrosoft.org> you wrote:
> > > On 20:15 Tue 14 Apr , Dirk Behme wrote:
> > > > Remove remaining legacy NAND defines for Beagle, EVM, Overo and Pandora.
> > > >
> > > > Signed-off-by: Dirk Behme <dirk.behme@googlemail.com>
> > > > ---
> > > >
> > > > For Zoom1 it was already removed by
> > > >
> > > > http://lists.denx.de/pipermail/u-boot/2009-April/050150.html
> > > > http://lists.denx.de/pipermail/u-boot/2009-April/050871.html
> > > >
> > > > Changes in v2:
> > > >
> > > > - Remove even more legacy NAND defines. Thanks to Tom Rix for the hint.
> > > >
> > > > This version v2 makes all previous versions of this patch obsolete.
> > > will be apply on the next
> >
> > Why "next" ? As I understand, this fixes build problems in the
> > *current* tree?
>
> I don't think so -- my understanding is that these boards aren't
> currently using legacy NAND; they just have some remnants of it that need
> cleaning out.
correct
as it's cosmetics change I've not in mind to apply them for the release but
the next
Best Regards,
J.
next prev parent reply other threads:[~2009-04-20 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 18:15 [U-Boot] [PATCH v2] OMAP3: Remove legacy NAND defines Dirk Behme
2009-04-17 5:30 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-20 5:19 ` Wolfgang Denk
2009-04-20 15:21 ` Scott Wood
2009-04-20 15:42 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-04-20 16:29 ` Dirk Behme
2009-04-26 21:46 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-26 22:09 ` Wolfgang Denk
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=20090420154256.GA14865@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