From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f45.google.com ([209.85.220.45]:56533 "EHLO mail-pa0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754236AbaCMP2X (ORCPT ); Thu, 13 Mar 2014 11:28:23 -0400 Received: by mail-pa0-f45.google.com with SMTP id kl14so1270759pab.4 for ; Thu, 13 Mar 2014 08:28:22 -0700 (PDT) Message-ID: <5321CE94.5070506@kernel.dk> Date: Thu, 13 Mar 2014 09:28:20 -0600 From: Jens Axboe MIME-Version: 1.0 To: Bjorn Helgaas , Alexander Gordeev CC: linux-kernel@vger.kernel.org, Mike Miller , iss_storagedev@hp.com, linux-pci@vger.kernel.org, Keith Busch , Matthew Wilcox Subject: Re: [PATCH v2 0/2] block: Use pci_enable_msix_exact() instead of pci_enable_msix() References: <20140313041231.GC26657@google.com> In-Reply-To: <20140313041231.GC26657@google.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: linux-pci-owner@vger.kernel.org List-ID: On 03/12/2014 10:12 PM, Bjorn Helgaas wrote: > On Wed, Feb 26, 2014 at 10:02:40AM +0100, Alexander Gordeev wrote: >> Changes since v1: >> - cciss: patch #1: a weird 'goto' removed; >> - cciss: patch #2: pci_enable_msix_exact() used, not pci_enable_msix_range(); >> - rsxx: patch dropped - no need to change anything; >> >> 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() or pci_enable_msi_exact() >> and pci_enable_msix_range() or pci_enable_msix_exact() >> interfaces. >> >> This change updates 'cciss' only, but there is also 'nvme' update >> pending - I am waiting for Intel guys to clarify if they want to >> route it thru their tree. If not, I will post the 'nvme' patch as >> a follow-up to this series. > > Hi Jens, > > I'd like to get these merged during the v3.15 merge window. I'd be glad to > review and apply them through my tree, unless you want to do it. They do > depend on f7fc32c, which went in after the v3.14 merge window, which makes > it a bit of a hassle. My 3.15/drivers (and core) branch are based off 3.14-rc3, so it should be OK. I've queued them up, as it's mostly a followup to the previous ones from Alexander. -- Jens Axboe