linux-kernel - Re: [GIT PULL rcu/next] RCU commits for 4.15

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] [day] [month] [year] [list]

Message-Id: <20180103173820.GS7829@linux.vnet.ibm.com>
Date:   Wed, 3 Jan 2018 09:38:20 -0800
From:   "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:     Ingo Molnar <mingo@...nel.org>
Cc:     linux-kernel@...r.kernel.org, rostedt@...dmis.org,
        rakib.mullick@...il.com, sj38.park@...il.com, dave@...olabs.net,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [GIT PULL rcu/next] RCU commits for 4.15

On Wed, Jan 03, 2018 at 02:17:17PM +0100, Ingo Molnar wrote:
> 
> * Paul E. McKenney <paulmck@...ux.vnet.ibm.com> wrote:

[ . . . ]

> Assuming that the subject line wanted to say v4.16, not v4.15 (which would be 
> really scary set of changes so late in the v4.15 cycle), I have pulled these into 
> tip:core/rcu, thanks Paul!

You are correct, it is for the upcoming merge window, not for current
mainline.

Hmmm...  Maybe this is why I have thus far succeeded in writing 2018
rather than 2017?  ;-)

							Thanx, Paul