From: Julia Lawall <julia.lawall@lip6.fr>
To: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
Cc: Linux PM mailing list <linux-pm@vger.kernel.org>,
Nicolas Palix <nicolas.palix@imag.fr>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Liam Breck <liam@networkimprov.net>,
Michal Marek <mmarek@suse.com>,
pali.rohar@gmail.com, Joe Perches <joe@perches.com>,
kbuild test robot <fengguang.wu@intel.com>,
cocci@systeme.lip6.fr
Subject: Re: [PATCH 0/2] detect identical chip data arrays
Date: Sun, 8 Oct 2017 22:44:50 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1710082243140.2160@hadrien> (raw)
In-Reply-To: <20171008203258.y7kqx7ipondxlsix@earth>
On Sun, 8 Oct 2017, Sebastian Reichel wrote:
> Hi,
>
> On Sun, Oct 08, 2017 at 09:18:39PM +0200, Julia Lawall wrote:
> > Rename battery.cocci as check_bq27xxx_data.cocci and adjust the warning
> > messages to indicate that some structures are the same, in response to
> > feedback from Liam Breck.
> >
> > Although check_bq27xxx_data.cocci says is requires Coccinelle 1.0.7, which
> > is not yet released, it actually works with the version currently available
> > on Github, eg from Coccinelle commit 3ba77b3a0f91.
>
> I think the rename makes sense, but I would expect the move to
> happen in one go with "git send-email -M", so that it detects the
> rename.
I'm not actually sure what is the status of the previous version.
Masahiro said applied, but I downloaded his tree and it was not there. So
I thought this way would be easier.
julia
next prev parent reply other threads:[~2017-10-08 20:44 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
2017-10-08 20:32 ` [PATCH 0/2] " Sebastian Reichel
2017-10-08 20:44 ` Julia Lawall [this message]
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.1710082243140.2160@hadrien \
--to=julia.lawall@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