From: Thomas Renninger <trenn@suse.de>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Arjun Sreedharan <arjun024@gmail.com>
Subject: Re: [PATCH 0/1] cpupower: Add cpuidle library
Date: Fri, 29 Apr 2016 08:57:50 +0200 [thread overview]
Message-ID: <31806757.JiaQphXfhu@skinner> (raw)
In-Reply-To: <CAJZ5v0hpwK=G=HCRk17f1v=nNtKGoVqc77cbRPtiGVpy2Tfg2A@mail.gmail.com>
On Thursday, April 28, 2016 05:37:38 PM Rafael J. Wysocki wrote:
> On Thu, Apr 28, 2016 at 3:23 PM, Thomas Renninger <trenn@suse.de> wrote:
> > On Tuesday, April 26, 2
...
> > This should now more or less match with what patchwork
> > gives you?
>
> That's about right. There is one more patch in Patchwork that is not
> present in your series:
>
> https://patchwork.kernel.org/patch/8301391/
Thanks, I have overseen this one.
> I've queued up your series for 4.7, but I'm still unsure about the above
> one.
Ah, I also wanted to fix this and then decided it's not worth it.
But now that we have a patch (compile tested from my side, looks
correct).
This fixes cppcheck error:
Checking bench/parse.c...
[bench/parse.c:91]: (error) Common realloc mistake: 'filename' nulled but not
freed upon failure
I had to merge this one on top of the others, I'll send the adjusted
version in a minute.
Thanks!
Thomas
prev parent reply other threads:[~2016-04-29 6:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 14:30 [PATCH 0/1] cpupower: Add cpuidle library Thomas Renninger
2016-04-25 14:34 ` [PATCH 1/1] cpupower: Add cpuidle parts into library Thomas Renninger
2016-04-26 20:27 ` Rafael J. Wysocki
2016-04-26 20:20 ` [PATCH 0/1] cpupower: Add cpuidle library Rafael J. Wysocki
2016-04-28 13:23 ` Thomas Renninger
2016-04-28 15:37 ` Rafael J. Wysocki
2016-04-29 6:57 ` Thomas Renninger [this message]
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=31806757.JiaQphXfhu@skinner \
--to=trenn@suse.de \
--cc=arjun024@gmail.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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