On 14/12/16 11:47, Christoph Hellwig wrote:
On Wed, Dec 14, 2016 at 11:37:17AM +0100, Hans Verkuil wrote:
Completely forgot this. Is it OK to queue it for 4.11? Or is it blocking
other follow-up work you want to do for 4.10?
My plan was to see if Bjorn would take the patch to do the trivial re
On Wed, Dec 14, 2016 at 11:37:17AM +0100, Hans Verkuil wrote:
> Completely forgot this. Is it OK to queue it for 4.11? Or is it blocking
> other follow-up work you want to do for 4.10?
My plan was to see if Bjorn would take the patch to do the trivial removal
of pci_enable_msix_exact and pci_enabl
On 14/12/16 11:29, Christoph Hellwig wrote:
Hi Hans,
just checked the current Linux tree and cobalt still uses the old
pci_enable_msi_range call. Did you queue this patch up for 4.10?
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...
Hi Hans,
just checked the current Linux tree and cobalt still uses the old
pci_enable_msi_range call. Did you queue this patch up for 4.10?
--
To unsubscribe from this list: send the line "unsubscribe linux-block" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http:
On Fri, Sep 16, 2016 at 10:01:42AM +0200, Hans Verkuil wrote:
> PCI_IRQ_MSI is unknown, I assume that this will appear in 4.9?
The flag is in 4.8-rc.
--
To unsubscribe from this list: send the line "unsubscribe linux-block" in
the body of a message to majord...@vger.kernel.org
More majordomo info
Hi Christoph,
On 09/11/2016 03:31 PM, Christoph Hellwig wrote:
> Simply the interrupt setup by using the new PCI layer helpers.
>
> Despite using pci_enable_msi_range, this driver was only requesting a
> single MSI vector anyway.
>
> Signed-off-by: Christoph Hellwig
> ---
> drivers/media/pci/c