public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] DM, Kconfig and clang changes
Date: Tue, 15 Jul 2014 08:21:53 +0200	[thread overview]
Message-ID: <53C4C881.4050406@denx.de> (raw)
In-Reply-To: <20140714231754.GM1847@bill-the-cat>

Hello Tom,

Am 15.07.2014 01:17, schrieb Tom Rini:
> On Mon, Jul 14, 2014 at 11:20:31PM +0200, Wolfgang Denk wrote:
>> Dear Tom,
>>
>> In message<20140714172225.GF1847@bill-the-cat>  you wrote:
>>>
>>> So the release is out, and I want to make sure that some of these big
>>> changes get as much testing as we can.
>>
>> Please also keep Heiko's MTD/UBI/UBIFS update in mind!
>
> Yes, that however is blocked on (a) fixing of some kernel issue he found

This fix is accepted from Artem, see:

http://git.infradead.org/ubifs-2.6.git/commit/e9110361a9a4e258b072b14bd44eb78cf11453cb

This patch is only necessary in u-boot, if we update to linux v3.16
as there is the bug in v3.16.

> with fastmap, iirc and (b) a follow-up patch doing another re-sync to
> show that in theory his approach is sound and with sufficient care can
> avoid the automerge problems Scott is (legitmately) worried about.

I wasn;t aware of, that you block the mtd/ubi/ubifs patches until I did
such a rebase to v3.15 ... so I try to do this ASAP.

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-07-15  6:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 17:22 [U-Boot] DM, Kconfig and clang changes Tom Rini
2014-07-14 17:26 ` Simon Glass
2014-07-14 17:48   ` Tom Rini
2014-07-14 21:20 ` Wolfgang Denk
2014-07-14 23:17   ` Tom Rini
2014-07-15  6:21     ` Heiko Schocher [this message]
2014-07-16 11:26 ` Masahiro Yamada
2014-07-17 22:17 ` Jeroen Hofstee
2014-07-29 11:10 ` Masahiro Yamada
2014-07-29 12:03   ` Albert ARIBAUD
2014-07-30  1:57     ` Masahiro Yamada

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=53C4C881.4050406@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox