linux-kernel - Re: [PATCH 1/2] GenWQE: Use pci_enable_msi_exact() instead of pci_enable_msi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140425182741.GB6473@kroah.com>
Date:	Fri, 25 Apr 2014 11:27:41 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	Alexander Gordeev <agordeev@...hat.com>,
	linux-kernel@...r.kernel.org,
	Frank Haverkamp <haver@...ux.vnet.ibm.com>,
	linux-pci@...r.kernel.org
Subject: Re: [PATCH 1/2] GenWQE: Use pci_enable_msi_exact() instead of
 pci_enable_msi_block()

On Fri, Apr 25, 2014 at 12:19:11PM -0600, Bjorn Helgaas wrote:
> On Mon, Apr 14, 2014 at 09:14:06AM +0200, 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()  or pci_enable_msi_exact()
> > and pci_enable_msix_range() or pci_enable_msix_exact()
> > interfaces.
> > 
> > Signed-off-by: Alexander Gordeev <agordeev@...hat.com>
> > Cc: Frank Haverkamp <haver@...ux.vnet.ibm.com>
> > Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> > Cc: linux-pci@...r.kernel.org
> > Acked-by: Frank Haverkamp <haver@...ux.vnet.ibm.com>
> 
> Greg, since you acked this rather than saying you applied it, I applied
> this to my pci/msi branch.  If you'd rather take it yourself, just let me
> know.

Nope, through your tree is fine, I have enough other patches in my trees :)

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/