linux-kernel - Re: [GIT PULL rcu/next + tools/memory-model] RCU and LKMM commits for 5.4

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

Date:   Sat, 24 Aug 2019 14:01:02 +0200
From:   Ingo Molnar <mingo@...nel.org>
To:     "Paul E. McKenney" <paulmck@...ux.ibm.com>
Cc:     rcu@...r.kernel.org, linux-kernel@...r.kernel.org,
        joel@...lfernandes.org, parri.andrea@...il.com,
        byungchul.park@....com, peterz@...radead.org, mojha@...eaurora.org,
        ice_yangxiao@....com, efremov@...ux.com, edumazet@...gle.com
Subject: Re: [GIT PULL rcu/next + tools/memory-model] RCU and LKMM commits
 for 5.4


* Paul E. McKenney <paulmck@...ux.ibm.com> wrote:

> On Thu, Aug 22, 2019 at 08:54:29PM +0200, Ingo Molnar wrote:
> 
> [ . . . ]
> 
> > Pulled into tip:core/rcu, thanks a lot Paul!
> 
> Thank you!
> 
> > The merge commit is a bit non-standard:
> > 
> >   07f038a408fb: Merge LKMM and RCU commits
> > 
> > but clear enough IMHO. Usually we try to keep this format:
> > 
> >   6c06b66e957c: Merge branch 'X' into Y
> > 
> > even for internal merge commits.
> 
> Please accept my apologies!  How about as shown below?  If this works
> for you, I will rebase my development commits on top this merge commit
> in order to make sure I don't revert back to my old format for next
> merge window.

Looks good - but I don't think we should create a new merge commit just 
for this.

> Ah, speaking of reminding me...  There is likely to be one more small RCU
> commit requested by the RISC-V guys.  If testing and review goes well,
> I will send you a pull request for it by the middle of next week.

Thanks!

	Ingo