[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190822192132.GJ28441@linux.ibm.com>
Date: Thu, 22 Aug 2019 12:21:32 -0700
From: "Paul E. McKenney" <paulmck@...ux.ibm.com>
To: Ingo Molnar <mingo@...nel.org>
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
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.
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.
Thanx, Paul
------------------------------------------------------------------------
commit 864866f469d90bb7044a7e47b0168a2c143de4d4
Merge: cfcdef5e3046 6738ff85c3ee
Author: Paul E. McKenney <paulmck@...ux.ibm.com>
Date: Thu Aug 22 12:09:20 2019 -0700
Merge branch 'lkmm.2019.08.09a' into HEAD
lkmm.2019.08.09a: Linux-kernel memory-model updates.
Powered by blists - more mailing lists