All of lore.kernel.org
 help / color / mirror / Atom feed
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:50:00 +0200	[thread overview]
Message-ID: <53AA54F8.6080403@denx.de> (raw)
In-Reply-To: <20140624143922.GH9006@bill-the-cat>

Hello Tom,

Am 24.06.2014 16:39, schrieb Tom Rini:
> On Tue, Jun 24, 2014 at 06:48:27AM +0200, Heiko Schocher wrote:
>> Hello Tom,
>>
>> Am 23.06.2014 17:05, schrieb Tom Rini:
>>> On Sun, Jun 22, 2014 at 09:36:43AM +0200, Wolfgang Denk wrote:
>>>> Dear Heiko,
>>>>
>>>> In message<53A67ED9.2090705@denx.de>   you wrote:
[...]
>>> is already out, lets do (as part of testing our theories out), a follow
>>> up patch to sync up with v3.15.  And finally, I think we need, in order
>>> to keep this pain point down, sync per kernel release.
>>
>> Ok, I had prepared a v5, posting it soon.
>>
>> I try to do also to prepare a seperate sync with v3.15 patch, but give
>> me some time ... also I found a bug in current v3.16-rc1 kernel, using
>> ubi fastmap, see:
>>
>> "UBI: fix rb_tree node comparison in add_map commit buggy?"
>> http://lists.infradead.org/pipermail/linux-mtd/2014-June/054348.html
>>
>> So current v3.16-rc1 kernel could not attach a ubi volume using
>> ubi fastmap and created with a kernel not having commit
>> 604b592e6fd3c98f21435e1181ba7723ffc24715 applied ... which is
>> the case for v3.14 ... with my fixup, a v3.16-rc1 kernel could
>> again attach a v3.14 kernel or U-Boot (with my v3.14 sync patches
>> applied) created ubi volume ...
>>
>> Maybe we wait with the sync, until this is sorted out?
>
> Yes, that's fine.  Perhaps we'll end up with a sync to v3.14 series, a
> v3.15 on top of it, and then backporting your bugfix patch(es) on top of
> that.

Ok, so let us bring in the v3.14 sync in the next merge window. I try
to do some more tests with it ...

I did a fast sync with v3.15, compiled for arm, mips and powerpc
but I have to test this, and this will takes some time, I currently
not have ...

I did the sync in the following way:

- checked out in the linux tree the commit with which the U-Boot
   sync was done.

- copy all linux mtd,ubi and ubifs files to the U-Boot mtd,ubi,ubifs
   code

   -> git diff will shows all U-Boot specific changes
   -> save this patch

- now in the linux tree checked out the new commit I wanted to sync
   U-Boot with

- copy all linux mtd,ubi and ubifs files from the new linux commit
   to the U-Boot mtd,ubi,ubifs code

   - committed this for documentation only

- apply the u-boot specific changes patch now
   - fixed small errors
     This worked with some small correction very fast ...

ToDo:

   - test
   - commit and send to ML

>> To sync us with each kernel release would be a good idea, but the
>> problem would be, to find time for it ...
>
> Yes, but I think if we do it more regularly it will be better for us and
> take less time.

Definitely.

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

  reply	other threads:[~2014-06-25  4:50 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 [this message]
2014-06-24 19:19                 ` Scott Wood
2014-06-25  4:56                   ` Heiko Schocher
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=53AA54F8.6080403@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.