linux-kernel - Re: [PATCH] Documentation/PCI: fix spelling mistake in boot-interrupts

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] [day] [month] [year] [list]

Message-ID: <20231228234129.GA1559242@bhelgaas>
Date: Thu, 28 Dec 2023 17:41:29 -0600
From: Bjorn Helgaas <helgaas@...nel.org>
To: attreyee-muk <tintinm2017@...il.com>
Cc: bhelgaas@...gle.com, corbet@....net, linux-pci@...r.kernel.org,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [PATCH] Documentation/PCI: fix spelling mistake in
 boot-interrupts

[+cc Randy]

On Sun, Dec 24, 2023 at 12:14:13AM +0530, attreyee-muk wrote:
> Correct to “re-enabled” from “reenabled”.
> 
> Signed-off-by: Attreyee Mukherjee <tintinm2017@...il.com>

I'm fine with this either way, so I squashed this together with the
"busses" patch and they're both on pci/misc for v6.8.

> ---
>  Documentation/PCI/boot-interrupts.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/PCI/boot-interrupts.rst b/Documentation/PCI/boot-interrupts.rst
> index 2ec70121bfca..931077bb0953 100644
> --- a/Documentation/PCI/boot-interrupts.rst
> +++ b/Documentation/PCI/boot-interrupts.rst
> @@ -61,7 +61,7 @@ Conditions
>  ==========
>  
>  The use of threaded interrupts is the most likely condition to trigger
> -this problem today. Threaded interrupts may not be reenabled after the IRQ
> +this problem today. Threaded interrupts may not be re-enabled after the IRQ
>  handler wakes. These "one shot" conditions mean that the threaded interrupt
>  needs to keep the interrupt line masked until the threaded handler has run.
>  Especially when dealing with high data rate interrupts, the thread needs to
> -- 
> 2.34.1
>