From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Shawn Lin <shawn.lin@rock-chips.com>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: PCI: Fix typos in msi-howto.rst
Date: Sun, 28 Dec 2025 18:08:26 +0700 [thread overview]
Message-ID: <aVEPqn7votUNbrXL@archie.me> (raw)
In-Reply-To: <1766713528-173281-1-git-send-email-shawn.lin@rock-chips.com>
[-- Attachment #1: Type: text/plain, Size: 1853 bytes --]
On Fri, Dec 26, 2025 at 09:45:28AM +0800, Shawn Lin wrote:
> diff --git a/Documentation/PCI/msi-howto.rst b/Documentation/PCI/msi-howto.rst
> index 0692c9a..667ebe2 100644
> --- a/Documentation/PCI/msi-howto.rst
> +++ b/Documentation/PCI/msi-howto.rst
> @@ -98,7 +98,7 @@ function::
>
> which allocates up to max_vecs interrupt vectors for a PCI device. It
> returns the number of vectors allocated or a negative error. If the device
> -has a requirements for a minimum number of vectors the driver can pass a
> +has a requirement for a minimum number of vectors the driver can pass a
> min_vecs argument set to this limit, and the PCI core will return -ENOSPC
> if it can't meet the minimum number of vectors.
>
> @@ -127,7 +127,7 @@ not be able to allocate as many vectors for MSI as it could for MSI-X. On
> some platforms, MSI interrupts must all be targeted at the same set of CPUs
> whereas MSI-X interrupts can all be targeted at different CPUs.
>
> -If a device supports neither MSI-X or MSI it will fall back to a single
> +If a device supports neither MSI-X nor MSI it will fall back to a single
> legacy IRQ vector.
>
> The typical usage of MSI or MSI-X interrupts is to allocate as many vectors
> @@ -203,7 +203,7 @@ How to tell whether MSI/MSI-X is enabled on a device
> ----------------------------------------------------
>
> Using 'lspci -v' (as root) may show some devices with "MSI", "Message
> -Signalled Interrupts" or "MSI-X" capabilities. Each of these capabilities
> +Signaled Interrupts" or "MSI-X" capabilities. Each of these capabilities
> has an 'Enable' flag which is followed with either "+" (enabled)
> or "-" (disabled).
>
Looks good, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-12-28 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 1:45 [PATCH] Documentation: PCI: Fix typos in msi-howto.rst Shawn Lin
2025-12-26 5:41 ` Randy Dunlap
2025-12-28 11:08 ` Bagas Sanjaya [this message]
2025-12-28 16:20 ` Zenghui Yu
2025-12-29 17:24 ` Bjorn Helgaas
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=aVEPqn7votUNbrXL@archie.me \
--to=bagasdotme@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=shawn.lin@rock-chips.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;
as well as URLs for NNTP newsgroup(s).