From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
joel@joelfernandes.org, parri.andrea@gmail.com,
byungchul.park@lge.com, peterz@infradead.org,
mojha@codeaurora.org, ice_yangxiao@163.com, efremov@linux.com,
edumazet@google.com
Subject: Re: [GIT PULL rcu/next + tools/memory-model] RCU and LKMM commits for 5.4
Date: Thu, 22 Aug 2019 12:21:32 -0700 [thread overview]
Message-ID: <20190822192132.GJ28441@linux.ibm.com> (raw)
In-Reply-To: <20190822185429.GA110910@gmail.com>
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@linux.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.
next prev parent reply other threads:[~2019-08-22 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 15:18 [GIT PULL rcu/next + tools/memory-model] RCU and LKMM commits for 5.4 Paul E. McKenney
2019-08-22 18:54 ` Ingo Molnar
2019-08-22 19:21 ` Paul E. McKenney [this message]
2019-08-24 12:01 ` Ingo Molnar
2019-08-24 13:32 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190822192132.GJ28441@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=byungchul.park@lge.com \
--cc=edumazet@google.com \
--cc=efremov@linux.com \
--cc=ice_yangxiao@163.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mojha@codeaurora.org \
--cc=parri.andrea@gmail.com \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).