Re: [PATCH v2 0/9] Phase out pci_enable_msi_block()
On Fri, Jan 17, 2014 at 02:00:32PM -0700, Bjorn Helgaas wrote: Bjorn, As the release is supposedly this weekend, do you prefer the patches to go to your tree or to individual trees after the release? I'd be happy to merge them, except for the fact that they probably wouldn't have any time in -next before I ask Linus to pull them. So how about if we wait until after the release, ask the area maintainers to take them, and if they don't take them, I'll put them in my tree for v3.15? Hi Gentleman, As the prerequisite commit 302a252 (PCI/MSI: Add pci_enable_msi_range() and pci_enable_msix_range()) is in mainline now, could you please take the ACKed patches to your trees? Thanks! Bjorn -- Regards, Alexander Gordeev agord...@redhat.com -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 0/9] Phase out pci_enable_msi_block()
On Sat, Jan 18, 2014 at 09:59:40AM -0500, Tejun Heo wrote: On Sat, Jan 18, 2014 at 07:38:55AM -0700, Bjorn Helgaas wrote: On Sat, Jan 18, 2014 at 12:15 AM, Alexander Gordeev agord...@redhat.com wrote: On Fri, Jan 17, 2014 at 02:00:32PM -0700, Bjorn Helgaas wrote: As the release is supposedly this weekend, do you prefer the patches to go to your tree or to individual trees after the release? I'd be happy to merge them, except for the fact that they probably wouldn't have any time in -next before I ask Linus to pull them. So how about if we wait until after the release, ask the area maintainers to take them, and if they don't take them, I'll put them in my tree for v3.15? Patch 11 depends on patches 1-10, so I am not sure how to better handle it. Whatever works for you ;) I am only concerned with a regression fix ahci: Fix broken fallback to single MSI mode which would be nice to have in 3.14. But it seems pretty much too late. Tejun, if you want to ack that one, I can put it in either the first 3.14 pull request or a subsequent one. Either way, since it's a regression fix, we should be able to get it in 3.14. Acked-by: Tejun Heo t...@kernel.org Please feel free to route it any way you see fit. I applied the following to my pci/msi branch, since they had acks from maintainers (Tejun, I assumed your ack applies to both ahci patches): ahci: Fix broken fallback to single MSI mode ahci: Use pci_enable_msi_range() vfio: Use pci_enable_msi_range() and pci_enable_msix_range() wil6210: Use pci_enable_msi_range() I didn't do anything with these: ipr: Get rid of superfluous call to pci_disable_msi/msix() ipr: Use pci_enable_msi_range() and pci_enable_msix_range() The conflict with ipr: Handle early EEH needs to get resolved first. Either Alexander's patches need to go via the same tree as the EEH change, or the EEH change needs to be in some published tree so I can cherry-pick it. nvme: Fix invalid call to irq_set_affinity_hint() nvme: Use pci_enable_msi_range() and pci_enable_msix_range() These don't seem fully baked yet. If/when Keith acks them, I (or he) can merge them. ath10k: Use pci_enable_msi_range() This has been acked, but no longer applies to mainline (I'm currently at 0e47c969c65e). Bjorn -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 0/9] Phase out pci_enable_msi_block()
On Sat, Jan 18, 2014 at 12:15 AM, Alexander Gordeev agord...@redhat.com wrote: On Fri, Jan 17, 2014 at 02:00:32PM -0700, Bjorn Helgaas wrote: As the release is supposedly this weekend, do you prefer the patches to go to your tree or to individual trees after the release? I'd be happy to merge them, except for the fact that they probably wouldn't have any time in -next before I ask Linus to pull them. So how about if we wait until after the release, ask the area maintainers to take them, and if they don't take them, I'll put them in my tree for v3.15? Patch 11 depends on patches 1-10, so I am not sure how to better handle it. Whatever works for you ;) I am only concerned with a regression fix ahci: Fix broken fallback to single MSI mode which would be nice to have in 3.14. But it seems pretty much too late. Tejun, if you want to ack that one, I can put it in either the first 3.14 pull request or a subsequent one. Either way, since it's a regression fix, we should be able to get it in 3.14. Bjorn -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 0/9] Phase out pci_enable_msi_block()
On Sat, Jan 18, 2014 at 07:38:55AM -0700, Bjorn Helgaas wrote: On Sat, Jan 18, 2014 at 12:15 AM, Alexander Gordeev agord...@redhat.com wrote: On Fri, Jan 17, 2014 at 02:00:32PM -0700, Bjorn Helgaas wrote: As the release is supposedly this weekend, do you prefer the patches to go to your tree or to individual trees after the release? I'd be happy to merge them, except for the fact that they probably wouldn't have any time in -next before I ask Linus to pull them. So how about if we wait until after the release, ask the area maintainers to take them, and if they don't take them, I'll put them in my tree for v3.15? Patch 11 depends on patches 1-10, so I am not sure how to better handle it. Whatever works for you ;) I am only concerned with a regression fix ahci: Fix broken fallback to single MSI mode which would be nice to have in 3.14. But it seems pretty much too late. Tejun, if you want to ack that one, I can put it in either the first 3.14 pull request or a subsequent one. Either way, since it's a regression fix, we should be able to get it in 3.14. Acked-by: Tejun Heo t...@kernel.org Please feel free to route it any way you see fit. Thanks! -- tejun -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH v2 0/9] Phase out pci_enable_msi_block()
This series is against next branch in Bjorn's repo: git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git Changes from v1 to v2: - added a regression fix ahci: Fix broken fallback to single MSI mode as patch 1/9; - the series is reordered to move the regression fix in front; - at Bjorn's request pci_enable_msi() is un-deprecated; - as result, pci_enable_msi_range(pdev, 1, 1) styled calls rolled back to pci_enable_msi(pdev); - nvme bug fix moved out as a separate patch 5/9 nvme: Fix invalid call to irq_set_affinity_hint() - patches changelog elaborated a bit; Bjorn, As the release is supposedly this weekend, do you prefer the patches to go to your tree or to individual trees after the release? Thanks! Alexander Gordeev (9): ahci: Fix broken fallback to single MSI mode ahci: Use pci_enable_msi_range() ipr: Get rid of superfluous call to pci_disable_msi/msix() ipr: Use pci_enable_msi_range() and pci_enable_msix_range() nvme: Fix invalid call to irq_set_affinity_hint() nvme: Use pci_enable_msi_range() and pci_enable_msix_range() vfio: Use pci_enable_msi_range() and pci_enable_msix_range() ath10k: Use pci_enable_msi_range() wil6210: Use pci_enable_msi_range() drivers/ata/ahci.c | 18 +- drivers/block/nvme-core.c | 33 - drivers/net/wireless/ath/ath10k/pci.c | 20 +- drivers/net/wireless/ath/wil6210/pcie_bus.c | 36 ++- drivers/scsi/ipr.c | 51 +- drivers/vfio/pci/vfio_pci_intrs.c | 12 -- 6 files changed, 72 insertions(+), 98 deletions(-) -- 1.7.7.6 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 0/9] Phase out pci_enable_msi_block()
On Fri, Jan 17, 2014 at 9:02 AM, Alexander Gordeev agord...@redhat.com wrote: This series is against next branch in Bjorn's repo: git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git Changes from v1 to v2: - added a regression fix ahci: Fix broken fallback to single MSI mode as patch 1/9; - the series is reordered to move the regression fix in front; - at Bjorn's request pci_enable_msi() is un-deprecated; - as result, pci_enable_msi_range(pdev, 1, 1) styled calls rolled back to pci_enable_msi(pdev); - nvme bug fix moved out as a separate patch 5/9 nvme: Fix invalid call to irq_set_affinity_hint() - patches changelog elaborated a bit; Bjorn, As the release is supposedly this weekend, do you prefer the patches to go to your tree or to individual trees after the release? I'd be happy to merge them, except for the fact that they probably wouldn't have any time in -next before I ask Linus to pull them. So how about if we wait until after the release, ask the area maintainers to take them, and if they don't take them, I'll put them in my tree for v3.15? Bjorn -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 0/9] Phase out pci_enable_msi_block()
On Fri, Jan 17, 2014 at 02:00:32PM -0700, Bjorn Helgaas wrote: As the release is supposedly this weekend, do you prefer the patches to go to your tree or to individual trees after the release? I'd be happy to merge them, except for the fact that they probably wouldn't have any time in -next before I ask Linus to pull them. So how about if we wait until after the release, ask the area maintainers to take them, and if they don't take them, I'll put them in my tree for v3.15? Patch 11 depends on patches 1-10, so I am not sure how to better handle it. Whatever works for you ;) I am only concerned with a regression fix ahci: Fix broken fallback to single MSI mode which would be nice to have in 3.14. But it seems pretty much too late. Bjorn Thanks! -- Regards, Alexander Gordeev agord...@redhat.com -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
