From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@lists.codethink.co.uk,
Kevin Hilman <khilman@baylibre.com>,
Ben Dooks <ben.dooks@codethink.co.uk>,
linux-amlogic@lists.infradead.org
Subject: [PATCH 04/11] ARM: meson: use NULL instead of 0 for pointer
Date: Tue, 8 Oct 2019 13:34:46 +0100 [thread overview]
Message-ID: <20191008123453.1651-4-ben.dooks@codethink.co.uk> (raw)
In-Reply-To: <20191008123453.1651-1-ben.dooks@codethink.co.uk>
Fix the second argument of of_get_cpu_node which is a pointer
being passed a plain 0 by using NULL instead. Fixes the following
warning:
arch/arm/mach-meson/platsmp.c:40:55: warning: Using plain integer as NULL pointer
Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
---
CC: Kevin Hilman <khilman@baylibre.com>
CC: linux-amlogic@lists.infradead.org
---
arch/arm/mach-meson/platsmp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-meson/platsmp.c b/arch/arm/mach-meson/platsmp.c
index 4b8ad728bb42..f992c436d3ed 100644
--- a/arch/arm/mach-meson/platsmp.c
+++ b/arch/arm/mach-meson/platsmp.c
@@ -37,7 +37,7 @@ static struct regmap *pmu;
static struct reset_control *meson_smp_get_core_reset(int cpu)
{
- struct device_node *np = of_get_cpu_node(cpu, 0);
+ struct device_node *np = of_get_cpu_node(cpu, NULL);
return of_reset_control_get_exclusive(np, NULL);
}
--
2.23.0
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next parent reply other threads:[~2019-10-08 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191008123453.1651-1-ben.dooks@codethink.co.uk>
2019-10-08 12:34 ` Ben Dooks [this message]
[not found] <20191008123341.1551-1-ben.dooks@codethink.co.uk>
2019-10-08 12:33 ` [PATCH 04/11] ARM: meson: use NULL instead of 0 for pointer Ben Dooks
2019-10-08 17:26 ` Martin Blumenstingl
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=20191008123453.1651-4-ben.dooks@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@lists.codethink.co.uk \
/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).