From: "Herbert Xu" <herbert@gondor.apana.org.au>
To: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: [PATCH 4/7] hwrng: bcm2835 - Fix W=1 unused variable warning
Date: Mon, 29 Jun 2020 18:04:00 +1000 [thread overview]
Message-ID: <E1jpolk-0003w0-60@fornost.hmeau.com> (raw)
In-Reply-To: 20200629080316.GA11246@gondor.apana.org.au
This patch fixes an unused variable warning when this driver is
built with CONFIG_OF=n.
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
---
drivers/char/hw_random/bcm2835-rng.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/char/hw_random/bcm2835-rng.c b/drivers/char/hw_random/bcm2835-rng.c
index cbf5eaea662c5..eec26329d1ea7 100644
--- a/drivers/char/hw_random/bcm2835-rng.c
+++ b/drivers/char/hw_random/bcm2835-rng.c
@@ -139,7 +139,6 @@ static int bcm2835_rng_probe(struct platform_device *pdev)
{
const struct bcm2835_rng_of_data *of_data;
struct device *dev = &pdev->dev;
- struct device_node *np = dev->of_node;
const struct of_device_id *rng_id;
struct bcm2835_rng_priv *priv;
int err;
@@ -166,7 +165,7 @@ static int bcm2835_rng_probe(struct platform_device *pdev)
priv->rng.cleanup = bcm2835_rng_cleanup;
if (dev_of_node(dev)) {
- rng_id = of_match_node(bcm2835_rng_of_match, np);
+ rng_id = of_match_node(bcm2835_rng_of_match, dev->of_node);
if (!rng_id)
return -EINVAL;
next prev parent reply other threads:[~2020-06-29 19:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 8:03 [PATCH 0/7] hwrng: Fix W=1 warnings Herbert Xu
2020-06-29 8:03 ` [PATCH 1/7] hwrng: npcm - Fix W=1 unused variable warning Herbert Xu
2020-06-29 8:03 ` [PATCH 2/7] hwrng: omap " Herbert Xu
2020-06-29 8:03 ` [PATCH 3/7] hwrng: hisi " Herbert Xu
2020-06-29 8:04 ` Herbert Xu [this message]
2020-06-29 8:04 ` [PATCH 5/7] hwrng: st " Herbert Xu
2020-06-29 8:04 ` [PATCH 6/7] hwrng: pic32 " Herbert Xu
2020-06-29 8:04 ` [PATCH 7/7] hwrng: octeon - Fix sparse warnings 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=E1jpolk-0003w0-60@fornost.hmeau.com \
--to=herbert@gondor.apana.org.au \
--cc=linux-crypto@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 NNTP newsgroup(s).