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] [day] [month] [year] [list]

Date:	Fri, 04 Feb 2011 12:38:01 -0800
From:	David Brown <davidb@...eaurora.org>
To:	Nicolas Pitre <nico@...xnic.net>
Cc:	Daniel Walker <dwalker@...eaurora.org>, Greg KH <greg@...ah.com>,
	Russell King <rmk@....linux.org.uk>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>,
	Stepan Moskovchenko <stepanm@...eaurora.org>,
	linux-arm-msm@...r.kernel.org
Subject: Re: linux-next: manual merge of the msm tree with the arm tree

On Fri, Feb 04 2011, Nicolas Pitre wrote:

> Maybe this would be nicer to Russell and others performing wide ranging 
> changes to the ARM code if the msm tree was more visible downstream, and 
> potentially help to avoid making a mountain out of a mole hill.

Currently, the msm tree is in linux-next, and the URL is in the
MAINTAINER's file.  The only want to make it more visible would be to
give frequent pull requests to RMK, which would create extra work for
him.  I think I just need to come up with the right balance of how often
to give the tree to RMK.

David

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
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/