From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Parav Pandit <parav@nvidia.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, paulmck@kernel.org, akiyks@gmail.com,
dlustig@nvidia.com, joel@joelfernandes.org, corbet@lwn.net,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] locking/memory-barriers.txt: Improve documentation for writel() usage
Date: Thu, 15 Sep 2022 19:16:23 +0700 [thread overview]
Message-ID: <6698eda3-977b-902f-ba23-89cfd674c121@gmail.com> (raw)
In-Reply-To: <20220915050106.650813-1-parav@nvidia.com>
On 9/15/22 12:01, Parav Pandit wrote:
> The cited commit [1] describes that when using writel(), explcit wmb()
> is not needed. However, it should have said that dma_wmb() is not
> needed.
>
> Hence update the example to be more accurate that matches the current
> implementation and document section of dma_wmb()/dma_rmb().
>
> [1] commit 5846581e3563 ("locking/memory-barriers.txt: Fix broken DMA vs. MMIO ordering example")
Just say the blamed commit without using numbered references.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-09-15 12:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 5:01 [PATCH] locking/memory-barriers.txt: Improve documentation for writel() usage Parav Pandit
2022-09-15 12:16 ` Bagas Sanjaya [this message]
2022-09-15 12:35 ` Parav Pandit
2022-09-15 12:37 ` Arnd Bergmann
2022-09-15 14:18 ` Parav Pandit
2022-09-15 15:16 ` Arnd Bergmann
2022-09-15 16:35 ` Parav Pandit
2022-09-15 18:38 ` Arnd Bergmann
2022-09-23 15:55 ` Parav Pandit
2022-09-23 18:40 ` Arnd Bergmann
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=6698eda3-977b-902f-ba23-89cfd674c121@gmail.com \
--to=bagasdotme@gmail.com \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=j.alglave@ucl.ac.uk \
--cc=joel@joelfernandes.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=parav@nvidia.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--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