From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Yubin Ruan <ablacktshirt@gmail.com>
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH] locking: Fix syntactic ambiguity
Date: Sat, 28 Oct 2017 20:27:49 -0700 [thread overview]
Message-ID: <20171029032749.GD3659@linux.vnet.ibm.com> (raw)
In-Reply-To: <0eb6e2e3-e193-3109-7794-fcdf10a3045b@gmail.com>
On Sun, Oct 29, 2017 at 09:01:57AM +0800, Yubin Ruan wrote:
> >From c8a3ed4cc54d322dd107e4842837851943784666 Mon Sep 17 00:00:00 2001
> From: Yubin Ruan <ablacktshirt@gmail.com>
> Date: Sun, 29 Oct 2017 08:40:31 +0800
> Subject: [PATCH] locking: Fix syntactic ambiguity
>
> Acked-by: Akira Yokosawa <akiyks@gmail.com>
> Suggested-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> Signed-off-by: Yubin Ruan <ablacktshirt@gmail.com>
Applied, thank you both!
Yubin, whatever you did to generate and send this patch works just fine,
thank you! ;-)
Thanx, Paul
> ---
> locking/locking-existence.tex | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/locking/locking-existence.tex b/locking/locking-existence.tex
> index 9fcbbf9..6340734 100644
> --- a/locking/locking-existence.tex
> +++ b/locking/locking-existence.tex
> @@ -174,8 +174,8 @@ single partitionable data structure such as the hash table shown in the
> figure, it can be problematic if a given data element can be a member
> of multiple hash tables or given more-complex data structures such
> as trees or graphs.
> -These problems can be solved, in fact, such solutions form the basis
> -of lock-based software transactional memory
> +Not only can these problems be solved, but the solutions also form
> +the basis of lock-based software transactional memory
> implementations~\cite{Shavit95,DaveDice2006DISC}.
> However,
> Chapter~\ref{chp:Deferred Processing}
> --
> 2.7.4
> --
> To unsubscribe from this list: send the line "unsubscribe perfbook" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2017-10-29 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 1:01 [PATCH] locking: Fix syntactic ambiguity Yubin Ruan
2017-10-29 3:27 ` 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=20171029032749.GD3659@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=ablacktshirt@gmail.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