public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
	corbet@lwn.net, linux-doc@vger.kernel.org,
	linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] docs/memory-barriers.txt: Add a missed closing parenthesis
Date: Mon, 10 Oct 2022 19:47:38 -0700	[thread overview]
Message-ID: <20221011024738.24510-1-sj@kernel.org> (raw)
In-Reply-To: <20221009183723.52037-1-sj@kernel.org>

On Sun, 9 Oct 2022 18:37:23 +0000 SeongJae Park <sj@kernel.org> wrote:

> Hi Paul,
> 
> On Sun, 9 Oct 2022 04:10:00 -0700 "Paul E. McKenney" <paulmck@kernel.org> wrote:
> 
> > On Sat, Oct 08, 2022 at 10:49:25AM -0700, SeongJae Park wrote:
> > > Description of io_stop_wc(), which added by commit d5624bb29f49
> > > ("asm-generic: introduce io_stop_wc() and add implementation for
> > > ARM64"), have unclosed parenthesis.  This commit closes it.
> > > 
> > > Fixes: d5624bb29f49 ("asm-generic: introduce io_stop_wc() and add implementation for ARM64")
> > > Signed-off-by: SeongJae Park <sj@kernel.org>
> > 
> > I have pulled this in, good eyes, and thank you!
> 
> Thank you for quick reply :)
> 
> > 
> > On the other three, we have traditionally asked for an ack from a
> > Korean speaker.  Do we still feel the need to do this?
> 
> I have asked review of the patches to my friend.  I'm unsure if my friend could
> do that in a timely manner, as my friend could also be busy.  Let's wait and
> see.

Thankfully, my friend gave me a feedback for improving the patch.  He has some
mailing tools issue, so I'm saying this instead.  I will post next version of
the translations patches soon.


Thanks,
SJ

> 
> IMHO, such review is not essential for this kind of incremental document
> updates, as I'd prefer making the doc up-to-date even if it contains some
> trivial errors, as long as the history is well manged and therefore such errors
> could be fixed later with good explanations.
> 
> 
> Thanks,
> SJ
> 
> [...]
> 

  reply	other threads:[~2022-10-11  2:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08 17:49 [PATCH 0/4] docs/memory-barriers.txt: Fix nits and update Korean translation SeongJae Park
2022-10-08 17:49 ` [PATCH 1/4] docs/memory-barriers.txt: Add a missed closing parenthesis SeongJae Park
2022-10-09  2:04   ` Bagas Sanjaya
2022-10-09 11:10   ` Paul E. McKenney
2022-10-09 18:37     ` SeongJae Park
2022-10-11  2:47       ` SeongJae Park [this message]
2022-10-08 17:49 ` [PATCH 2/4] docs/memory-barriers.txt/kokr: introduce io_stop_wc() and add implementation for ARM64 SeongJae Park
2022-10-08 17:49 ` [PATCH 3/4] docs/memory-barriers.txt/kokr: Add memory barrier dma_mb() SeongJae Park
2022-10-08 17:49 ` [PATCH 4/4] docs/memory-barriers.txt/kokr: Fix confusing name of 'data dependency barrier' SeongJae Park

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=20221011024738.24510-1-sj@kernel.org \
    --to=sj@kernel.org \
    --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 \
    /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