From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH v2] Fix labeling of appendix and section
Date: Mon, 9 Apr 2018 14:58:48 -0700 [thread overview]
Message-ID: <20180409215848.GS3948@linux.vnet.ibm.com> (raw)
In-Reply-To: <36926eec-8b4a-76e9-15a1-f4fc354875cc@gmail.com>
On Tue, Apr 10, 2018 at 06:32:32AM +0900, Akira Yokosawa wrote:
> On 2018/04/09 10:21:33 -0700, Paul E. McKenney wrote:
> > On Tue, Apr 10, 2018 at 12:44:58AM +0900, Akira Yokosawa wrote:
> >> >From d9d064c4aac8758ccaa435444ff0e60a16a9d6d2 Mon Sep 17 00:00:00 2001
> >> From: Akira Yokosawa <akiyks@gmail.com>
> >> Date: Tue, 10 Apr 2018 00:30:08 +0900
> >> Subject: [PATCH v2] Fix labeling of appendix and section
> >>
> >> These are a couple of labels which don't match the current
> >> context due to movement to/from appendix.
> >>
> >> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
> >> ---
> >> Change from v1:
> >> Fixed typo in commit log.
> >
> > Good eyes, applied and queued, thank you! I changed one additional
> > "appendix" to section, please see below for the updated commit, and
> > please let me know if I messed anything up.
>
> Ah, I knew I missed something ;-)
> I wouldn't be surprised if there were other similar cases.
Nor would I. ;-)
Thanx, Paul
> Thanks, Akira
>
> >
> > Thanx, Paul
> >
> > ------------------------------------------------------------------------
> >
> > commit 15e646185e3f404c6d84af4947e598278e53d22d
> > Author: Akira Yokosawa <akiyks@gmail.com>
> > Date: Tue Apr 10 00:30:08 2018 +0900
> >
> > Fix labeling of appendix and section
> >
> > These are a couple of labels which don't match the current
> > context due to movement to/from appendix.
> >
> > Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
> > Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> >
> > diff --git a/appendix/toyrcu/toyrcu.tex b/appendix/toyrcu/toyrcu.tex
> > index a796401e8d0c..c0a45a85ca03 100644
> > --- a/appendix/toyrcu/toyrcu.tex
> > +++ b/appendix/toyrcu/toyrcu.tex
> > @@ -2,7 +2,7 @@
> >
> > \QuickQuizChapter{chp:app:``Toy'' RCU Implementations}{``Toy'' RCU Implementations}
> >
> > -The toy RCU implementations in this section are designed not for
> > +The toy RCU implementations in this appendix are designed not for
> > high performance, practicality, or any kind of production use,\footnote{
> > However, production-quality user-level RCU implementations
> > are available~\cite{MathieuDesnoyers2009URCU,MathieuDesnoyers2012URCU}.}
> > @@ -15,7 +15,7 @@ Chapters~\ref{chp:Introduction},
> > and~\ref{chp:Deferred Processing}
> > for even these toy RCU implementations to be easily understandable.
> >
> > -This section provides a series of RCU implementations in order of
> > +This appendix provides a series of RCU implementations in order of
> > increasing sophistication, from the viewpoint of solving the
> > existence-guarantee problem.
> > Section~\ref{sec:app:toyrcu:Lock-Based RCU} presents a rudimentary
> > diff --git a/memorder/memorder.tex b/memorder/memorder.tex
> > index 079840425ca3..40fe3a4919f0 100644
> > --- a/memorder/memorder.tex
> > +++ b/memorder/memorder.tex
> > @@ -4179,7 +4179,7 @@ dependencies.
> >
> > \section{Hardware Specifics}
> > \label{sec:memorder:Hardware Specifics}
> > -\OriginallyPublished{Appendix}{sec:memorder:Hardware Specifics}{Memory-Barrier Instructions For Specific CPUs}{Linux Journal}{PaulMcKenney2005i,PaulMcKenney2005j}
> > +\OriginallyPublished{Section}{sec:memorder:Hardware Specifics}{Memory-Barrier Instructions For Specific CPUs}{Linux Journal}{PaulMcKenney2005i,PaulMcKenney2005j}
> >
> > \begin{table*}[tbh]
> > \rowcolors{4}{}{lightgray}
> >
>
prev parent reply other threads:[~2018-04-09 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d3ea21c4-ba6f-46e3-15da-cd35d450b59d@gmail.com>
[not found] ` <c07a5add-15e7-0c0a-b2ef-af96bbde7059@gmail.com>
2018-04-09 17:21 ` [PATCH v2] Fix labeling of appendix and section Paul E. McKenney
2018-04-09 21:32 ` Akira Yokosawa
2018-04-09 21:58 ` 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=20180409215848.GS3948@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akiyks@gmail.com \
--cc=perfbook@vger.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