[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jKHb8-P-Y2ecnH9sd6vWhY9cWPfow1Lx_gzRMbHWusRXg@mail.gmail.com>
Date: Fri, 4 May 2018 14:13:59 -0700
From: Kees Cook <keescook@...omium.org>
To: Andrea Parri <andrea.parri@...rulasolutions.com>
Cc: Jonathan Corbet <corbet@....net>,
Elena Reshetova <elena.reshetova@...el.com>,
linux-doc@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Documentation: refcount-vs-atomic: Update reference to
LKMM doc.
On Fri, May 4, 2018 at 2:11 PM, Andrea Parri
<andrea.parri@...rulasolutions.com> wrote:
> The LKMM project has moved to 'tools/memory-model/'.
>
> Signed-off-by: Andrea Parri <andrea.parri@...rulasolutions.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.
Will this get linkified by rst ?
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists