From: Joe Perches <joe@perches.com>
To: Liam Breck <liam@networkimprov.net>
Cc: "Julia Lawall" <julia.lawall@lip6.fr>,
"Masahiro Yamada" <yamada.masahiro@socionext.com>,
"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,
"Gilles Muller" <Gilles.Muller@lip6.fr>,
"Nicolas Palix" <nicolas.palix@imag.fr>,
cocci@systeme.lip6.fr,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"kbuild test robot" <fengguang.wu@intel.com>
Subject: Re: [PATCH] coccinelle: api: detect duplicate chip data arrays
Date: Thu, 05 Oct 2017 12:54:25 -0700 [thread overview]
Message-ID: <1507233265.4434.45.camel@perches.com> (raw)
In-Reply-To: <CAKvHMgSniUfBjLXdBA8n_konTZm8D5kJf7M+DAZUXmEQzD0iUA@mail.gmail.com>
On Thu, 2017-10-05 at 12:46 -0700, Liam Breck wrote:
> Hi Joe,
>
> On Thu, Oct 5, 2017 at 12:30 PM, Joe Perches <joe@perches.com> wrote:
> > On Thu, 2017-10-05 at 21:19 +0200, Julia Lawall wrote:
> > > On Thu, 5 Oct 2017, Joe Perches wrote:
> > > > On Thu, 2017-10-05 at 21:13 +0200, Julia Lawall wrote:
> > > > > On Fri, 6 Oct 2017, Masahiro Yamada wrote:
> > > > > > 2017-10-01 21:42 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.
> > > > > > > Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
> > > > > >
> > > > > > Applied to linux-kbuild/misc.
> > > > >
> > > > > Thanks for picking it up.
> > > >
> > > > If it is specific to one file, why not just run it
> > > > and post the resultant patch? Why have it in tree?
> > >
> > > I guess that they anticipate that the data may change in the future?
> >
> > Aren't you the script author Julia? Who is the "they"?
> >
> > I think having a script for a single file unnecessary.
>
> Sebastian Reichel, the power-supply maintainer, requested this script.
> I previously implemented this as a run-time check within ifdef DEBUG,
> but that was rejected.
Hi Liam.
If you are the author of the script, you should also have
a sign-off/from here right?
This also has a copyright of Inria and Julia Lawall
which, if you are the author, doesn't seem appropriate.
cheers, Joe
next prev parent reply other threads:[~2017-10-05 19:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 12:42 [PATCH] coccinelle: api: detect duplicate chip data arrays Julia Lawall
2017-10-05 18:02 ` Masahiro Yamada
2017-10-05 19:13 ` Julia Lawall
2017-10-05 19:15 ` Joe Perches
2017-10-05 19:19 ` Julia Lawall
2017-10-05 19:30 ` Joe Perches
2017-10-05 19:40 ` Julia Lawall
2017-10-05 19:54 ` Joe Perches
2017-10-05 19:57 ` Julia Lawall
2017-10-05 19:46 ` Liam Breck
2017-10-05 19:54 ` Joe Perches [this message]
2017-10-05 19:58 ` Julia Lawall
2017-10-05 19:25 ` Liam Breck
2017-10-05 19:28 ` Julia Lawall
2017-10-05 19:20 ` Liam Breck
2017-10-05 19:25 ` Julia Lawall
2017-10-05 19:39 ` Liam Breck
2017-10-05 19:40 ` Julia Lawall
2017-10-09 2:50 ` Fengguang Wu
2017-10-09 6:39 ` Julia Lawall
2017-10-05 19:41 ` Julia Lawall
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=1507233265.4434.45.camel@perches.com \
--to=joe@perches.com \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=fengguang.wu@intel.com \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=liam@networkimprov.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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