linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: kernel test robot <lkp@intel.com>,
	kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH] crypto: qcom-rng - Fix qcom_rng_of_match unused warning
Date: Wed, 3 Aug 2022 17:55:24 +0530	[thread overview]
Message-ID: <YuppNF2+MYs9V84j@matsya> (raw)
In-Reply-To: <YuOp49dCARTVQ+c+@gondor.apana.org.au>

On 29-07-22, 17:35, Herbert Xu wrote:
> On Sun, Jul 24, 2022 at 08:12:39AM +0800, kernel test robot wrote:
> >
> > >> drivers/crypto/qcom-rng.c:190:34: warning: 'qcom_rng_of_match' defined but not used [-Wunused-const-variable=]
> >      190 | static const struct of_device_id qcom_rng_of_match[] = {
> >          |                                  ^~~~~~~~~~~~~~~~~
> 
> ---8<---
> Module device tables need to be declared as maybe_unused because
> they will be unused when built-in and the corresponding option is
> also disabled.
> 
> This patch adds the maybe_unused attributes to OF and ACPI.  This
> also allows us to remove the ifdef around the ACPI data structure.

Reviewed-by: Vinod Koul <vkoul@kernel.org>

> 
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
> 
> diff --git a/drivers/crypto/qcom-rng.c b/drivers/crypto/qcom-rng.c
> index 031b5f701a0a..72dd1a4ebac4 100644
> --- a/drivers/crypto/qcom-rng.c
> +++ b/drivers/crypto/qcom-rng.c
> @@ -9,6 +9,7 @@
>  #include <linux/crypto.h>
>  #include <linux/io.h>
>  #include <linux/iopoll.h>
> +#include <linux/kernel.h>
>  #include <linux/module.h>
>  #include <linux/of.h>
>  #include <linux/platform_device.h>
> @@ -201,15 +202,13 @@ static int qcom_rng_remove(struct platform_device *pdev)
>  	return 0;
>  }
>  
> -#if IS_ENABLED(CONFIG_ACPI)
> -static const struct acpi_device_id qcom_rng_acpi_match[] = {
> +static const struct acpi_device_id __maybe_unused qcom_rng_acpi_match[] = {
>  	{ .id = "QCOM8160", .driver_data = 1 },
>  	{}
>  };
>  MODULE_DEVICE_TABLE(acpi, qcom_rng_acpi_match);
> -#endif
>  
> -static const struct of_device_id qcom_rng_of_match[] = {
> +static const struct of_device_id __maybe_unused qcom_rng_of_match[] = {
>  	{ .compatible = "qcom,prng", .data = (void *)0},
>  	{ .compatible = "qcom,prng-ee", .data = (void *)1},
>  	{}
> -- 
> Email: Herbert Xu <herbert@gondor.apana.org.au>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

-- 
~Vinod

      reply	other threads:[~2022-08-03 12:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <202207240830.NxaVYPVM-lkp@intel.com>
2022-07-29  9:35 ` [PATCH] crypto: qcom-rng - Fix qcom_rng_of_match unused warning Herbert Xu
2022-08-03 12:25   ` 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=YuppNF2+MYs9V84j@matsya \
    --to=vkoul@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=kbuild-all@lists.01.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.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).