From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH-ARM 1/2] Add support for the Embest SBC2440-II Board
Date: Wed, 24 Jun 2009 01:40:01 +0200 [thread overview]
Message-ID: <20090623234001.GS23512@game.jcrosoft.org> (raw)
In-Reply-To: <4A3FD5C5.6030900@freescale.com>
On 14:04 Mon 22 Jun , Scott Wood wrote:
> Jean-Christophe PLAGNIOL-VILLARD wrote:
> >no as you add the nand in this patch
> >the nand need to be add in a seperate patch,
> >this one need to only add the s3c2440 support
> >and the nand will be handle by Scott the nand Maintainer
>
> If a NAND patch is sandwiched in the middle of other patches that
> need to go via an arch tree, and depends on some of those patches,
> I'd rather ack the NAND bits to go through the arch tree rather than
> try to merge everything separately while still maintaining
> dependencies. In that case, keeping the NAND bits in a separate
> patch is nice, but not mandatory IMHO.
To simplify bisect and merge I prefer to have the nand adding in an other
patch
Best Regards,
J.
next prev parent reply other threads:[~2009-06-23 23:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 16:42 [U-Boot] [PATCH-ARM 1/2] Add support for the Embest SBC2440-II Board kevin.morfitt at fearnside-systems.co.uk
2009-06-19 19:54 ` Wolfgang Denk
2009-06-20 17:36 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-20 23:56 ` kevin.morfitt at fearnside-systems.co.uk
2009-06-21 9:46 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-21 10:43 ` kevin.morfitt at fearnside-systems.co.uk
2009-06-22 19:04 ` Scott Wood
2009-06-23 0:19 ` kevin.morfitt at fearnside-systems.co.uk
2009-06-23 23:40 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-06-22 19:26 ` Scott Wood
2009-06-23 0:20 ` kevin.morfitt at fearnside-systems.co.uk
2009-06-23 16:15 ` Scott Wood
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=20090623234001.GS23512@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