linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: akiyks@gmail.com, bigeasy@linutronix.de, elver@google.com,
	frederic@kernel.org, joel@joelfernandes.org, julia@ni.com,
	mchehab+huawei@kernel.org, neeraju@codeaurora.org,
	paul.gortmaker@windriver.com, peterz@infradead.org,
	qiang.zhang@windriver.com, swood@redhat.com, urezki@gmail.com,
	w@1wt.eu, wangqing@vivo.com, linux-kernel@vger.kernel.org,
	rcu@vger.kernel.org, kernel-team@fb.com, tglx@linutronix.de
Subject: Re: [GIT PULL tip/core/rcu] RCU, LKMM, and KCSAN commits for v5.12
Date: Fri, 12 Feb 2021 07:07:05 -0800	[thread overview]
Message-ID: <20210212150705.GO2743@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20210212123109.GB2185387@gmail.com>

On Fri, Feb 12, 2021 at 01:31:09PM +0100, Ingo Molnar wrote:
> 
> * Paul E. McKenney <paulmck@kernel.org> wrote:
> 
> > Hello, Ingo!
> > 
> > This pull request contains changes for RCU, KCSAN, LKMM, and nolibc.
> > You can pull the entire group using branch for-mingo.  Or, if you prefer,
> > you can pull them separately, using for-mingo-rcu to pull the RCU changes,
> > for-mingo-kcsan to pull the KCSAN changes, for-mingo-lkmm to pull the
> > LKMM changes, and for-mingo-nolibc to pull the noclib changes.
> > 
> > The changes are as follows:
> > 
> > 1.	RCU updates (for-mingo-rcu):
> 
> > 4.	Fixes to nolibc that allows it to run once again on ARMv8.
> >	https://lore.kernel.org/lkml/20210121072031.23777-1-w@1wt.eu/
> 
> Pulled these two into tip:core/rcu - as nolibc's main (only?) usecase 
> within the kernel is torture-testing.
> 
> > 2.	Kernel concurrency sanitizer (KCSAN) updates from Marco Elver.
> > 	https://lore.kernel.org/lkml/20210106173323.GA23292@paulmck-ThinkPad-P72/
> 
> > 3.	Linux-kernel memory model (LKMM) updates.
> > 	https://lore.kernel.org/lkml/20210106173548.GA23664@paulmck-ThinkPad-P72/
> 
> Pulled these two into tip:locking/core.

Thank you, Ingo!  In the future, I will group nolibc with RCU.  But there
has to be something other than RCU that needs it.  I will take a look. ;-)

							Thanx, Paul

  reply	other threads:[~2021-02-12 15:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28  1:04 [GIT PULL tip/core/rcu] RCU, LKMM, and KCSAN commits for v5.12 Paul E. McKenney
2021-02-12 12:31 ` Ingo Molnar
2021-02-12 15:07   ` Paul E. McKenney [this message]
2021-02-13 12:36     ` Willy Tarreau
2021-02-13 16:44       ` "Single user mode" initrd [ Was: [GIT PULL tip/core/rcu] RCU, LKMM, and KCSAN commits for v5.12 ] 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=20210212150705.GO2743@paulmck-ThinkPad-P72 \
    --to=paulmck@kernel.org \
    --cc=akiyks@gmail.com \
    --cc=bigeasy@linutronix.de \
    --cc=elver@google.com \
    --cc=frederic@kernel.org \
    --cc=joel@joelfernandes.org \
    --cc=julia@ni.com \
    --cc=kernel-team@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mingo@kernel.org \
    --cc=neeraju@codeaurora.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=peterz@infradead.org \
    --cc=qiang.zhang@windriver.com \
    --cc=rcu@vger.kernel.org \
    --cc=swood@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=urezki@gmail.com \
    --cc=w@1wt.eu \
    --cc=wangqing@vivo.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;
as well as URLs for NNTP newsgroup(s).