From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: YueHaibing <yuehaibing@huawei.com>
Cc: Antoine Tenart <antoine.tenart@bootlin.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Pascal Van Leeuwen <pvanleeuwen@insidesecure.com>,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] crypto: inside-secure - Fix build error without CONFIG_PCI
Date: Mon, 2 Sep 2019 18:32:45 -0700 [thread overview]
Message-ID: <CAKv+Gu-KFp13gnx=cnVRrU4_sD8qLLXFcTOK8zuc7MC+B+GmcQ@mail.gmail.com> (raw)
In-Reply-To: <20190902141910.1080-1-yuehaibing@huawei.com>
On Mon, 2 Sep 2019 at 07:19, YueHaibing <yuehaibing@huawei.com> wrote:
>
> If CONFIG_PCI is not set, building fails:
>
> rivers/crypto/inside-secure/safexcel.c: In function safexcel_request_ring_irq:
> drivers/crypto/inside-secure/safexcel.c:944:9: error: implicit declaration of function pci_irq_vector;
> did you mean rcu_irq_enter? [-Werror=implicit-function-declaration]
> irq = pci_irq_vector(pci_pdev, irqid);
> ^~~~~~~~~~~~~~
>
> Use #ifdef block to guard this.
>
> Fixes: 625f269a5a7a ("crypto: inside-secure - add support for PCI based FPGA development board")
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
> drivers/crypto/inside-secure/safexcel.c | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/crypto/inside-secure/safexcel.c b/drivers/crypto/inside-secure/safexcel.c
> index e12a2a3..c23fe34 100644
> --- a/drivers/crypto/inside-secure/safexcel.c
> +++ b/drivers/crypto/inside-secure/safexcel.c
> @@ -937,7 +937,8 @@ static int safexcel_request_ring_irq(void *pdev, int irqid,
> int ret, irq;
> struct device *dev;
>
> - if (IS_ENABLED(CONFIG_PCI) && is_pci_dev) {
> +#if IS_ENABLED(CONFIG_PCI)
please don't use IS_ENABLED() with preprocessor conditionals - just
use #ifdef CONFIG_PCI instead
> + if (is_pci_dev) {
> struct pci_dev *pci_pdev = pdev;
>
> dev = &pci_pdev->dev;
> @@ -947,7 +948,10 @@ static int safexcel_request_ring_irq(void *pdev, int irqid,
> irqid, irq);
> return irq;
> }
> - } else if (IS_ENABLED(CONFIG_OF)) {
> + } else
> +#endif
> + {
> +#if IS_ENABLED(CONFIG_OF)
> struct platform_device *plf_pdev = pdev;
> char irq_name[6] = {0}; /* "ringX\0" */
>
> @@ -960,6 +964,7 @@ static int safexcel_request_ring_irq(void *pdev, int irqid,
> irq_name, irq);
> return irq;
> }
> +#endif
> }
>
> ret = devm_request_threaded_irq(dev, irq, handler,
> @@ -1137,7 +1142,8 @@ static int safexcel_probe_generic(void *pdev,
>
> safexcel_configure(priv);
>
> - if (IS_ENABLED(CONFIG_PCI) && priv->version == EIP197_DEVBRD) {
> +#if IS_ENABLED(CONFIG_PCI)
> + if (priv->version == EIP197_DEVBRD) {
> /*
> * Request MSI vectors for global + 1 per ring -
> * or just 1 for older dev images
> @@ -1153,6 +1159,7 @@ static int safexcel_probe_generic(void *pdev,
> return ret;
> }
> }
> +#endif
>
> /* Register the ring IRQ handlers and configure the rings */
> priv->ring = devm_kcalloc(dev, priv->config.rings,
> --
> 2.7.4
>
>
next prev parent reply other threads:[~2019-09-03 1:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 14:19 [PATCH -next] crypto: inside-secure - Fix build error without CONFIG_PCI YueHaibing
2019-09-03 1:32 ` Ard Biesheuvel [this message]
2019-09-03 1:45 ` [PATCH v2 " YueHaibing
2019-09-04 11:57 ` Pascal Van Leeuwen
2019-09-04 12:10 ` Ard Biesheuvel
2019-09-04 12:25 ` Pascal Van Leeuwen
2019-09-04 12:27 ` Ard Biesheuvel
2019-09-04 12:31 ` Herbert Xu
2019-09-04 12:45 ` Pascal Van Leeuwen
2019-09-04 13:08 ` Herbert Xu
2019-09-04 12:43 ` Pascal Van Leeuwen
2019-09-04 12:26 ` PCI: Add stub pci_irq_vector and others Herbert Xu
2019-09-04 14:33 ` Yuehaibing
2019-09-05 21:07 ` Bjorn Helgaas
2019-09-05 22:53 ` Herbert Xu
2019-09-20 19:42 ` Bjorn Helgaas
2019-09-20 23:16 ` Herbert Xu
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='CAKv+Gu-KFp13gnx=cnVRrU4_sD8qLLXFcTOK8zuc7MC+B+GmcQ@mail.gmail.com' \
--to=ard.biesheuvel@linaro.org \
--cc=antoine.tenart@bootlin.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pvanleeuwen@insidesecure.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;
as well as URLs for NNTP newsgroup(s).