From mboxrd@z Thu Jan 1 00:00:00 1970 From: Heiko Schocher Date: Sat, 18 Jul 2009 10:43:44 +0200 Subject: [U-Boot] [PATCHv3 3/3] 83xx, kmeter1: added NAND support In-Reply-To: <20090717153611.GD31317@b07421-ec1.am.freescale.net> References: <4A584AFC.6080005@invitel.hu> <200907131120.31201.sr@denx.de> <4A5B0483.3060407@denx.de> <200907131157.34023.sr@denx.de> <4A5B0930.9010409@denx.de> <20090716193518.GE32758@b07421-ec1.am.freescale.net> <4A60067F.9000400@denx.de> <20090717153611.GD31317@b07421-ec1.am.freescale.net> Message-ID: <4A618B40.9050000@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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