All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 0/3] formal/dyntickrcu: Followup changes
Date: Mon, 8 Apr 2019 11:42:50 -0700	[thread overview]
Message-ID: <20190408184250.GW14111@linux.ibm.com> (raw)
In-Reply-To: <36421da6-4c59-597a-660f-f7ddf1d8835c@gmail.com>

On Tue, Apr 09, 2019 at 12:44:20AM +0900, Akira Yokosawa wrote:
> Hi Paul,
> 
> This is a followup patch set relative to the workaround patch
> in this mail thread ("formal/dyntickrcu: Mitigate ugliness around
> tall inline snippets").
> 
> Looks like you have not pushed it yet, though.

You are right, I did miss that step!  Fixed.

> It turns out that I misunderstood the working of \AtBeginEnvironment{}
> command, and patch #1 fixes the way to redefine VerbatimN environment.
> I wanted to add a Fixes: tag, but I don't have the commit id, so
> I put a stub of "xxxxxxxxxxxx" in the change log. Can you replace it
> with the actual commit id?

Done!

> Patches #2 and #3 add references to the git commits of the fixes to
> bugs in preemptive RCU found by verification. The actual changes were
> a little bit different from what are presented in inline snippets,
> but I left the snippets as are.  As they are more than a decade
> old, adding references should help the context look more real.

I reworked #2 a bit to place the new citations in time order (along
with another that I had misplaced).

Queued and this time really pushed!  ;-)  Thank you!!!

						Thanx, Paul

>         Thanks, Akira
> -- 
> Akira Yokosawa (3):
>   formal/dyntickrcu: Fix the way to redefine VerbatimN
>   RCU.bib: Add entries of git commits of dyntickrcu fixes
>   formal/dyntickrcu: Cite git commits of dyntickrcu fixes
> 
>  bib/RCU.bib           | 22 ++++++++++++++++++++++
>  formal/dyntickrcu.tex | 12 ++++--------
>  perfbook.tex          |  5 ++++-
>  3 files changed, 30 insertions(+), 9 deletions(-)
> 
> -- 
> 2.17.1
> 
> 


      parent reply	other threads:[~2019-04-08 18:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-06  0:31 [PATCH] formal/dyntickrcu: Mitigate ugliness of tall inline snippets Akira Yokosawa
2019-04-06  2:05 ` Paul E. McKenney
2019-04-08 15:44 ` [PATCH 0/3] formal/dyntickrcu: Followup changes Akira Yokosawa
2019-04-08 15:46   ` [PATCH 1/3] formal/dyntickrcu: Fix the way to redefine VerbatimN Akira Yokosawa
2019-04-08 15:47   ` [PATCH 2/3] RCU.bib: Add entries of git commits of dyntickrcu fixes Akira Yokosawa
2019-04-08 15:48   ` [PATCH 3/3] formal/dyntickrcu: Cite " Akira Yokosawa
2019-04-08 18:42   ` 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=20190408184250.GW14111@linux.ibm.com \
    --to=paulmck@linux.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.