From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Omer Efrat <omer.efrat@tandemg.com>,
"backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: PCI MSI API support in backports
Date: Wed, 23 May 2018 14:21:59 +0200 [thread overview]
Message-ID: <5B055CE7.4000000@broadcom.com> (raw)
In-Reply-To: <HE1PR0202MB2954B6138062CFAF4D2D2BA59A6B0@HE1PR0202MB2954.eurprd02.prod.outlook.com>
On 5/23/2018 1:39 PM, Omer Efrat wrote:
> Our wireless driver uses pci_alloc_irq_vectors function in order to allocate the pci irq vectors.
> (hardware supports MSI, with no MSIx support)
>
> When trying to backport from linux-stable v4.16 to v3.10.104, compilation fails.
> It seems that backports didn't backported pci_alloc_irq_vectors function (introduced at aff171641d181ea573380efc3f559c9de4741fc5 PCI: Provide sensible IRQ vector alloc/free routines), although MSIx APIs are supported in backports.
>
> Is that makes sense?
> Are changes to PCI driver being included in backports by their owners as a workflow?
> Is pci_alloc_irq_vectors function planned to be included in backports?
> Are we missing something?
Well. I think what you are missing is a wireless driver in linux
upstream. We backport on a as-needed basis so the reason is probably
that none of the upstream drivers require the pci_alloc_irq_vectors()
function. So what wireless driver are we talking about here. Is it a
proprietary driver?
Regards,
Arend
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2018-05-23 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 11:39 PCI MSI API support in backports Omer Efrat
2018-05-23 12:21 ` Arend van Spriel [this message]
2018-05-24 13:40 ` Omer Efrat
2018-05-24 19:31 ` Arend van Spriel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5B055CE7.4000000@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=omer.efrat@tandemg.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.