linux-kernel - Re: [PATCH v3] docs: x86: replace do_IRQ int the entry_64.rst with common

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 15 Sep 2022 11:34:56 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Tuo Cao <91tuocao@...il.com>, tglx@...utronix.de, mingo@...hat.com,
        bp@...en8.de, dave.hansen@...ux.intel.com, x86@...nel.org,
        hpa@...or.com
Cc:     linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
        91tuocao@...il.com
Subject: Re: [PATCH v3] docs: x86: replace do_IRQ int the entry_64.rst with
 common_interrupt()

Tuo Cao <91tuocao@...il.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@...il.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