From: Andrea Parri <andrea.parri@amarulasolutions.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Kees Cook <keescook@chromium.org>,
Elena Reshetova <elena.reshetova@intel.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrea Parri <andrea.parri@amarulasolutions.com>
Subject: [PATCH] Documentation: refcount-vs-atomic: Update reference to LKMM doc.
Date: Fri, 4 May 2018 23:11:49 +0200 [thread overview]
Message-ID: <1525468309-5310-1-git-send-email-andrea.parri@amarulasolutions.com> (raw)
The LKMM project has moved to 'tools/memory-model/'.
Signed-off-by: Andrea Parri <andrea.parri@amarulasolutions.com>
---
Documentation/core-api/refcount-vs-atomic.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/core-api/refcount-vs-atomic.rst b/Documentation/core-api/refcount-vs-atomic.rst
index 83351c258cdb9..322851bada167 100644
--- a/Documentation/core-api/refcount-vs-atomic.rst
+++ b/Documentation/core-api/refcount-vs-atomic.rst
@@ -17,7 +17,7 @@ in order to help maintainers validate their code against the change in
these memory ordering guarantees.
The terms used through this document try to follow the formal LKMM defined in
-github.com/aparri/memory-model/blob/master/Documentation/explanation.txt
+tools/memory-model/Documentation/explanation.txt.
memory-barriers.txt and atomic_t.txt provide more background to the
memory ordering in general and for atomic operations specifically.
--
2.7.4
next reply other threads:[~2018-05-04 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 21:11 Andrea Parri [this message]
2018-05-04 21:13 ` Kees Cook
2018-05-04 21:37 ` Andrea Parri
2018-05-08 20:52 ` Jonathan Corbet
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=1525468309-5310-1-git-send-email-andrea.parri@amarulasolutions.com \
--to=andrea.parri@amarulasolutions.com \
--cc=corbet@lwn.net \
--cc=elena.reshetova@intel.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®