From: Julia Lawall <julia.lawall@lip6.fr>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: "Julia Lawall" <Julia.Lawall@lip6.fr>,
"Liam Breck" <liam@networkimprov.net>,
"Sebastian Reichel" <sebastian.reichel@collabora.co.uk>,
"Pali Rohár" <pali.rohar@gmail.com>,
"Linux PM mailing list" <linux-pm@vger.kernel.org>,
kernel-janitors@vger.kernel.org, "Joe Perches" <joe@perches.com>,
"Gilles Muller" <Gilles.Muller@lip6.fr>,
"Nicolas Palix" <nicolas.palix@imag.fr>,
"Michal Marek" <mmarek@suse.com>,
cocci@systeme.lip6.fr,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"kbuild test robot" <fengguang.wu@intel.com>
Subject: Re: [PATCH 2/2] scripts: coccinelle: api: detect identical chip data arrays
Date: Wed, 8 Nov 2017 21:04:17 +0800 (CST) [thread overview]
Message-ID: <alpine.DEB.2.20.1711082104070.2708@hadrien> (raw)
In-Reply-To: <CAK7LNAQKOK5fbkq9AcSzmHc+qJLxAwB0Hy5eYy389uMnvah7uA@mail.gmail.com>
On Tue, 7 Nov 2017, Masahiro Yamada wrote:
> 2017-10-09 4:18 GMT+09:00 Julia Lawall <Julia.Lawall@lip6.fr>:
> > This semantic patch detects duplicate arrays declared using BQ27XXX_DATA
> > within a single structure. It is currently specific to the file
> > drivers/power/supply/bq27xxx_battery.c. Nevertheless, having the script in
> > the kernel will allow others to check their code if the data structures
> > change in the future.
> >
> > Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
> >
>
> Applied to linux-kbuild/misc.
Thanks!
julia
next prev parent reply other threads:[~2017-11-08 13:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-08 19:18 [PATCH 0/2] detect identical chip data arrays Julia Lawall
2017-10-08 19:18 ` [PATCH 1/2] scripts: coccinelle: api: drop battery.cocci Julia Lawall
2017-10-08 19:18 ` [PATCH 2/2] scripts: coccinelle: api: detect identical chip data arrays Julia Lawall
2017-11-07 0:21 ` Masahiro Yamada
2017-11-08 13:04 ` Julia Lawall [this message]
2017-10-08 20:32 ` [PATCH 0/2] " Sebastian Reichel
2017-10-08 20:44 ` Julia Lawall
2017-10-08 21:26 ` Sebastian Reichel
2017-10-09 8:31 ` Masahiro Yamada
2017-10-09 8:40 ` Julia Lawall
2017-10-09 9:11 ` Masahiro Yamada
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.20.1711082104070.2708@hadrien \
--to=julia.lawall@lip6.fr \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=fengguang.wu@intel.com \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=liam@networkimprov.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=nicolas.palix@imag.fr \
--cc=pali.rohar@gmail.com \
--cc=sebastian.reichel@collabora.co.uk \
--cc=yamada.masahiro@socionext.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