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
| ||
|
Date: Thu, 21 Jul 2011 17:25:45 +0930 From: Rusty Russell <rusty@...tcorp.com.au> To: Jonathan Cameron <jic23@....ac.uk> Cc: Stephen Rothwell <sfr@...b.auug.org.au>, Greg Ungerer <gerg@...pgear.com>, Jonas Bonn <jonas@...thpole.se>, linux-next@...r.kernel.org, linux-kernel@...r.kernel.org, Greg Ungerer <gerg@...inux.org>, Geert Uytterhoeven <geert@...ux-m68k.org> Subject: Re: linux-next: manual merge of the rr tree with the tree On Tue, 19 Jul 2011 12:27:42 +0100, Jonathan Cameron <jic23@....ac.uk> wrote: > On 07/07/11 02:07, Rusty Russell wrote: > > On Thu, 7 Jul 2011 10:24:32 +1000, Stephen Rothwell <sfr@...b.auug.org.au> wrote: > >> Hi all, > > .... > >>> Acked-by: Greg Ungerer <gerg@...inux.org> > >> > >> OK, so now someone just has to remember to apply it (or tell Linus, or > >> fix up the trees) during the merge window. That person probably won't > >> be me (since I will not be online next week (assuming Linus follows > >> through and opens the merge window next week). > > > > I'm travelling next week too, so m68k will probably get merged first, > > and hence I'll roll in this fix myself. > > > > Thanks, > > Rusty. > Rusty? > > If not I'm happy to take on adapting this to meet everyone's requirements. It's trivial code... just please send to Linus first day of merge window, and when I rebase I'll fix this up. Thanks, Rusty. -- 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