From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org, rcu@vger.kernel.org, arnd@arndb.de,
bigeasy@linutronix.de, elver@google.com, ethp@qq.com,
frederic@kernel.org, jbi.octave@gmail.com,
joel@joelfernandes.org, lihaoliang@google.com,
madhuparnabhowmik10@gmail.com, mchehab+huawei@kernel.org,
peter.enderborg@sony.com, rdunlap@infradead.org,
richard.weiyang@linux.alibaba.com, urezki@gmail.com,
zou_wei@huawei.com, tglx@linutronix.de
Subject: Re: [GIT PULL tip/core/rcu] RCU commits for v5.9
Date: Fri, 31 Jul 2020 00:20:57 +0200 [thread overview]
Message-ID: <20200730222057.GA423051@gmail.com> (raw)
In-Reply-To: <20200714172701.GA31369@paulmck-ThinkPad-P72>
* Paul E. McKenney <paulmck@kernel.org> wrote:
> Hello, Ingo!
>
> This pull request contains the following changes:
>
> 1. Documentation updates.
>
> https://lore.kernel.org/lkml/20200623000923.GA25047@paulmck-ThinkPad-P72
>
> 2. Miscellaneous fixes.
>
> https://lore.kernel.org/lkml/20200623002128.GA25456@paulmck-ThinkPad-P72
>
> 3. kfree_rcu updates.
>
> https://lore.kernel.org/lkml/20200624201200.GA28901@paulmck-ThinkPad-P72
>
> 4. RCU tasks updates.
>
> https://lore.kernel.org/lkml/20200623002423.GA25869@paulmck-ThinkPad-P72
>
> 5. Read-side scalability tests.
>
> https://lore.kernel.org/lkml/20200623002941.GA26089@paulmck-ThinkPad-P72
>
> 6. SRCU updates.
>
> https://lore.kernel.org/lkml/20200623003310.GA26539@paulmck-ThinkPad-P72
>
> 7. Torture-test updates.
>
> https://lore.kernel.org/lkml/20200623003731.GA26717@paulmck-ThinkPad-P72
>
> All of these have been subjected to the kbuild test robot and -next
> testing, and are available in the git repository based on v5.8-rc3 at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git for-mingo
>
> for you to fetch changes up to 13625c0a4074d3bab61b1dc70a828b574255f339:
>
> Merge branches 'doc.2020.06.29a', 'fixes.2020.06.29a', 'kfree_rcu.2020.06.29a', 'rcu-tasks.2020.06.29a', 'scale.2020.06.29a', 'srcu.2020.06.29a' and 'torture.2020.06.29a' into HEAD (2020-06-29 12:03:15 -0700)
> 61 files changed, 2395 insertions(+), 680 deletions(-)
Pulled into tip:core/rcu, thanks a lot Paul!
I assume the fix Uladzislau Rezki is working on will resolve Sebastian
Andrzej Siewior's objections?
Thanks,
Ingo
next prev parent reply other threads:[~2020-07-30 22:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 17:27 [GIT PULL tip/core/rcu] RCU commits for v5.9 Paul E. McKenney
2020-07-14 18:14 ` Sebastian Andrzej Siewior
2020-07-14 18:27 ` Paul E. McKenney
2020-07-14 19:02 ` Sebastian Andrzej Siewior
2020-07-14 20:06 ` Uladzislau Rezki
2020-07-14 20:53 ` Paul E. McKenney
2020-07-15 7:15 ` Sebastian Andrzej Siewior
2020-07-14 20:17 ` Uladzislau Rezki
2020-07-15 14:12 ` Paul E. McKenney
2020-07-30 22:20 ` Ingo Molnar [this message]
2020-07-30 23:15 ` 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=20200730222057.GA423051@gmail.com \
--to=mingo@kernel.org \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=elver@google.com \
--cc=ethp@qq.com \
--cc=frederic@kernel.org \
--cc=jbi.octave@gmail.com \
--cc=joel@joelfernandes.org \
--cc=lihaoliang@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=madhuparnabhowmik10@gmail.com \
--cc=mchehab+huawei@kernel.org \
--cc=paulmck@kernel.org \
--cc=peter.enderborg@sony.com \
--cc=rcu@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=richard.weiyang@linux.alibaba.com \
--cc=tglx@linutronix.de \
--cc=urezki@gmail.com \
--cc=zou_wei@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.