From: Bjorn Helgaas <helgaas@kernel.org>
To: attreyee-muk <tintinm2017@gmail.com>
Cc: bhelgaas@google.com, corbet@lwn.net, linux-pci@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH] Documentation/PCI: fix spelling mistake in boot-interrupts
Date: Thu, 28 Dec 2023 17:41:29 -0600 [thread overview]
Message-ID: <20231228234129.GA1559242@bhelgaas> (raw)
In-Reply-To: <20231223184412.25598-1-tintinm2017@gmail.com>
[+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@gmail.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
>
prev parent reply other threads:[~2023-12-28 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-23 18:44 [PATCH] Documentation/PCI: fix spelling mistake in boot-interrupts attreyee-muk
2023-12-23 19:28 ` Randy Dunlap
2023-12-23 22:09 ` Jonathan Corbet
2023-12-28 23:41 ` Bjorn Helgaas [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=20231228234129.GA1559242@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=tintinm2017@gmail.com \
/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