From: Jens Axboe <axboe@kernel.dk>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: linux-kernel@vger.kernel.org, Mike Miller <mike.miller@hp.com>,
Asai Thambi S P <asamymuthupa@micron.com>,
Joshua Morris <josh.h.morris@us.ibm.com>,
Philip Kelleher <pjk1939@linux.vnet.ibm.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
iss_storagedev@hp.com, linux-pci@vger.kernel.org
Subject: Re: [PATCH 0/9] block: Use pci_enable_msix_range() instead of pci_enable_msix()
Date: Mon, 24 Feb 2014 09:16:19 -0800 [thread overview]
Message-ID: <530B7E63.2070908@kernel.dk> (raw)
In-Reply-To: <20140222093843.GB27897@dhcp-26-207.brq.redhat.com>
On 2014-02-22 01:38, Alexander Gordeev wrote:
> On Fri, Feb 21, 2014 at 03:46:13PM -0800, Jens Axboe wrote:
>> On Wed, Feb 19 2014, Alexander Gordeev wrote:
>>> As result of deprecation of MSI-X/MSI enablement functions
>>> pci_enable_msix() and pci_enable_msi_block() all drivers
>>> using these two interfaces need to be updated to use the
>>> new pci_enable_msi_range() and pci_enable_msix_range()
>>> interfaces.
>>
>> Thanks. Applied 3-4, and 6-9 (didn't get the others).
>
> Oh, I just realized I posted outdated series, sorry for that :(
> Out of applied patch 4 is not needed and patch 9 needs a rework.
>
> Should I repost the whole series?
Send a revised series against the previous, since they are already
committed.
--
Jens Axboe
next prev parent reply other threads:[~2014-02-24 17:16 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 [this message]
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
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=530B7E63.2070908@kernel.dk \
--to=axboe@kernel.dk \
--cc=agordeev@redhat.com \
--cc=asamymuthupa@micron.com \
--cc=iss_storagedev@hp.com \
--cc=josh.h.morris@us.ibm.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mike.miller@hp.com \
--cc=pjk1939@linux.vnet.ibm.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).