linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	linux-pci@vger.kernel.org,
	Asai Thambi S P <asamymuthupa@micron.com>
Subject: Re: [PATCH 10/9] skd: Use pci_enable_msix_exact() instead of pci_enable_msix_range()
Date: Tue, 25 Feb 2014 14:19:22 -0800	[thread overview]
Message-ID: <20140225221922.GA10563@kernel.dk> (raw)
In-Reply-To: <20140225213317.GB20652@dhcp-26-207.brq.redhat.com> <20140225213109.GA20652@dhcp-26-207.brq.redhat.com>

On Tue, Feb 25 2014, Alexander Gordeev wrote:
> Function pci_enable_msix_exact() is a variation of
> pci_enable_msix_range() that allows a device driver
> to request a particular number of MSI-X interrupts,
> rather than any number within a specified range.

Applied 10-11, thanks.

-- 
Jens Axboe


  reply	other threads:[~2014-02-25 22:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19  8:58 [PATCH 0/9] block: Use pci_enable_msix_range() instead of pci_enable_msix() Alexander Gordeev
2014-02-19  8:58 ` [PATCH 1/9] cciss: Fallback to MSI rather than to INTx if MSI-X failed Alexander Gordeev
2014-02-19  8:58 ` [PATCH 2/9] cciss: Use pci_enable_msix_range() instead of pci_enable_msix() Alexander Gordeev
2014-02-19  8:58 ` [PATCH 3/9] mtip32xx: Remove superfluous call to pci_disable_msi() Alexander Gordeev
2014-02-19  8:58 ` [PATCH 4/9] mtip32xx: Use pci_enable_msix_range() instead of pci_enable_msix() Alexander Gordeev
2014-02-19  8:58 ` [PATCH 5/9] rsxx: " Alexander Gordeev
2014-02-19  8:58 ` [PATCH 6/9] skd: Fix out of array boundary access Alexander Gordeev
2014-02-19  8:58 ` [PATCH 7/9] skd: Fix incomplete cleanup of MSI-X interrupt Alexander Gordeev
2014-02-19  8:58 ` [PATCH 8/9] skd: Use unified access to skdev->msix_entries throughout the code Alexander Gordeev
2014-02-19  8:58 ` [PATCH 9/9] skd: Use pci_enable_msix_range() instead of pci_enable_msix() Alexander Gordeev
2014-02-21 23:46 ` [PATCH 0/9] block: " Jens Axboe
2014-02-22  9:38   ` Alexander Gordeev
2014-02-24 17:16     ` Jens Axboe
2014-02-25 21:31 ` [PATCH 10/9] skd: Use pci_enable_msix_exact() instead of pci_enable_msix_range() Alexander Gordeev
2014-02-25 22:19   ` Jens Axboe [this message]
2014-02-25 21:33 ` [PATCH 11/9] mtip32xx: Use pci_enable_msi() instead of pci_enable_msi_range() Alexander Gordeev

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=20140225221922.GA10563@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=agordeev@redhat.com \
    --cc=asamymuthupa@micron.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=kyungmin.park@samsung.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).