public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH] Documentation/PCI: fix spelling mistake in msi-howto
Date: Thu, 28 Dec 2023 17:40:05 -0600	[thread overview]
Message-ID: <20231228234005.GA1559156@bhelgaas> (raw)
In-Reply-To: <20231223184720.25645-1-tintinm2017@gmail.com>

On Sun, Dec 24, 2023 at 12:17:20AM +0530, attreyee-muk wrote:
> Correct the spelling of "buses" from "busses" in msi-howto.rst
> 
> Signed-off-by: Attreyee Mukherjee <tintinm2017@gmail.com>

Applied with Randy's ack to pci/misc for v6.8, thanks.

> ---
>  Documentation/PCI/msi-howto.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/PCI/msi-howto.rst b/Documentation/PCI/msi-howto.rst
> index c9400f02333b..783d30b7bb42 100644
> --- a/Documentation/PCI/msi-howto.rst
> +++ b/Documentation/PCI/msi-howto.rst
> @@ -236,7 +236,7 @@ including a full 'lspci -v' so we can add the quirks to the kernel.
>  Disabling MSIs below a bridge
>  -----------------------------
>  
> -Some PCI bridges are not able to route MSIs between busses properly.
> +Some PCI bridges are not able to route MSIs between buses properly.
>  In this case, MSIs must be disabled on all devices behind the bridge.
>  
>  Some bridges allow you to enable MSIs by changing some bits in their
> -- 
> 2.34.1
> 

      parent reply	other threads:[~2023-12-28 23:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-23 18:47 [PATCH] Documentation/PCI: fix spelling mistake in msi-howto attreyee-muk
2023-12-23 19:25 ` Randy Dunlap
2023-12-28 23:40 ` 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=20231228234005.GA1559156@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=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