From: Julia Lawall <julia.lawall@lip6.fr>
To: Liam Breck <liam@networkimprov.net>
Cc: "Julia Lawall" <julia.lawall@lip6.fr>,
"Sebastian Reichel" <sebastian.reichel@collabora.co.uk>,
"Gilles Muller" <Gilles.Muller@lip6.fr>,
"Nicolas Palix" <nicolas.palix@imag.fr>,
"Michal Marek" <mmarek@suse.com>,
cocci@systeme.lip6.fr, "Andrew F. Davis" <afd@ti.com>,
"Pali Rohár" <pali.rohar@gmail.com>,
"Linux PM mailing list" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v3 0/5] bq27xxx_battery data memory update
Date: Wed, 27 Sep 2017 15:25:37 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1709271525180.3186@hadrien> (raw)
In-Reply-To: <CAKvHMgQeMTgVQGk7Xn7ijNWPTPu4kVjM4ZAUUR_X-_nxSC1OBw@mail.gmail.com>
On Wed, 27 Sep 2017, Liam Breck wrote:
> On Wed, Sep 27, 2017 at 3:02 AM, Julia Lawall <julia.lawall@lip6.fr> wrote:
> > The github version of Coccinelle finally supports the semantic patch for
>
> Should we add something to the script that aborts if the correct
> Coccinelle version is not running?
I will prepare a version for integration in the kernel.
julia
>
> > your code. I have attached the semantic patch. I wonder what should be
> > done with this? Do you want to use it locally with make coccicheck? Do
> > you want it to be integrated into the kernel? Everything in the semantic
> > patch depends on the occurrence of BQ27XXX_DATA, so if make coccicheck is
> > used on files that don't contain this word, they should be ignored very
> > efficiently. So perhaps it is ok for scripts/coccinelle even if it is
> > relevant to only one file.
> >
> > julia
>
next prev parent reply other threads:[~2017-09-27 13:25 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 3:36 [PATCH v3 0/5] bq27xxx_battery data memory update Liam Breck
2017-08-24 3:36 ` [PATCH v3 1/5] power: supply: bq27xxx: Create single chip data table Liam Breck
2017-08-24 3:36 ` [PATCH v3 2/5] power: supply: bq27xxx: Add chip IDs for previously shadowed chips Liam Breck
2017-08-24 3:36 ` [PATCH v3 3/5] power: supply: bq27xxx: Enable data memory update for certain chips Liam Breck
2017-08-24 3:36 ` [PATCH v3 4/5] power: supply: bq27xxx: Flag identical chip data when in debug mode Liam Breck
2017-08-24 3:36 ` [PATCH v3 5/5] power: supply: bq27xxx: Remove duplicate chip data arrays Liam Breck
2017-08-29 10:54 ` [PATCH v3 0/5] bq27xxx_battery data memory update Sebastian Reichel
2017-08-29 15:31 ` Andrew F. Davis
2017-08-29 21:22 ` Sebastian Reichel
2017-08-29 23:07 ` Liam Breck
2017-08-30 0:29 ` Sebastian Reichel
2017-08-30 1:14 ` Liam Breck
2017-08-30 6:01 ` Julia Lawall
2017-08-31 9:54 ` Julia Lawall
2017-08-31 11:01 ` Liam Breck
2017-08-31 11:33 ` Julia Lawall
2017-08-31 11:43 ` Liam Breck
2017-09-05 19:15 ` Liam Breck
2017-09-05 20:14 ` Julia Lawall
2017-09-18 0:45 ` Liam Breck
2017-09-18 5:33 ` Julia Lawall
2017-09-19 21:47 ` Liam Breck
2017-09-19 22:00 ` Julia Lawall
2017-09-19 22:36 ` Liam Breck
2017-09-20 9:14 ` Julia Lawall
2017-09-20 9:41 ` Liam Breck
2017-09-20 9:45 ` Julia Lawall
2017-09-20 9:57 ` Liam Breck
2017-09-27 10:02 ` Julia Lawall
2017-09-27 12:02 ` Liam Breck
2017-09-27 12:16 ` Julia Lawall
2017-09-27 12:46 ` Liam Breck
2017-10-01 11:59 ` Julia Lawall
2017-09-27 13:12 ` Liam Breck
2017-09-27 13:25 ` Julia Lawall
2017-09-27 13:25 ` Julia Lawall [this message]
2017-08-29 22:29 ` Liam Breck
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.1709271525180.3186@hadrien \
--to=julia.lawall@lip6.fr \
--cc=Gilles.Muller@lip6.fr \
--cc=afd@ti.com \
--cc=cocci@systeme.lip6.fr \
--cc=liam@networkimprov.net \
--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 \
/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