From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] future/formalregress: Fix staccato of 'been'
Date: Sat, 7 Apr 2018 16:41:05 -0700 [thread overview]
Message-ID: <20180407234105.GN3948@linux.vnet.ibm.com> (raw)
In-Reply-To: <b1a921af-ee58-8dfd-cda2-0523b89c66b0@gmail.com>
On Sun, Apr 08, 2018 at 12:23:05AM +0900, Akira Yokosawa wrote:
> >From b4f82853b7425a54e5ac898b91660fff66e4190b Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Sat, 7 Apr 2018 23:14:24 +0900
> Subject: [PATCH] future/formalregress: Fix staccato of 'been'
>
> Also remove redundant "v" in "v4.17".
>
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
Good eyes, applied and pushed, thank you!
Thanx, Paul
> ---
> Hi Paul,
>
> If you prefer "v4.17", "version" can be removed instead.
>
> Thanks, Akira
> --
> future/formalregress.tex | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/future/formalregress.tex b/future/formalregress.tex
> index dd37ec8..8402da1 100644
> --- a/future/formalregress.tex
> +++ b/future/formalregress.tex
> @@ -116,7 +116,7 @@ In contrast, one of the great strengths of PPCMEM and \co{herd}
> is their detailed modeling of various CPU families memory models,
> including x86, ARM, Power, and, in the case of \co{herd},
> even a Linux-kernel memory model~\cite{Alglave:2018:FSC:3173162.3177156},
> -which has been been accepted into version v4.17 of
> +which has been accepted into version 4.17 of
> the Linux kernel.
>
> The \co{cbmc} and Nidhugg tools provide some ability to select
> --
> 2.7.4
>
prev parent reply other threads:[~2018-04-07 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-07 15:23 [PATCH] future/formalregress: Fix staccato of 'been' Akira Yokosawa
2018-04-07 23:41 ` 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=20180407234105.GN3948@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.