From: Jonathan Corbet <corbet@lwn.net>
To: SeongJae Park <sj38.park@gmail.com>
Cc: paulmck@kernel.org, SeongJae Park <sjpark@amazon.de>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] Documentation: Fix trivial nits
Date: Wed, 5 Feb 2020 10:22:29 -0700 [thread overview]
Message-ID: <20200205102229.3497c3b1@lwn.net> (raw)
In-Reply-To: <20200131205237.29535-1-sj38.park@gmail.com>
On Fri, 31 Jan 2020 21:52:32 +0100
SeongJae Park <sj38.park@gmail.com> wrote:
> his patchset fixes trivial nits in the documentations.
>
> SeongJae Park (5):
> docs/locking: Fix outdated section names
> docs/ko_KR/howto: Insert missing dots
> Documentation/ko_KR/howto: Update broken web addresses
> Documentation/ko_KR/howto: Update a broken link
> Documentation/memory-barriers: Fix typos
>
> Documentation/locking/spinlocks.rst | 4 ++--
> Documentation/memory-barriers.txt | 8 ++++----
> Documentation/translations/ko_KR/howto.rst | 10 +++++-----
> 3 files changed, 11 insertions(+), 11 deletions(-)
OK, I've applied parts 1, 3, and 4. It looks like Paul picked up #5, and
I had separate comments on #2.
Thanks,
jon
prev parent reply other threads:[~2020-02-05 17:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 20:52 SeongJae Park
2020-01-31 20:52 ` [PATCH 1/5] docs/locking: Fix outdated section names SeongJae Park
2020-01-31 20:52 ` [PATCH 2/5] docs/ko_KR/howto: Insert missing dots SeongJae Park
2020-02-05 17:15 ` Jonathan Corbet
2020-02-06 0:12 ` SeongJae Park
2020-01-31 20:52 ` [PATCH 3/5] Documentation/ko_KR/howto: Update broken web addresses SeongJae Park
2020-01-31 20:52 ` [PATCH 4/5] Documentation/ko_KR/howto: Update a broken link SeongJae Park
2020-01-31 20:52 ` [PATCH 5/5] Documentation/memory-barriers: Fix typos SeongJae Park
2020-01-31 21:23 ` Paul E. McKenney
2020-02-05 17:22 ` Jonathan Corbet [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=20200205102229.3497c3b1@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=sj38.park@gmail.com \
--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
all inboxes | Powered by JetHome®