From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 0/8] Fixups for together/ directory
Date: Tue, 11 Oct 2016 00:31:08 -0700 [thread overview]
Message-ID: <20161011073108.GB29518@linux.vnet.ibm.com> (raw)
In-Reply-To: <20161010230738.14452-1-sj38.park@gmail.com>
On Tue, Oct 11, 2016 at 08:07:30AM +0900, SeongJae Park wrote:
> This patchset fixes few trivial problems under together/ directory that found
> by Korean translation work.
>
> SeongJae Park (8):
> together: Add missing NBSPs for line numbers
> together: Fix a wrong code line quotation
> together: Fix wrong function name quotations
> together: Add a missing comma
> together: Append `()` suffix to function name quotation
> together: Fix a wrong field citation
> together: Fix a contextual typo
> together: Improve struct field quotation readability
>
> together/applyrcu.tex | 14 +++++++-------
> together/refcnt.tex | 10 +++++-----
> 2 files changed, 12 insertions(+), 12 deletions(-)
Queued and pushed, thank you!
Thanx, Paul
prev parent reply other threads:[~2016-10-11 7:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 23:07 [PATCH 0/8] Fixups for together/ directory SeongJae Park
2016-10-10 23:07 ` [PATCH 1/8] together: Add missing NBSPs for line numbers SeongJae Park
2016-10-10 23:07 ` [PATCH 2/8] together: Fix a wrong code line quotation SeongJae Park
2016-10-10 23:07 ` [PATCH 3/8] together: Fix wrong function name quotations SeongJae Park
2016-10-10 23:07 ` [PATCH 4/8] together: Add a missing comma SeongJae Park
2016-10-10 23:07 ` [PATCH 5/8] together: Append `()` suffix to function name quotation SeongJae Park
2016-10-10 23:07 ` [PATCH 6/8] together: Fix a wrong field citation SeongJae Park
2016-10-10 23:07 ` [PATCH 7/8] together: Fix a contextual typo SeongJae Park
2016-10-10 23:07 ` [PATCH 8/8] together: Improve struct field quotation readability SeongJae Park
2016-10-11 7:31 ` Paul E. McKenney [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=20161011073108.GB29518@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=perfbook@vger.kernel.org \
--cc=sj38.park@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.