From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: pierre Kuo <vichy.kuo@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 1/2] locking: fix typo
Date: Thu, 2 Nov 2017 15:51:17 -0700 [thread overview]
Message-ID: <20171102225117.GE3624@linux.vnet.ibm.com> (raw)
In-Reply-To: <1509605869-8186-1-git-send-email-vichy.kuo@gmail.com>
On Thu, Nov 02, 2017 at 02:57:48PM +0800, pierre Kuo wrote:
> From: Pierre Kuo <vichy.kuo@gmail.com>
>
> In 7.1.1.2 Local Locking Hierarchies, below left parenthesis seems
> better to be comma.
>
> "before invoking the comparison function
> (which is unknown code from qsort()’s perspective,"
> ^^^ change it as comma.
>
> Signed-off-by: Pierre Kuo <vichy.kuo@gmail.com>
I queued and pushed both, thank you!
On the patch below, I interchanged the comma with the preceding space
character.
Thanx, Paul
> ---
> locking/locking.tex | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/locking/locking.tex b/locking/locking.tex
> index 12a0240..5921f50 100644
> --- a/locking/locking.tex
> +++ b/locking/locking.tex
> @@ -327,7 +327,7 @@ But the first thread holds Lock~C, so the second thread's call to
> Lock~B, resulting in deadlock.
>
> In contrast, if \co{qsort()} releases Lock~C before invoking the
> -comparison function (which is unknown code from \co{qsort()}'s perspective,
> +comparison function ,which is unknown code from \co{qsort()}'s perspective,
> then deadlock is avoided as shown in
> Figure~\ref{fig:lock:Local Locking Hierarchy for qsort()}.
>
> --
> 1.9.1
>
> --
> 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
>
next prev parent reply other threads:[~2017-11-02 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 6:57 [PATCH 1/2] locking: fix typo pierre Kuo
2017-11-02 6:57 ` [PATCH 2/2] SMPdesign: " pierre Kuo
2017-11-02 22:51 ` Paul E. McKenney [this message]
2017-11-03 13:23 ` [PATCH 1/2] locking: " pierre kuo
2017-11-03 14:02 ` Paul E. McKenney
2017-11-03 14:41 ` pierre kuo
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=20171102225117.GE3624@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=perfbook@vger.kernel.org \
--cc=vichy.kuo@gmail.com \
/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