linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	kernel-team@fb.com, akiyks@gmail.com,
	paul.heidekrueger@in.tum.de
Subject: [GIT PULL] LKMM changes for v6.1
Date: Sat, 1 Oct 2022 20:31:16 -0700	[thread overview]
Message-ID: <20221002033116.GA3513193@paulmck-ThinkPad-P17-Gen-1> (raw)

Hello, Linus,

Once the merge window opens, please pull the latest LKMM changes from:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tags/lkmm.2022.09.30a
  HEAD: be94ecf7608cc11ff46442012e710bb8fb139b99: tools/memory-model: Clarify LKMM's limitations in litmus-tests.txt (2022-08-31 05:15:31 -0700)

----------------------------------------------------------------
LKMM pull request for v6.1

This pull request includes several documentation updates.

----------------------------------------------------------------
Akira Yokosawa (2):
      docs/memory-barriers.txt: Fix confusing name of 'data dependency barrier'
      docs/memory-barriers.txt: Fixup long lines

Paul Heidekrüger (1):
      tools/memory-model: Clarify LKMM's limitations in litmus-tests.txt

 Documentation/memory-barriers.txt                 | 177 ++++++++++++----------
 tools/memory-model/Documentation/litmus-tests.txt |  37 +++--
 2 files changed, 122 insertions(+), 92 deletions(-)

             reply	other threads:[~2022-10-02  3:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-02  3:31 Paul E. McKenney [this message]
2022-10-03 17:32 ` [GIT PULL] LKMM changes for v6.1 pr-tracker-bot

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=20221002033116.GA3513193@paulmck-ThinkPad-P17-Gen-1 \
    --to=paulmck@kernel.org \
    --cc=akiyks@gmail.com \
    --cc=kernel-team@fb.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.heidekrueger@in.tum.de \
    --cc=torvalds@linux-foundation.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).