linux-kernel - Re: linux-next: manual merge of the v4l-dvb 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]

Date:	Wed, 11 Jan 2012 08:58:00 -0800
From:	Olof Johansson <olof@...om.net>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Nicolas Ferre <nicolas.ferre@...el.com>,
	Guennadi Liakhovetski <g.liakhovetski@....de>,
	Mauro Carvalho Chehab <mchehab@...radead.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Linus <torvalds@...ux-foundation.org>,
	linux-arm-kernel@...ts.infradead.org,
	"Wu, Josh" <Josh.wu@...el.com>
Subject: Re: linux-next: manual merge of the v4l-dvb tree with the arm-soc tree

On Wed, Jan 11, 2012 at 8:46 AM, Arnd Bergmann <arnd@...db.de> wrote:

> Agreed. How about if you rebase the few other (non-ISI) patches that
> I had in arm-soc onto v3.2 and send me an updated pull request so
> I can send them on? There's no reason to hold them up.

Just to clarify: The late/* branch that I was referring to in my email
would just then contain the ISI patches, the rest would be in the
above branch.


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