From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 0/3] Adjust labeling of chapter and appendix
Date: Wed, 16 Nov 2016 07:10:46 -0800 [thread overview]
Message-ID: <20161116151046.GG3612@linux.vnet.ibm.com> (raw)
In-Reply-To: <74e04f98-adb1-cd0d-7b6f-bbd550a6ea56@gmail.com>
On Wed, Nov 16, 2016 at 09:57:08AM +0900, Akira Yokosawa wrote:
> >From 08d86c4db893e5b689c4d051b765006ce507c45c Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Wed, 16 Nov 2016 09:43:11 +0900
> Subject: [PATCH 0/3] Adjust labeling of chapter and appendix
>
> Hi Paul,
>
> "bib" cleanups aside, I noticed a few inconsistent labeling of
> "formal" and "whymemorybarriers".
> This patch set adjusts them.
Good catches, applied, thank you!
Thanx, Paul
> Thanks, Akira
>
> ---
> Akira Yokosawa (3):
> formal: Promote \OriginallyPublieshed macro to Chapter
> appendix/ack: Adjust labeling in 'Reviewers' section
> treewide: Adjust labeling of 'formal'
>
> appendix/ack/ack.tex | 8 ++++----
> appendix/rcuimpl/rcupreempt.tex | 2 +-
> debugging/debugging.tex | 2 +-
> defer/toyrcu.tex | 2 +-
> formal/dyntickrcu.tex | 2 +-
> formal/formal.tex | 2 +-
> 6 files changed, 9 insertions(+), 9 deletions(-)
>
> --
> 2.7.4
>
next prev parent reply other threads:[~2016-11-16 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 0:57 [PATCH 0/3] Adjust labeling of chapter and appendix Akira Yokosawa
2016-11-16 0:58 ` [PATCH 1/3] formal: Promote \OriginallyPublieshed macro to Chapter Akira Yokosawa
2016-11-16 0:59 ` [PATCH 2/3] appendix/ack: Adjust labeling in 'Reviewers' section Akira Yokosawa
2016-11-16 1:01 ` [PATCH 3/3] treewide: Adjust labeling of 'formal' Akira Yokosawa
2016-11-16 15:10 ` Paul E. McKenney [this message]
2016-11-16 22:26 ` [PATCH 0/3] Adjust labeling of chapter and appendix Akira Yokosawa
2016-11-17 17:38 ` Paul E. McKenney
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=20161116151046.GG3612@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 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.