linux-kernel - Re: [PATCH 00/19] First HREF Device Tree enablement patch-set

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 10 Sep 2012 01:41:52 -0700
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Lee Jones <lee.jones@...aro.org>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	STEricsson_nomadik_linux@...t.st.com, linus.walleij@...ricsson.com
Subject: Re: [PATCH 00/19] First HREF Device Tree enablement patch-set

On Fri, Sep 7, 2012 at 3:58 PM, Arnd Bergmann <arnd@...db.de> wrote:
> On Friday 07 September 2012, Lee Jones wrote:
>> (...)
>> Linus wanted to keep changes to the Device Tree and changes
>> in platform code separate, which is my reason for submitting
>> all of my changes to date that way.
> (...)
> Linus: What is the reason you want to see the commits split up
> like this?

Basically that was at a point when we were changing a lot of
subsystem trees with DT patches that were merged in out-of-order
fashion.

Then it's better to have the DT changes to be pushed
separately at the end of the merge window after all subtrees
with dependent changes are merged. (Or even in the next merge
window if there is no hurry, but we always seem to be in a hurry...)

If all the changes are in the same subtree (like ARM SoC with
ACKs from all over the place where needed) you can do it
this way instead, and I agree it looks better.

So basically two different merge strategies get you to split
patches differently.

Any way is fine with me, do as Arnd suggests if all is going
in through ARM SoC.

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/