From: "Paul E. McKenney" <paulmck@kernel.org>
To: Elad Lahav <e2lahav@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] locking: fix small typo
Date: Thu, 6 Oct 2022 06:00:06 -0700 [thread overview]
Message-ID: <20221006130006.GU4196@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <20220930014636.429996-1-e2lahav@gmail.com>
On Thu, Sep 29, 2022 at 09:46:36PM -0400, Elad Lahav wrote:
> Signed-off-by: Elad Lahav <e2lahav@gmail.com>
Good eyes! Queued and pushed, thank you!
Thanx, Paul
> ---
> locking/locking.tex | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/locking/locking.tex b/locking/locking.tex
> index 45a12caa..032bd13d 100644
> --- a/locking/locking.tex
> +++ b/locking/locking.tex
> @@ -1473,7 +1473,7 @@ Should readers be allowed to continue to acquire the lock, possibly
> starving the writer?
> Similarly, suppose that a writer holds the lock and that a large number
> of both readers and writers are waiting to acquire the lock.
> -When the current writer release the lock, should it be given to a reader
> +When the current writer releases the lock, should it be given to a reader
> or to another writer?
> If it is given to a reader, how many readers should be allowed to acquire
> the lock before the next writer is permitted to do so?
> --
> 2.25.1
>
prev parent reply other threads:[~2022-10-06 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 1:46 [PATCH] locking: fix small typo Elad Lahav
2022-10-06 13:00 ` 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=20221006130006.GU4196@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=e2lahav@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).