| 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: <CALCETrXu19aHhudTfPAr5PM05FR0xKBiSHgbubVhh6QUrHCADw@mail.gmail.com> Date: Sat, 13 Dec 2014 23:26:36 -0800 From: Andy Lutomirski <luto@...capital.net> To: Stephen Rothwell <sfr@...b.auug.org.au> Cc: "linux-next@...r.kernel.org" <linux-next@...r.kernel.org>, "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: linux-next: question about the luto-misc tree On Dec 13, 2014 10:58 PM, "Stephen Rothwell" <sfr@...b.auug.org.au> wrote: > > Hi Andy, > > The luto-misc tree seems to have a whole series of commits in it that > have just bee removed from the rcu tree ... You really have to be very > careful if you base your work on a tree that is regularly rebased. Hmm. They were there a couple days ago. Paul, what should I do about this? I only need the one NMI nesting change for the stuff in luto/next. > > I also wonder if the other commits in that tree are destined for > v3.19? If they are for v3.20, then they should not be in linux-next > until after v3.19-rc1 has been released. They're for 3.20. I'll drop the whole series from the next branch for now. --Andy > -- > Cheers, > Stephen Rothwell sfr@...b.auug.org.au -- 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