Re: [PATCH RFC v2 10/29] PCI/MSI: Get rid of pci_enable_msi_block_auto() interface

2013-11-20 Thread Tejun Heo
On Fri, Oct 18, 2013 at 07:12:10PM +0200, Alexander Gordeev wrote: > As result of introduction of pci_get_msi_cap() interface > pci_enable_msi_block_auto() function became superflous. > > To enable maximum possible number of MSIs drivers will > first obtain that number from pci_get_msi_cap()

Re: [PATCH RFC v2 10/29] PCI/MSI: Get rid of pci_enable_msi_block_auto() interface

2013-11-20 Thread Tejun Heo
On Fri, Oct 18, 2013 at 07:12:10PM +0200, Alexander Gordeev wrote: As result of introduction of pci_get_msi_cap() interface pci_enable_msi_block_auto() function became superflous. To enable maximum possible number of MSIs drivers will first obtain that number from pci_get_msi_cap() function

[PATCH RFC v2 10/29] PCI/MSI: Get rid of pci_enable_msi_block_auto() interface

2013-10-19 Thread Alexander Gordeev
As result of introduction of pci_get_msi_cap() interface pci_enable_msi_block_auto() function became superflous. To enable maximum possible number of MSIs drivers will first obtain that number from pci_get_msi_cap() function and then call pci_enable_msi_block() interface. Signed-off-by:

[PATCH RFC v2 10/29] PCI/MSI: Get rid of pci_enable_msi_block_auto() interface

2013-10-19 Thread Alexander Gordeev
As result of introduction of pci_get_msi_cap() interface pci_enable_msi_block_auto() function became superflous. To enable maximum possible number of MSIs drivers will first obtain that number from pci_get_msi_cap() function and then call pci_enable_msi_block() interface. Signed-off-by: