mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Tuo Cao <91tuocao@gmail.com>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
	corbet@lwn.net, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] docs: x86: replace do_IRQ int the entry_64.rst with common_interrupt
Date: Thu, 15 Sep 2022 15:41:05 +0100	[thread overview]
Message-ID: <YyM5gTgcvvFY7Oxk@casper.infradead.org> (raw)
In-Reply-To: <20220915135452.7901-1-91tuocao@gmail.com>

On Thu, Sep 15, 2022 at 09:54:52PM +0800, Tuo Cao wrote:
> 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..4f12152570e7 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

If we write common_interrupt() with the brackets, that'll get turned
into a nice link to the kernel-doc for common_interrupt().  If anyone
writes it ;-)

> +   with the interrupt number as a parameter.
>  
>   - APIC interrupts: Various special-purpose interrupts for things
>     like TLB shootdown.
> -- 
> 2.17.1
> 

      reply	other threads:[~2022-09-15 14:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15 13:54 Tuo Cao
2022-09-15 14:41 ` Matthew Wilcox [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=YyM5gTgcvvFY7Oxk@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=91tuocao@gmail.com \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --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

all inboxes | Powered by JetHome®