From: Jonathan Corbet <corbet@lwn.net>
To: Tuo Cao <91tuocao@gmail.com>,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
91tuocao@gmail.com
Subject: Re: [PATCH v3] docs: x86: replace do_IRQ int the entry_64.rst with common_interrupt()
Date: Thu, 15 Sep 2022 11:34:56 -0600 [thread overview]
Message-ID: <87fsgsee2n.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220915150155.9908-1-91tuocao@gmail.com>
Tuo Cao <91tuocao@gmail.com> writes:
> do_IRQ has been replaced by common_interrupt in commit
> fa5e5c409213 ("x86/entry: Use idtentry for interrupts").
>
> Signed-off-by: Tuo Cao <91tuocao@gmail.com>
> ---
> Documentation/x86/entry_64.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/x86/entry_64.rst b/Documentation/x86/entry_64.rst
> index e433e08f7018..0afdce3c06f4 100644
> --- a/Documentation/x86/entry_64.rst
> +++ b/Documentation/x86/entry_64.rst
> @@ -33,8 +33,8 @@ Some of these entries are:
> - interrupt: An array of entries. Every IDT vector that doesn't
> explicitly point somewhere else gets set to the corresponding
> value in interrupts. These point to a whole array of
> - magically-generated functions that make their way to do_IRQ with
> - the interrupt number as a parameter.
> + magically-generated functions that make their way to common_interrupt()
> + with the interrupt number as a parameter.
>
> - APIC interrupts: Various special-purpose interrupts for things
> like TLB shootdown.
So why have you sent a "v3" the same day? It doesn't look like anything
has changed...?
Thanks,
jon
next prev parent reply other threads:[~2022-09-15 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 15:01 [PATCH v3] docs: x86: replace do_IRQ int the entry_64.rst with common_interrupt() Tuo Cao
2022-09-15 17:34 ` Jonathan Corbet [this message]
2022-09-16 14:50 ` tuo cao
2022-09-21 19:56 ` Jonathan Corbet
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=87fsgsee2n.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=91tuocao@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 NNTP newsgroup(s).