linux-kernel - Re: linux-next: manual merge of the msm tree with the arm 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: <alpine.LFD.2.00.1010181714090.2764@xanadu.home>
Date:	Mon, 18 Oct 2010 17:17:54 -0400 (EDT)
From:	Nicolas Pitre <nico@...xnic.net>
To:	Daniel Walker <dwalker@...o99.com>
Cc:	Arnd Bergmann <arnd@...db.de>, Russell King <rmk@....linux.org.uk>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jeremy Kerr <jeremy.kerr@...onical.com>,
	Jeff Ohlstein <johlstei@...eaurora.org>
Subject: Re: linux-next: manual merge of the msm tree with the arm tree

On Mon, 18 Oct 2010, Daniel Walker wrote:

> I guess your assuming I send my pull request after Russell's, which
> isn't necessarily true, and I'd rather not have that dependency if I
> don't have to. 

Look, we're not establishing a straight rule here -- just figuring out a 
way to move forward.  What we're asking you to do is either ask RMK to 
pull your tree now, or wait until RMK's tree has hit mainline so you can 
pull Linus' tree and fix the issue yourself before asking Linus to pull, 
or whatever.  Is some collaboration on your part for this particular 
issue too much to ask for?

Nicolas
--
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/