From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jerry Van Baren <gerald.vanbaren@ge.com>
Date: Fri, 06 Nov 2009 16:17:57 -0500
Subject: [U-Boot] Quick sanity test after my NAND patches
In-Reply-To: <20091106210801.GA31725@loki.buserror.net>
References: <0554BEF07D437848AF01B9C9B5F0BC5D93D82E24@dlee01.ent.ti.com>
	<20091106210801.GA31725@loki.buserror.net>
Message-ID: <4AF49285.4050101@ge.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Scott Wood wrote:
> On Fri, Nov 06, 2009 at 02:47:01PM -0600, Paulraj, Sandeep wrote:
>> As most of you know I submitted a lot of patches for the MTD NAND driver
>> to sync up with what's in the kernel.
> 
> They appear to correlate with specific Linux commits -- could you preserve
> the authorship and signoffs?  Especially when a copyrightably-sized chunk of
> code is being added.
> 
> -Scott

I don't know if the technique will work for you (Sandeep), but for the 
libfdt synchronization, I literally extracted the patches from the 
master DTC repository (git format-patch) and applied them (git am).

For the most part, David Gibson and Jon Loeliger made separate patches 
for libfdt vs. the other stuff, so that was very helpful.  Once or twice 
I hand edited the patch to remove patches to non-libfdt files.  I also 
have to change the include/fdtlib.h file path since the DTC puts the 
header file in a different directory.  Hand editing the patches is an 
ugly solution, but the result is very nice since it preserves the 
changes, signoffs, and comments verbatim.

HTH,
gvb