From: Will Deacon <will@kernel.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Akira Yokosawa <akiyks@gmail.com>,
"Paul E. McKenney" <paulmck@linux.ibm.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Boqun Feng <boqun.feng@gmail.com>,
Andrea Parri <parri.andrea@gmail.com>,
Nicholas Piggin <npiggin@gmail.com>,
David Howells <dhowells@redhat.com>,
Daniel Lustig <dlustig@nvidia.com>,
Joel Fernandes <joel@joelfernandes.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [RFC PATCH -lkmm] docs/memory-barriers: Fix inconsistent name of 'data dependency barrier'
Date: Thu, 9 Jun 2022 16:03:39 +0100 [thread overview]
Message-ID: <20220609150339.GA3289@willie-the-truck> (raw)
In-Reply-To: <Yp9h4Cmo0UNZp6xD@rowland.harvard.edu>
On Tue, Jun 07, 2022 at 10:34:08AM -0400, Alan Stern wrote:
> On Tue, Jun 07, 2022 at 02:34:33PM +0100, Will Deacon wrote:
> > Alternatively, maybe we should be removing the historical stuff from the
> > document altogether if it's no longer needed. We don't have any occurrences
> > of read_barrier_depends() anymore, so why confuse people with it?
>
> How about relegating discussion of these barriers to a special
> "historical" or "niche architecture" section of the document? In a
> separate patch, of course.
That would work, perhaps with a little bit of commentary to say that it's
no longer relevent to the kernel sources and is provided for information
only.
Will
prev parent reply other threads:[~2022-06-09 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 4:15 [RFC PATCH -lkmm] docs/memory-barriers: Fix inconsistent name of 'data dependency barrier' Akira Yokosawa
2022-05-28 13:57 ` Alan Stern
2022-06-07 13:34 ` Will Deacon
2022-06-07 14:34 ` Alan Stern
2022-06-08 2:00 ` Akira Yokosawa
2022-06-09 15:07 ` Will Deacon
2022-06-09 15:03 ` Will Deacon [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=20220609150339.GA3289@willie-the-truck \
--to=will@kernel.org \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=joel@joelfernandes.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
/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).