From: Bjorn Helgaas <helgaas@kernel.org>
To: Zenghui Yu <yuzenghui@huawei.com>
Cc: corbet@lwn.net, linux-pci@vger.kernel.org,
linux-doc@vger.kernel.or, linux-kernel@vger.kernel.org,
wanghaibin.wang@huawei.com, Andrew Murray <andrew.murray@arm.com>
Subject: Re: [PATCH v2] Documentation: PCI: msi-howto.rst: Fix wrong function name
Date: Mon, 30 Dec 2019 08:25:57 -0600 [thread overview]
Message-ID: <20191230142557.GA188380@google.com> (raw)
In-Reply-To: <20191230131428.1200-1-yuzenghui@huawei.com>
On Mon, Dec 30, 2019 at 09:14:28PM +0800, Zenghui Yu wrote:
> pci_irq_alloc_vectors() -> pci_alloc_irq_vectors().
>
> Reviewed-by: Andrew Murray <andrew.murray@arm.com>
> Signed-off-by: Zenghui Yu <yuzenghui@huawei.com>
Applied to pci/misc for v5.6, thanks!
> ---
>
> v1 -> v2:
> Add Andrew's R-b tag.
>
> 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 994cbb660ade..aa2046af69f7 100644
> --- a/Documentation/PCI/msi-howto.rst
> +++ b/Documentation/PCI/msi-howto.rst
> @@ -283,5 +283,5 @@ or disabled (0). If 0 is found in any of the msi_bus files belonging
> to bridges between the PCI root and the device, MSIs are disabled.
>
> It is also worth checking the device driver to see whether it supports MSIs.
> -For example, it may contain calls to pci_irq_alloc_vectors() with the
> +For example, it may contain calls to pci_alloc_irq_vectors() with the
> PCI_IRQ_MSI or PCI_IRQ_MSIX flags.
> --
> 2.19.1
>
>
prev parent reply other threads:[~2019-12-30 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 13:14 [PATCH v2] Documentation: PCI: msi-howto.rst: Fix wrong function name Zenghui Yu
2019-12-30 14:25 ` 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=20191230142557.GA188380@google.com \
--to=helgaas@kernel.org \
--cc=andrew.murray@arm.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.or \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=wanghaibin.wang@huawei.com \
--cc=yuzenghui@huawei.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).