From: Akira Yokosawa <akiyks@gmail.com>
To: Yubin Ruan <ablacktshirt@gmail.com>, perfbook@vger.kernel.org
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH] typo at Chp 7.
Date: Sat, 28 Oct 2017 00:02:19 +0900 [thread overview]
Message-ID: <bf23f56f-b4e1-48fe-821d-721457cd469e@gmail.com> (raw)
In-Reply-To: <20171027092317.GA8509@HP>
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
> of lock-based software transactional memory
> implementations~\cite{Shavit95,DaveDice2006DISC}.
> However,
> --
> 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
> .
>
And please refer to Section 1.5 of perfbook for the process of contributing
patches.
Here is what Paul told me when I submitted my first patch back in April 2016.
On 2016/04/13 1:00, Paul E. McKenney wrote:
> Akira, in the future, please do use "git format-patch" and also please
> use the Linux-kernel preferred format for referencing commits, as shown
> in the updated commit below. The idea is to use the first 12 digits of
> the SHA-1 commit ID, followed by the subject line in both quotes and
> parentheses.
You can see the archive of the thread at:
http://www.spinics.net/lists/perfbook/msg00148.html
Thanks, Akira
next prev parent reply other threads:[~2017-10-27 15:02 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 [this message]
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
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=bf23f56f-b4e1-48fe-821d-721457cd469e@gmail.com \
--to=akiyks@gmail.com \
--cc=ablacktshirt@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