linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: manfred@colorfullife.com, stern@rowland.harvard.edu,
	parri.andrea@gmail.com, will@kernel.org, peterz@infradead.org,
	boqun.feng@gmail.com, npiggin@gmail.com, dhowells@redhat.com,
	j.alglave@ucl.ac.uk, luc.maranget@inria.fr, akiyks@gmail.com,
	dlustig@nvidia.com, joel@joelfernandes.org, tglx@linutronix.de,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	kernel-team@fb.com
Subject: Re: [GIT PULL lkmm] LKMM commits for v5.15
Date: Wed, 18 Aug 2021 08:41:40 +0200	[thread overview]
Message-ID: <YRyrpPhEdRCnRmlq@gmail.com> (raw)
In-Reply-To: <20210812002535.GA405507@paulmck-ThinkPad-P17-Gen-1>


* Paul E. McKenney <paulmck@kernel.org> wrote:

> Hello, Ingo!
> 
> This pull request contains changes for the Linux-kernel memory model
> (LKMM).  These changes focus on documentation, providing additional
> examples and use cases.  These have been posted to LKML:
> 
> https://lore.kernel.org/lkml/20210721211003.869892-1-paulmck@kernel.org/
> https://lore.kernel.org/lkml/20210721211003.869892-2-paulmck@kernel.org/
> https://lore.kernel.org/lkml/20210721211003.869892-3-paulmck@kernel.org/
> https://lore.kernel.org/lkml/20210721211003.869892-4-paulmck@kernel.org/
> 
> They have been exposed to -next and the kernel test robot, not that these
> services do all that much for documentation changes.
> 
> The following changes since commit 2734d6c1b1a089fb593ef6a23d4b70903526fe0c:
> 
>   Linux 5.14-rc2 (2021-07-18 14:13:49 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git lkmm
> 
> for you to fetch changes up to 87859a8e3f083bd57b34e6a962544d775a76b15f:
> 
>   tools/memory-model: Document data_race(READ_ONCE()) (2021-07-27 11:48:55 -0700)
> 
> ----------------------------------------------------------------
> Manfred Spraul (1):
>       tools/memory-model: Heuristics using data_race() must handle all values
> 
> Paul E. McKenney (3):
>       tools/memory-model: Make read_foo_diagnostic() more clearly diagnostic
>       tools/memory-model: Add example for heuristic lockless reads
>       tools/memory-model: Document data_race(READ_ONCE())
> 
>  .../memory-model/Documentation/access-marking.txt  | 151 ++++++++++++++++++---
>  1 file changed, 135 insertions(+), 16 deletions(-)

Pulled into tip:locking/debug, thanks a lot Paul!

	Ingo

      reply	other threads:[~2021-08-18  6:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12  0:25 [GIT PULL lkmm] LKMM commits for v5.15 Paul E. McKenney
2021-08-18  6:41 ` 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=YRyrpPhEdRCnRmlq@gmail.com \
    --to=mingo@kernel.org \
    --cc=akiyks@gmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=dlustig@nvidia.com \
    --cc=j.alglave@ucl.ac.uk \
    --cc=joel@joelfernandes.org \
    --cc=kernel-team@fb.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luc.maranget@inria.fr \
    --cc=manfred@colorfullife.com \
    --cc=npiggin@gmail.com \
    --cc=parri.andrea@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=stern@rowland.harvard.edu \
    --cc=tglx@linutronix.de \
    --cc=will@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).