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  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 Nov 2009 11:44:01 +0200
From:	Tomi Valkeinen <>
To:	Stephen Rothwell <>,
	ext Tony Lindgren <>
Cc:	"" <>,
	"" <>,
	"" <>
Subject: Re: [PATCH 00/19] OMAP: DSS2 v5 intro

On Wed, 2009-11-11 at 09:45 +0100, Valkeinen Tomi (Nokia-D/Helsinki)
> On Tue, 2009-11-10 at 13:40 +0100, Artem Bityutskiy wrote:
> > Tomi,
> > 
> > could you please kindly ask Stephen (CCed) to include the DSS2 tree into
> > linux-next, because you are going to merge it the next merge window, and
> > there does not seem to be any blocker for this.
> > 
> > Being in linux-next for a while is really important.
> Stephen, would this be possible? DSS2 driver is rather big piece of
> code, even if it's quite isolated, so it would be nice to have it in
> linux-next.
> What does it require from me? A git tree, obviously, but what should it
> be based on?

Ah, I just realized that DSS2 patches depend on patches from Tony's
tree. I guess I should base my tree on top of some Tony's tree that is
going to linux-next?


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