From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Quick sanity test after my NAND patches
Date: Fri, 06 Nov 2009 16:17:57 -0500 [thread overview]
Message-ID: <4AF49285.4050101@ge.com> (raw)
In-Reply-To: <20091106210801.GA31725@loki.buserror.net>
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
next prev parent reply other threads:[~2009-11-06 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 20:47 [U-Boot] Quick sanity test after my NAND patches Paulraj, Sandeep
2009-11-06 21:08 ` Scott Wood
2009-11-06 21:17 ` Jerry Van Baren [this message]
2009-11-06 21:28 ` Paulraj, Sandeep
2009-11-06 21:37 ` Jerry Van Baren
2009-11-06 21:44 ` Paulraj, Sandeep
2009-11-08 22:59 ` Wolfgang Denk
2009-11-06 22:03 ` Scott Wood
2009-11-06 22:14 ` Paulraj, Sandeep
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=4AF49285.4050101@ge.com \
--to=gerald.vanbaren@ge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.