On Tue, Mar 25, 2014 at 03:27:30PM +0100, Alexander Gordeev wrote:
On Thu, Mar 06, 2014 at 01:56:46PM -0800, Sarah Sharp wrote:
What do you mean by this sentence? Are you fixing some bug in those two
functions, or just cleaning up how they look? Either way, this should
really be two
On 04/02/2014 02:41 PM, Alexander Gordeev wrote:
On Tue, Mar 25, 2014 at 03:27:30PM +0100, Alexander Gordeev wrote:
On Thu, Mar 06, 2014 at 01:56:46PM -0800, Sarah Sharp wrote:
What do you mean by this sentence? Are you fixing some bug in those two
functions, or just cleaning up how they
On Thu, Mar 06, 2014 at 01:56:46PM -0800, Sarah Sharp wrote:
What do you mean by this sentence? Are you fixing some bug in those two
functions, or just cleaning up how they look? Either way, this should
really be two patches.
Hi Sarah,
Any feedback on v2?
Thanks!
Sarah Sharp
--
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.
On Thu, Mar 06, 2014 at 09:11:24PM +0100, 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()
