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:	Thu, 23 Feb 2012 16:54:41 +0200
From:	Ohad Ben-Cohen <>
To:	Arnd Bergmann <>
	linux-arm <>,, "Grosen, Mark" <>,
	Brian Swetland <>,
	Grant Likely <>,
	Tony Lindgren <>,
	Rusty Russell <>,
	Greg KH <>,,
	Stephen Boyd <>,
	Russell King <>,
	"Shah, Bhavin" <>, Iliyan Malchev <>,
	"Anna, Suman" <>,
	"Guzman Lugo, Fernando" <>,
	Stephen Rothwell <>,
	Loic PALLARDY <>,
	Linus Walleij <>,
	Ludovic BARRE <>,
	Michal Simek <>, "Clark, Rob" <>,
	John Williams <>,
	Saravana Kannan <>,
Subject: Re: [GIT PULL] adding rpmsg and remoteproc to 3.4

On Thu, Feb 23, 2012 at 4:31 PM, Arnd Bergmann <> wrote:
> I've looked at the code again now and pulled it into the arm-soc
> tree as the next/rpmsg branch, queued for submission to Linus in
> the 3.4 merge window. There won't be any conflicts in linux-next
> because the commits are identical,  so it doesn't matter whether
> you leave your branch in linux-next or now.  If you have updates
> on top of this branch, I can apply them directly here.
> Let's see how things go after v3.4-rc1  before we decide whether
> you want to keep sending patches to arm-soc for v3.5  as well or
> whether you just use your own branch then.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists