From: Johannes Berg <johannes@sipsolutions.net>
To: Chi-Hsien Lin <Chi-Hsien.Lin@cypress.com>,
"backports@vger.kernel.org" <backports@vger.kernel.org>
Cc: Winnie Chang <Winnie.Chang@cypress.com>
Subject: Re: [PATCH] backports: wrap pci_alloc_irq_vectors() in PCI defines
Date: Wed, 07 Nov 2018 10:39:05 +0100 [thread overview]
Message-ID: <e47d4b4b88f3b0212e525ff26fcc93b7400072a7.camel@sipsolutions.net> (raw)
In-Reply-To: <1541583418-196225-1-git-send-email-chi-hsien.lin@cypress.com> (sfid-20181107_103746_394708_739E53DB)
On Wed, 2018-11-07 at 09:37 +0000, Chi-Hsien Lin wrote:
> From: Winnie Chang <Winnie.Chang@cypress.com>
>
> pci_alloc_irq_vectors() needs to be wrapped in CONFIG_PCI and
> CONFIG_PCI_MSI definition to avoid a function redefinition compiler
> error.
Applied, thanks!
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
prev parent reply other threads:[~2018-11-07 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 9:37 [PATCH] backports: wrap pci_alloc_irq_vectors() in PCI defines Chi-Hsien Lin
2018-11-07 9:39 ` Johannes Berg [this message]
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=e47d4b4b88f3b0212e525ff26fcc93b7400072a7.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Chi-Hsien.Lin@cypress.com \
--cc=Winnie.Chang@cypress.com \
--cc=backports@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).