From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 0/3] mtd, ubi, ubifs: resync with Linux-3.14
Date: Wed, 25 Jun 2014 06:56:02 +0200 [thread overview]
Message-ID: <53AA5662.80502@denx.de> (raw)
In-Reply-To: <1403637570.26908.38.camel@snotra.buserror.net>
Hello Scott,
Am 24.06.2014 21:19, schrieb Scott Wood:
> On Sun, 2014-06-22 at 08:59 +0200, Heiko Schocher wrote:
>> Ok, did a "git diff v3.7.1..v3.14 ..." for drivers/mtd/nand and
>> drivers/mtd/mtd*.{c,h} and applied it with "git am -3 ..." after
>> fetching the Linux tree into my U-boot repository ... this
>> command worked now nice ... but there are subtle diffs between
>> the sources in the "copied from linux" tree and the "git am -3"
>> tree ... which did not pop up when doing a "git am -3 ...", just
>> detected them because I could do a diff between "my copied from linux"
>> version and the "git am -3 ..." created version!
>
> It looks like the 3.7.1 sync was mainly just the NAND code, not the rest
> of mtd, other than some API changes needed by the NAND code.
Yes.
> Did you find any differences in the NAND code?
IIRC, yes.
>> And I have no chance to detect this difference, when using
>> "git am -3 ..." ... it just remains in the code ...
>>
>> I vote for copying the linux files, marking U-Boot specific code
>> with __UBOOT__ ...
>
> Yes, the 3-way merge approach requires that we know where and when the
> old code came from. Unfortunately that information is not present
> outside of drivers/mtd/nand, so for those directories starting from
> scratch is reasonable (unless we can figure it out based on when the
> code was added to U-Boot...). Once that's been done, future updates can
> be done with 3-way merges.
Ok.
> I still disagree with #ifndef __UBOOT__ as it will hurt more than it
> helps with future merges.
The remove of this is not to difficult ... Tom, Wolfgang? Should I
remove?
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2014-06-25 4:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 7:15 [U-Boot] [PATCH v4 0/3] mtd, ubi, ubifs: resync with Linux-3.14 Heiko Schocher
2014-06-17 7:15 ` [U-Boot] [PATCH v4 1/3] lib, rbtree: " Heiko Schocher
2014-06-17 7:15 ` [U-Boot] [PATCH v4 2/3] lib, list_sort: add list_sort from linux 3.14 Heiko Schocher
2014-06-17 7:15 ` [U-Boot] [PATCH v4 3/3] mtd, ubi, ubifs: resync with Linux-3.14 Heiko Schocher
2014-06-17 15:54 ` [U-Boot] [PATCH v4 0/3] " Scott Wood
2014-06-18 7:55 ` Heiko Schocher
2014-06-18 21:24 ` Scott Wood
2014-06-18 21:42 ` Tom Rini
2014-06-19 10:34 ` Heiko Schocher
2014-06-19 23:45 ` Scott Wood
2014-06-20 7:59 ` Heiko Schocher
2014-06-22 6:59 ` Heiko Schocher
2014-06-22 7:36 ` Wolfgang Denk
2014-06-23 15:05 ` Tom Rini
2014-06-24 4:48 ` Heiko Schocher
2014-06-24 6:58 ` Marek Vasut
2014-06-24 14:36 ` Tom Rini
2014-06-24 14:39 ` Tom Rini
2014-06-25 4:50 ` Heiko Schocher
2014-06-24 19:19 ` Scott Wood
2014-06-25 4:56 ` Heiko Schocher [this message]
2014-06-26 7:51 ` Wolfgang Denk
2014-06-30 20:20 ` Scott Wood
2014-06-30 22:56 ` Wolfgang Denk
2014-06-30 23:09 ` Scott Wood
2014-07-01 10:45 ` Wolfgang Denk
2014-07-06 18:04 ` Wolfgang Denk
2014-07-07 16:12 ` Tom Rini
2014-07-07 17:24 ` Wolfgang Denk
2014-07-07 19:59 ` 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=53AA5662.80502@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 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.