From: Thomas Renninger <trenn@suse.de>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-pm@vger.kernel.org
Subject: Re: [PATCH 0/1] cpupower: Add cpuidle library
Date: Thu, 28 Apr 2016 15:23:05 +0200 [thread overview]
Message-ID: <9049803.y9XhT0fdX4@skinner> (raw)
In-Reply-To: <2574684.bDi1t35TAq@vostro.rjw.lan>
On Tuesday, April 26, 2016 10:20:00 PM Rafael J. Wysocki wrote:
> On Monday, April 25, 2016 04:30:09 PM Thomas Renninger wrote:
> > Hi,
> >
> > this is a cleanup I wanted to do for a long time.
> > I already added the change to our build service and things
> > still build against the same archs like arm, ppc, x86:
> > https://build.opensuse.org/package/show/hardware/cpupower
> >
> > It would be nice to get the one or other review.
> >
> > Rafael: If you could queue this up for mainline inclusion at some
> > point of time, I would very much appreciate it!
>
> I can do it right now, but there are a few cpupower patches in Patchwork
> that I'm not sure what to do with.
Where do I find the patchwork stuff?
> Do you want me to drop those on the floor?
No, please not.
I went through the list and found some patches.
Not critical, but valid fixes.
The one from Mattia already was in, in another form.
I will send them right now.
This should now more or less match with what patchwork
gives you?
Thanks,
Thomas
next prev parent reply other threads:[~2016-04-28 13:23 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 [this message]
2016-04-28 15:37 ` Rafael J. Wysocki
2016-04-29 6:57 ` Thomas Renninger
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=9049803.y9XhT0fdX4@skinner \
--to=trenn@suse.de \
--cc=linux-pm@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.