From: Bin Gao <bin.gao@linux.intel.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Zhang Rui <rui.zhang@intel.com>,
Eduardo Valentin <edubezval@gmail.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
ysiyer <yegnesh.s.iyer@intel.com>, Bin Gao <bin.gao@intel.com>
Subject: Re: [PATCH] thermal: fix of_table.cocci warnings
Date: Mon, 29 Aug 2016 10:00:00 -0700 [thread overview]
Message-ID: <20160829170000.GA60737@worksta> (raw)
In-Reply-To: <alpine.DEB.2.10.1608272058090.3363@hadrien>
On Sat, Aug 27, 2016 at 08:59:12PM +0200, Julia Lawall wrote:
> Make sure (of/i2c/platform)_device_id tables are NULL terminated
> Generated by: scripts/coccinelle/misc/of_table.cocci
>
> CC: Yegnesh S Iyer <yegnesh.s.iyer@intel.com>
> Signed-off-by: Julia Lawall <julia.lawall@lip6.fr>
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> ---
>
> Please take the patch only if it's a positive warning. Thanks!
>
> intel_bxt_pmic_thermal.c | 1 +
> 1 file changed, 1 insertion(+)
>
> --- a/drivers/thermal/intel_bxt_pmic_thermal.c
> +++ b/drivers/thermal/intel_bxt_pmic_thermal.c
> @@ -281,6 +281,7 @@ static struct platform_device_id pmic_th
> .name = "bxt_wcove_thermal",
> .driver_data = (kernel_ulong_t)&bxtwc_thermal_data,
> },
> + {},
> };
>
> static struct platform_driver pmic_thermal_driver = {
Included in v5. Thanks.
-Bin
prev parent reply other threads:[~2016-08-29 16:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 18:59 [PATCH] thermal: fix of_table.cocci warnings Julia Lawall
2016-08-27 19:11 ` constification and cocci / kernel build test robot ? Joe Perches
2016-08-28 9:40 ` Julia Lawall
2016-08-28 13:13 ` Julia Lawall
2016-08-28 17:39 ` Joe Perches
2016-08-28 17:43 ` Julia Lawall
2016-08-30 18:50 ` Kees Cook
2016-08-30 19:23 ` Julia Lawall
2016-08-30 22:15 ` Kees Cook
2016-08-31 5:22 ` Julia Lawall
2016-08-31 10:08 ` Mark Rutland
2016-08-31 14:44 ` Kees Cook
2016-08-31 16:41 ` Mark Rutland
2016-09-01 14:10 ` PaX Team
2016-08-29 17:00 ` Bin Gao [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=20160829170000.GA60737@worksta \
--to=bin.gao@linux.intel.com \
--cc=bin.gao@intel.com \
--cc=edubezval@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=yegnesh.s.iyer@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).