From: Julia Lawall <julia.lawall@lip6.fr>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linus.walleij@linaro.org, gnurou@gmail.com, lee.jones@linaro.org,
broonie@kernel.org, a.zummo@towertech.it,
alexandre.belloni@free-electrons.com, lgirdwood@gmail.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, rtc-linux@googlegroups.com,
swarren@nvidia.com, treding@nvidia.com,
Chaitanya Bandi <bandik@nvidia.com>
Subject: [PATCH] gpio: max77620: fix of_table.cocci warnings
Date: Mon, 11 Jan 2016 11:48:34 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.10.1601111146380.2512@hadrien> (raw)
Make sure (of/i2c/platform)_device_id tables are NULL terminated
Generated by: scripts/coccinelle/misc/of_table.cocci
CC: Laxman Dewangan <ldewangan@nvidia.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
Signed-off-by: Julia Lawall <julia.lawall@lip6.fr>
---
Please take the patch only if it's a positive warning. Thanks!
gpio-max77620.c | 1 +
1 file changed, 1 insertion(+)
--- a/drivers/gpio/gpio-max77620.c
+++ b/drivers/gpio/gpio-max77620.c
@@ -301,6 +301,7 @@ static struct platform_device_id max7762
{
.name = "max20024-gpio",
},
+ {},
};
static struct platform_driver max77620_gpio_driver = {
next reply other threads:[~2016-01-11 10:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 10:48 Julia Lawall [this message]
2016-01-14 9:00 ` [PATCH] gpio: max77620: fix of_table.cocci warnings Linus Walleij
2016-01-14 9:47 ` Lee Jones
2016-01-14 9:39 ` Laxman Dewangan
2016-01-15 13:15 ` Linus Walleij
[not found] ` <CACRpkdaV6e2SeAGE5C6_W6_0qbwMG6RaL+b+8o+JoyuJR-Y=Hg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-15 13:44 ` Julia Lawall
2016-01-18 12:08 ` Laxman Dewangan
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=alpine.DEB.2.10.1601111146380.2512@hadrien \
--to=julia.lawall@lip6.fr \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=bandik@nvidia.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ldewangan@nvidia.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=swarren@nvidia.com \
--cc=treding@nvidia.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