From: Jonathan Corbet <corbet@lwn.net>
To: Changbin Du <changbin.du@gmail.com>
Cc: Federico Vaga <federico.vaga@vaga.pv.it>,
Alex Shi <alexs@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Changbin Du <changbin.du@gmail.com>
Subject: Re: [PATCH] Documentation: in_irq() cleanup
Date: Fri, 13 Aug 2021 09:44:28 -0600 [thread overview]
Message-ID: <87o8a1xsbn.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210813144713.85598-1-changbin.du@gmail.com>
Changbin Du <changbin.du@gmail.com> writes:
> Replace the obsolete and ambiguos macro in_irq() with new
> macro in_hardirq().
>
> Signed-off-by: Changbin Du <changbin.du@gmail.com>
> ---
> Documentation/kernel-hacking/hacking.rst | 2 +-
> Documentation/kernel-hacking/locking.rst | 4 ++--
> Documentation/translations/it_IT/kernel-hacking/hacking.rst | 2 +-
> Documentation/translations/it_IT/kernel-hacking/locking.rst | 4 ++--
> Documentation/translations/zh_CN/kernel-hacking/hacking.rst | 2 +-
> 5 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/Documentation/kernel-hacking/hacking.rst b/Documentation/kernel-hacking/hacking.rst
> index df65c19aa7df..f514cec8e16b 100644
> --- a/Documentation/kernel-hacking/hacking.rst
> +++ b/Documentation/kernel-hacking/hacking.rst
> @@ -77,7 +77,7 @@ fast: frequently it simply acknowledges the interrupt, marks a 'software
> interrupt' for execution and exits.
>
> You can tell you are in a hardware interrupt, because
> -:c:func:`in_irq()` returns true.
> +:c:func:`in_hardirq()` returns true.
While you're in the neighborhood, can you please get rid of the :c:func:
markup? We've not needed that for some time now; simply saying
in_hardirq() is sufficient.
Thanks,
jon
next prev parent reply other threads:[~2021-08-13 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 14:47 [PATCH] Documentation: in_irq() cleanup Changbin Du
2021-08-13 15:44 ` Jonathan Corbet [this message]
2021-08-14 1:44 ` Changbin Du
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=87o8a1xsbn.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=alexs@kernel.org \
--cc=changbin.du@gmail.com \
--cc=federico.vaga@vaga.pv.it \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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