linux-kernel - Re: linux-next: manual merge of the akpm tree with the arm-soc tree

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]

Message-ID: <20130312133225.GG12700@titan.lakedaemon.net>
Date:	Tue, 12 Mar 2013 09:32:25 -0400
From:	Jason Cooper <jason@...edaemon.net>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Andrew Lunn <andrew@...n.ch>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Jingoo Han <jg1.han@...sung.com>, linux-kernel@...r.kernel.org,
	linux-next@...r.kernel.org, Olof Johansson <olof@...om.net>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: linux-next: manual merge of the akpm tree with the arm-soc tree

On Tue, Mar 12, 2013 at 12:48:24PM +0000, Arnd Bergmann wrote:
> On Tuesday 12 March 2013, Jason Cooper wrote:
> > I chose to keep them together to maintain bisectability.  Either you
> > have all of the fix (you landed on this branch), or you don't.  Was this
> > the correct decision in this case, or did I miss something?
> 
> I think you don't need to worry about bisection in this case, especially
> as you mentioned that 3.8 is already broken.
> 
> From all I can tell, these are four separate fixes, and you want to have
> all of them get merged, but applying just one of them will not make the
> state of the kernel tree any worse than what it is before the patches.

Ok, thanks for the clarification.  I'll ease up on the bisectability
requirement for fixes in the future.

thx,

Jason.
--
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/