From: Vinod Koul <vkoul@kernel.org>
To: YueHaibing <yuehaibing@huawei.com>
Cc: dan.j.williams@intel.com, wangzhou1@hisilicon.com,
qiuzhenfa@hisilicon.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] dmaengine: hisilicon: Fix build error without PCI_MSI
Date: Wed, 15 Apr 2020 21:19:06 +0530 [thread overview]
Message-ID: <20200415154906.GR72691@vkoul-mobl> (raw)
In-Reply-To: <20200328114133.17560-1-yuehaibing@huawei.com>
On 28-03-20, 19:41, YueHaibing wrote:
> If PCI_MSI is not set, building fais:
>
> drivers/dma/hisi_dma.c: In function ‘hisi_dma_free_irq_vectors’:
> drivers/dma/hisi_dma.c:138:2: error: implicit declaration of function ‘pci_free_irq_vectors’;
> did you mean ‘pci_alloc_irq_vectors’? [-Werror=implicit-function-declaration]
> pci_free_irq_vectors(data);
> ^~~~~~~~~~~~~~~~~~~~
>
> Make HISI_DMA depends on PCI_MSI to fix this.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2020-04-15 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 11:41 [PATCH -next] dmaengine: hisilicon: Fix build error without PCI_MSI YueHaibing
2020-03-30 2:39 ` Zhou Wang
2020-03-30 6:59 ` Yuehaibing
2020-04-15 15:49 ` Vinod Koul [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=20200415154906.GR72691@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiuzhenfa@hisilicon.com \
--cc=wangzhou1@hisilicon.com \
--cc=yuehaibing@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox