From: Jonathan Corbet <corbet@lwn.net>
To: Stephen Boyd <swboyd@chromium.org>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: locking: Add 'need' to hardirq section
Date: Wed, 18 Mar 2020 08:55:42 -0600 [thread overview]
Message-ID: <20200318085542.081ca750@lwn.net> (raw)
In-Reply-To: <20200318054425.111928-1-swboyd@chromium.org>
On Tue, 17 Mar 2020 22:44:25 -0700
Stephen Boyd <swboyd@chromium.org> wrote:
> Add the missing word to make this sentence read properly.
>
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
> ---
> Documentation/kernel-hacking/locking.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/kernel-hacking/locking.rst b/Documentation/kernel-hacking/locking.rst
> index a8518ac0d31d..9850c1e52607 100644
> --- a/Documentation/kernel-hacking/locking.rst
> +++ b/Documentation/kernel-hacking/locking.rst
> @@ -263,7 +263,7 @@ by a hardware interrupt on another CPU. This is where
> interrupts on that cpu, then grab the lock.
> :c:func:`spin_unlock_irq()` does the reverse.
>
> -The irq handler does not to use :c:func:`spin_lock_irq()`, because
> +The irq handler does not need to use :c:func:`spin_lock_irq()`, because
Please take out the :c:func: stuff while you're at it, we don't need that
anymore. Just spin_lock_irq() will do the right thing.
Thanks,
jon
next prev parent reply other threads:[~2020-03-18 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 5:44 [PATCH] docs: locking: Add 'need' to hardirq section Stephen Boyd
2020-03-18 14:55 ` Jonathan Corbet [this message]
2020-03-18 17:31 ` Stephen Boyd
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=20200318085542.081ca750@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swboyd@chromium.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 NNTP newsgroup(s).