public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHv3 3/3] 83xx, kmeter1: added NAND support
Date: Sat, 18 Jul 2009 10:43:44 +0200	[thread overview]
Message-ID: <4A618B40.9050000@denx.de> (raw)
In-Reply-To: <20090717153611.GD31317@b07421-ec1.am.freescale.net>

Hello Scott,

Scott Wood wrote:
> On Fri, Jul 17, 2009 at 07:05:03AM +0200, Heiko Schocher wrote:
>> Hmm... this is the third patch of a patchset, so it apply cleanly, if
>> the other 2 patches are first applied ... or should I base this patch
>> against current nand-flash tree, because this patch goes through your
>> tree?
> 
> Ah, I missed that.  It's generally preferred, when possible, to not mix
> custodians in a single patchset -- if you can separate out the NAND
> driver into its own standalone patch (that doesn't touch any board
> configs), that'd be ideal.  Otherwise, it'll have to wait until the

Hmm.. because it is for the kmeter1 (83xx) based board, it touches
also this config file ...

> prerequisite patches are merged (or at least acked) by the relevant
> custodian.

I prefer this way. If this is OK for you I can send a new patch,
with your suggestions included ...

bye
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2009-07-18  8:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-11  8:19 [U-Boot] [PATCHv2 3/3] 83xx, kmeter1: added NAND support Heiko Schocher
2009-07-13  9:20 ` Stefan Roese
2009-07-13  9:55   ` Heiko Schocher
2009-07-13  9:57     ` Stefan Roese
2009-07-13 10:15       ` [U-Boot] [PATCHv3 " Heiko Schocher
2009-07-16 19:35         ` Scott Wood
2009-07-17  5:05           ` Heiko Schocher
2009-07-17 15:36             ` Scott Wood
2009-07-18  8:43               ` Heiko Schocher [this message]
2009-07-21 15:13         ` [U-Boot] [PATCHv4 " Heiko Schocher
2009-08-06 22:08           ` 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=4A618B40.9050000@denx.de \
    --to=hs@denx.de \
    --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