From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Thomas Renninger <trenn@suse.de>
Cc: cpufreq@vger.kernel.org
Subject: Re: [cpupower] RFC: support "cpupower subcommand [ -c cpulist ]"
Date: Wed, 10 Aug 2011 13:27:20 +0200 [thread overview]
Message-ID: <20110810112720.GA4649@isilmar-3.linta.de> (raw)
In-Reply-To: <201108100900.12243.trenn@suse.de>
On Wed, Aug 10, 2011 at 09:00:11AM +0200, Thomas Renninger wrote:
> On Saturday 06 August 2011 17:18:29 Dominik Brodowski wrote:
> > Currently, one needs to set the cpulist _before_ the subcommand, i.e.
> >
> > cpupower [ -c cpulist ] subcommand [ARGS]
> >
> > However, cpufrequtils used to allow to have "-c CPU" as a parameter to
> > cpufreq-set(1) or cpufreq-info(1). Therefore, it may make sense to also
> > support
> Why exactly would this be an enhancement?
> To be able to create an alias easier?
Exactly. Also,
$ cpufreq-set -c 0 -g powersave
would translate more intuitively to
$ cpupower frequency-set -c 0 g powersave
> > cpupower subcommand [ARGS#1] [ -c cpulist ] [ARGS#2]
> >
> > The attached patch attempts to do so, but I'm not yet 100% convinced myself
> > that a) we should do this at all, and b) that I chose the right approach.
> I'd not try to do that.
Best,
Dominik
next prev parent reply other threads:[~2011-08-10 11:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 15:18 [cpupower] RFC: support "cpupower subcommand [ -c cpulist ]" Dominik Brodowski
2011-08-10 7:00 ` Thomas Renninger
2011-08-10 11:27 ` Dominik Brodowski [this message]
2011-08-11 21:48 ` Thomas Renninger
2011-08-15 17:54 ` Dominik Brodowski
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=20110810112720.GA4649@isilmar-3.linta.de \
--to=linux@dominikbrodowski.net \
--cc=cpufreq@vger.kernel.org \
--cc=trenn@suse.de \
/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