From: Bjorn Helgaas <bhelgaas@google.com>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI/MSI: Fix cut-and-paste errors in documentation
Date: Wed, 12 Feb 2014 12:14:25 -0700 [thread overview]
Message-ID: <20140212191425.GA5554@google.com> (raw)
In-Reply-To: <1392201325-11173-1-git-send-email-agordeev@redhat.com>
On Wed, Feb 12, 2014 at 11:35:25AM +0100, Alexander Gordeev wrote:
> Function pci_enable_msi_range() is used in examples where
> pci_enable_msix_range() should have been used instead.
>
> Reported-by: Bjorn Helgaas <bhelgaas@google.com>
> Cc: linux-pci@vger.kernel.org
> Signed-off-by: Alexander Gordeev <agordeev@redhat.com>
Applied to pci/misc for v3.15, thanks!
Bjorn
> ---
> Documentation/PCI/MSI-HOWTO.txt | 12 ++++++------
> 1 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/PCI/MSI-HOWTO.txt b/Documentation/PCI/MSI-HOWTO.txt
> index a8d0100..43c5a5f 100644
> --- a/Documentation/PCI/MSI-HOWTO.txt
> +++ b/Documentation/PCI/MSI-HOWTO.txt
> @@ -257,8 +257,8 @@ possible, likely up to the limit returned by pci_msix_vec_count() function:
>
> static int foo_driver_enable_msix(struct foo_adapter *adapter, int nvec)
> {
> - return pci_enable_msi_range(adapter->pdev, adapter->msix_entries,
> - 1, nvec);
> + return pci_enable_msix_range(adapter->pdev, adapter->msix_entries,
> + 1, nvec);
> }
>
> Note the value of 'minvec' parameter is 1. As 'minvec' is inclusive,
> @@ -269,8 +269,8 @@ In this case the function could look like this:
>
> static int foo_driver_enable_msix(struct foo_adapter *adapter, int nvec)
> {
> - return pci_enable_msi_range(adapter->pdev, adapter->msix_entries,
> - FOO_DRIVER_MINIMUM_NVEC, nvec);
> + return pci_enable_msix_range(adapter->pdev, adapter->msix_entries,
> + FOO_DRIVER_MINIMUM_NVEC, nvec);
> }
>
> 4.3.1.2 Exact number of MSI-X interrupts
> @@ -282,8 +282,8 @@ parameters:
>
> static int foo_driver_enable_msix(struct foo_adapter *adapter, int nvec)
> {
> - return pci_enable_msi_range(adapter->pdev, adapter->msix_entries,
> - nvec, nvec);
> + return pci_enable_msix_range(adapter->pdev, adapter->msix_entries,
> + nvec, nvec);
> }
>
> 4.3.1.3 Specific requirements to the number of MSI-X interrupts
> --
> 1.7.7.6
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-02-12 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 10:35 [PATCH] PCI/MSI: Fix cut-and-paste errors in documentation Alexander Gordeev
2014-02-12 19:14 ` 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=20140212191425.GA5554@google.com \
--to=bhelgaas@google.com \
--cc=agordeev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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).