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:	Wed, 6 Jul 2011 13:12:01 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	"Nori, Sekhar" <nsekhar@...com>
Cc:	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Nicolas Pitre <nicolas.pitre@...aro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Russell King <rmk@....linux.org.uk>
Subject: Re: Please submit platform trees for inclusion in arm-soc.git v3.1

On Wednesday 06 July 2011, Nori, Sekhar wrote:
> On Fri, Jul 01, 2011 at 23:48:14, Arnd Bergmann wrote:
> 
> > * If you currently merge your patches upstream through RMK's tree,
> >   you can keep doing so.
> 
> We currently send DaVinci patches upstream through Russell.
> This makes it look like the change applies only to those
> maintainers who were sending patches to Linus directly.
> 
> I want to make sure I read this correctly and should continue
> sending patches upstream through Russell?

You are welcome to submit patches to the arm-soc tree instead of
Russell's if you prefer to do so, either way is fine with me
at least.

The arm-soc tree was introduced mostly to reorganize the upstream
merge process for those platforms that directly send patches to
Linus, but we can also do it for everyone else.

We probably still need to try out a few things and see how it goes.
Russell also has write access to the arm-soc tree, so one of the
possible models is that you send the patches to him, but he adds
them to the arm-soc tree rather than the arm-linux one.

Russell, do you have a preference? If you want to stop merging
subarch trees into linux-arm.git, we can do that in arm-soc.git.
The idea behind my suggestion to keep using your tree was to not
change too many things at once, and we can always revisit this
question.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ