Discussions of the Parallel Programming book
 help / color / mirror / Atom feed
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] advsync: Typo fix and vertical spacing tweaks
Date: Sat, 16 Apr 2016 20:36:52 -0700	[thread overview]
Message-ID: <20160417033652.GJ3687@linux.vnet.ibm.com> (raw)
In-Reply-To: <5711F2CF.1030907@gmail.com>

On Sat, Apr 16, 2016 at 05:07:43PM +0900, Akira Yokosawa wrote:
> >From e9f9f2126a24841bb19970292716819f0300872b Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiysw@gmail.com>
> Date: Sat, 16 Apr 2016 16:48:19 +0900
> Subject: [PATCH 0/3] advsync: Typo fix and vertical spacing tweaks
> 
> As I mentioned earlier, I tweaked vertical spacings in the
> `Guarantees` subsection. This series also fixes a typo I made
> in the previous patch. It also adds necessary blank lines in the
> latex source of the `What Can You Trust?` subsection.
> 
> Akira Yokosawa (3):
>   advsync: Fix a trivial typo
>   advsync: Add necessary blank lines around minipages
>   advsync: Tweak vertical spacing around code snippets
> 
>  advsync/memorybarriers.tex | 44 ++++++++++++++------------------------------
>  1 file changed, 14 insertions(+), 30 deletions(-)

Nice!

Queued and pushed.

							Thanx, Paul


      parent reply	other threads:[~2016-04-17  3:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-16  8:07 [PATCH 0/3] advsync: Typo fix and vertical spacing tweaks Akira Yokosawa
2016-04-16  8:11 ` [PATCH 1/3] advsync: Fix a trivial typo Akira Yokosawa
2016-04-16  8:14 ` [PATCH 2/3] advsync: Add necessary blank lines around minipages Akira Yokosawa
2016-04-16  8:17 ` [PATCH 3/3] advsync: Tweak vertical spacing around code snippets Akira Yokosawa
2016-04-17  3:36 ` 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=20160417033652.GJ3687@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