| 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
| ||
|
Message-Id: <201201250018.16848.rjw@sisk.pl> Date: Wed, 25 Jan 2012 00:18:16 +0100 From: "Rafael J. Wysocki" <rjw@...k.pl> To: Stephen Rothwell <sfr@...b.auug.org.au> Cc: linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>, Tejun Heo <tj@...nel.org>, Jiri Slaby <jslaby@...e.cz> Subject: Re: linux-next: Tree for Jan 24 Hi Stephen, On Tuesday, January 24, 2012, Stephen Rothwell wrote: > Hi all, > > Changes since 20120123: > > New tree: ktest > Reinstated tree: input-mt > > My fixes tree contains: > powerpc: make PSERIES_IDLE bool > > Linus' tree gained a build failure for which I applied a patch. > > The arm tree gained a conflict against Linus' tree. > > The arm-soc tree lost its conflicts but gained another against the arm > tree. > > The s5p tree gained conflicts against Linus' tree. > > The nfs tree lost its build failure. > > The sound-asoc tree lost its build failure. > > The input tree gained a build failure so I used the version from > next-20120123. > > The akpm tree lost several patches that were merged into Linus' tree. Is there any new material touching kernel/workqueue.c or kernel/freezer.c? We seem to have a freezer regression in linux-next which doesn't seem to be present in my tree. Thanks, Rafael -- 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