From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] memorder: Adjust epigraph style
Date: Fri, 25 Aug 2017 21:38:10 -0700 [thread overview]
Message-ID: <20170826043810.GX11320@linux.vnet.ibm.com> (raw)
In-Reply-To: <f084b0ef-0b12-1cfd-b057-f4f79ed3b75e@gmail.com>
On Sat, Aug 26, 2017 at 12:01:17PM +0900, Akira Yokosawa wrote:
> >From a7cccce3ad3d4c93d20d7c5cb05de931f5e67733 Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Sat, 26 Aug 2017 11:57:45 +0900
> Subject: [PATCH] memorder: Adjust epigraph style
>
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
Good catch, fixed!
Thanx, Paul
> ---
> memorder/memorder.tex | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/memorder/memorder.tex b/memorder/memorder.tex
> index bde5a45..c571e49 100644
> --- a/memorder/memorder.tex
> +++ b/memorder/memorder.tex
> @@ -4,7 +4,7 @@
> \OriginallyPublished{Chapter}{chp:memorder:Memory Ordering}{Linux Kernel Memory Barriers}{kernel.org}{Howells2009membartxt}
> \OriginallyPublished{Chapter}{chp:memorder:Memory Ordering}{A formal kernel memory-ordering model}{Linux Weekly News}{JadeAlglave2017LWN-LKMM-1,JadeAlglave2017LWN-LKMM-2}
> %
> -\epigraph{The art of progress is to preserve order amid change and to preserve change amid order.}{Alfred North Whitehead}
> +\Epigraph{The art of progress is to preserve order amid change and to preserve change amid order.}{\emph{Alfred North Whitehead}}
>
> Causality and sequencing are deeply intuitive, and hackers often
> tend to have a much stronger grasp of these concepts than does
> --
> 2.7.4
>
prev parent reply other threads:[~2017-08-26 4:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-26 3:01 [PATCH] memorder: Adjust epigraph style Akira Yokosawa
2017-08-26 4:38 ` 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=20170826043810.GX11320@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.