Linux Power Management development
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: Joe Perches <joe@perches.com>
Cc: "Masahiro Yamada" <yamada.masahiro@socionext.com>,
	"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,
	"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] coccinelle: api: detect duplicate chip data arrays
Date: Thu, 5 Oct 2017 21:57:00 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1710052154310.2626@hadrien> (raw)
In-Reply-To: <1507233246.4434.44.camel@perches.com>



On Thu, 5 Oct 2017, Joe Perches wrote:

> On Thu, 2017-10-05 at 21:40 +0200, Julia Lawall wrote:
> > On Thu, 5 Oct 2017, Joe Perches wrote:
> > > btw: spatch 1.7 doesn't seem to have a tag in git
> > >
> > > From the script:
> > >
> > >     // Requires: 1.0.7
> > >
> > > Assuming this is correct, then this doesn't even run today
> > > except maybe on your system.
> >
> > It runs on the current github version.  If you don't have the github
> > version it will suffer from false negatives, but nothing will break.
>
> fyi: there's no tag for 1.0.7 there either.

Yes, I know.  1.0.7 doesn't exist.  I didn't think it would be meaningful
to put the actual version I get with 1.0.6 with the commit id, because
commit ids aren't ordered.  I hoped that 1.0.7 would be released, but I
haven't gotten confirmation that all of the makefile issues have been
resolved.

julia

  reply	other threads:[~2017-10-05 19:57 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 [this message]
2017-10-05 19:46           ` Liam Breck
2017-10-05 19:54             ` Joe Perches
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=alpine.DEB.2.20.1710052154310.2626@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