From: Yubin Ruan <ablacktshirt@gmail.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
perfbook@vger.kernel.org
Subject: Re: [PATCH] typo at Chp 7.
Date: Sat, 28 Oct 2017 17:14:35 +0800 [thread overview]
Message-ID: <20171028091432.GB5742@HP> (raw)
In-Reply-To: <7589cd7e-208c-6f8c-dd98-c587904c0b14@gmail.com>
On Sat, Oct 28, 2017 at 10:53:31AM +0900, Akira Yokosawa wrote:
> On 2017/10/28 17:06, Yubin Ruan wrote:
> > On Fri, Oct 27, 2017 at 04:05:49PM -0700, Paul E. McKenney wrote:
> >> On Sat, Oct 28, 2017 at 12:02:19AM +0900, Akira Yokosawa wrote:
> >>> Hi Yubin,
> >>>
> >>> On 2017/10/27 18:23, Yubin Ruan wrote:
> >>>> Hi paul,
> >>>>
> >>>> I finish chapter 7 and find some typo. Fixed in the patch below.
> >>>>
> >>>> Yubin
> >>>>
> >>>> diff --git a/locking/locking-existence.tex b/locking/locking-existence.tex
> >>>> index 9fcbbf9..c7c4ae8 100644
> >>>> --- a/locking/locking-existence.tex
> >>>> +++ b/locking/locking-existence.tex
> >>>> @@ -174,7 +174,7 @@ 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
> >>>> +These problems can be solved. In fact, such solutions form the basis
> >>>
> >>> I'd suggest the following:
> >>>
> >>> +These problems can be solved, in fact, and such solutions form the basis
> >>
> >> How about this?
> >>
> >> Not only can these problems be solved, but the solutions also
> >> form the basis of lock-based software transactional memory [...].
> >
> > Thanks for your suggestion. I think Akira's approach looks more nature to me.
> > So, let me finish this little patch ;-)
>
> Well, I think Paul's suggestion is much clearer.
>
> BTW Yubin, your mail has a date field indicating it came from the near future:
>
> > Date: Sat, 28 Oct 2017 16:06:40 +0800
>
> May be time zone setting issue?
What time zone should I set?
Yubin
> > --------------------------------------------------------------------------
> >>From aede1ef2fe8c5213c8aec9581192c5915e69010c Mon Sep 17 00:00:00 2001
> > From: Yubin Ruan <ablacktshirt@gmail.com>
> > Date: Sat, 28 Oct 2017 16:00:43 +0800
> > Subject: [PATCH] locking: a typo fixed
> >
> > Signed-off-by: Yubin Ruan <ablacktshirt@gmail.com>
> > ---
> > locking/locking-existence.tex | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/locking/locking-existence.tex b/locking/locking-existence.tex
> > index 9fcbbf9..2be69d8 100644
> > --- a/locking/locking-existence.tex
> > +++ b/locking/locking-existence.tex
> > @@ -174,7 +174,7 @@ 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
> > +These problems can be solved, in fact, and such solutions form the basis
> > of lock-based software transactional memory
> > implementations~\cite{Shavit95,DaveDice2006DISC}.
> > However,
> >
>
next prev parent reply other threads:[~2017-10-28 9:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 9:23 [PATCH] typo at Chp 7 Yubin Ruan
2017-10-27 9:33 ` Yubin Ruan
2017-10-27 15:18 ` Akira Yokosawa
2017-10-27 23:24 ` Paul E. McKenney
2017-10-28 13:37 ` Yubin Ruan
2017-10-28 13:17 ` Paul E. McKenney
2017-10-28 22:29 ` Akira Yokosawa
2017-10-29 3:19 ` Paul E. McKenney
2017-10-29 0:15 ` Yubin Ruan
2017-10-29 3:20 ` Paul E. McKenney
2017-10-27 23:32 ` Paul E. McKenney
2017-10-27 15:02 ` Akira Yokosawa
2017-10-27 23:05 ` Paul E. McKenney
2017-10-28 8:06 ` Yubin Ruan
2017-10-28 1:53 ` Akira Yokosawa
2017-10-28 9:14 ` Yubin Ruan [this message]
2017-10-28 9:16 ` Yubin Ruan
2017-10-28 13:23 ` Paul E. McKenney
2017-10-28 23:09 ` Akira Yokosawa
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=20171028091432.GB5742@HP \
--to=ablacktshirt@gmail.com \
--cc=akiyks@gmail.com \
--cc=paulmck@linux.vnet.ibm.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