From: SeongJae Park <sj38.park@gmail.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: paulmck@kernel.org, corbet@lwn.net, linux-doc@vger.kernel.org,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
SeongJae Park <sjpark@amazon.de>
Subject: Re: [PATCH 0/3] memory-barriers: Apply missed changes
Date: Sat, 29 Aug 2020 10:19:50 +0200 [thread overview]
Message-ID: <20200829081950.2709-1-sj38.park@gmail.com> (raw)
In-Reply-To: <20200829080816.1440-1-sjpark@amazon.de>
Oops, I forgot adding 'From:' line in the body. This will make author and
signed-off-by mismatch. Sorry, I will send v2 soon.
Thanks,
SeongJae Park
On Sat, 29 Aug 2020 10:08:13 +0200 SeongJae Park <sj38.park@gmail.com> wrote:
> This patchset applies missed changes that should land in the
> memory-barriers.txt and its Korean translation.
>
> The patches are based on v5.9-rc2.
>
> SeongJae Park (3):
> docs/memory-barriers.txt: Fix references for DMA*.txt files
> docs/memory-barriers.txt/kokr: Remove remaining references to mmiowb()
> dics/memory-barriers.txt/kokr: Allow architecture to override the
> flush barrier
>
> Documentation/memory-barriers.txt | 8 ++---
> .../translations/ko_KR/memory-barriers.txt | 32 ++++++++++++-------
> 2 files changed, 24 insertions(+), 16 deletions(-)
>
> --
> 2.17.1
>
prev parent reply other threads:[~2020-08-29 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 8:08 [PATCH 0/3] memory-barriers: Apply missed changes SeongJae Park
2020-08-29 8:08 ` [PATCH 1/3] docs/memory-barriers.txt: Fix references for DMA*.txt files SeongJae Park
2020-08-29 8:08 ` [PATCH 2/3] docs/memory-barriers.txt/kokr: Remove remaining references to mmiowb() SeongJae Park
2020-08-29 8:08 ` [PATCH 3/3] dics/memory-barriers.txt/kokr: Allow architecture to override the flush barrier SeongJae Park
2020-08-29 8:19 ` SeongJae Park [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=20200829081950.2709-1-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=sjpark@amazon.de \
/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).