mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
	colin.king@canonical.com, grandmaster@al2klimov.de,
	joel@joelfernandes.org, madhuparnabhowmik10@gmail.com,
	neeraju@codeaurora.org, paul.gortmaker@windriver.com,
	qiang.zhang@windriver.com, rdunlap@infradead.org,
	tklauser@distanz.ch, weiyongjun1@huawei.com, kernel-team@fb.com
Subject: Re: [GIT PULL tip/core/rcu] RCU commits for v5.10
Date: Fri, 9 Oct 2020 08:27:08 +0200	[thread overview]
Message-ID: <20201009062708.GB9972@gmail.com> (raw)
In-Reply-To: <20200914174607.GA12722@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/20200831175419.GA31013@paulmck-ThinkPad-P72
> 
> 2.	Miscellaneous fixes.
> 
> 	https://lore.kernel.org/lkml/20200831180050.GA32590@paulmck-ThinkPad-P72
> 
> 3.	Torture-test updates.
> 
> 	https://lore.kernel.org/lkml/20200831180348.GA416@paulmck-ThinkPad-P72
> 
> 4.	New smp_call_function() torture test.
> 
> 	https://lore.kernel.org/lkml/20200831180731.GA582@paulmck-ThinkPad-P72
> 
> 5.	Strict grace periods for KASAN.  The point of this series is to find
> 	RCU-usage bugs, so the corresponding new RCU_STRICT_GRACE_PERIOD
> 	Kconfig option depends on both DEBUG_KERNEL and RCU_EXPERT, and is
> 	further disabled by dfefault.  Finally, the help text includes
> 	a goodly list of scary caveats.
> 
> 	https://lore.kernel.org/lkml/20200831181101.GA950@paulmck-ThinkPad-P72
> 
> 6.	Debugging for smp_call_function().
> 
> 	https://lore.kernel.org/lkml/20200831181356.GA1224@paulmck-ThinkPad-P72

>  57 files changed, 1582 insertions(+), 421 deletions(-)

Pulled into tip:core/rcu, thanks a lot Paul!

	Ingo

      reply	other threads:[~2020-10-09  6:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14 17:46 Paul E. McKenney
2020-10-09  6:27 ` Ingo Molnar [this message]

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=20201009062708.GB9972@gmail.com \
    --to=mingo@kernel.org \
    --cc=colin.king@canonical.com \
    --cc=grandmaster@al2klimov.de \
    --cc=joel@joelfernandes.org \
    --cc=kernel-team@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=madhuparnabhowmik10@gmail.com \
    --cc=neeraju@codeaurora.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=paulmck@kernel.org \
    --cc=qiang.zhang@windriver.com \
    --cc=rcu@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=tklauser@distanz.ch \
    --cc=weiyongjun1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome