public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Seyfried <seife@suse.de>
To: Dave Jones <davej@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>,
	cpufreq@lists.linux.org.uk, alex-kernel@digriz.org.uk,
	Alexander Clouter <alex@digriz.org.uk>,
	LKML <linux-kernel@vger.kernel.org>,
	Blaisorblade <blaisorblade@yahoo.it>
Subject: Re: [patch 1/1] cpufreq_conservative: invert meaning of   'ignore_nice'
Date: Fri, 30 Sep 2005 15:56:56 +0200	[thread overview]
Message-ID: <433D4428.3050906@suse.de> (raw)
In-Reply-To: <20050929215153.GF31516@redhat.com>

Dave Jones wrote:
> On Thu, Sep 29, 2005 at 01:46:33PM +0200, Blaisorblade wrote:

>  > So userspace tools will error out rather than do the reverse of what they were 
>  > doing, and the user will fix the thing according to the (new) docs.
> 
> Agreed. If we change this, we change it completely.
> Stefan already mentioned his app will break, and we typically don't
> find out about widespread breakage until after we ship a release.

I can live with the change - powersaved has a setting "consider_nice" to
configure this and i can put out a support article telling people to
"invert" this setting if they are running custom kernels, so it is not
really a showstopper for me. Most of the users don't understand thos
settings anyway ;-)

I'm not sure what is better for me - a nice short name or a clear
indication on which version we are running ;-)
-- 
Stefan Seyfried                  \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices      \ wanted to be paid for what I write."
SUSE LINUX Products GmbH, Nürnberg \                    -- Leonard Cohen


  reply	other threads:[~2005-09-30 15:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29  8:44 [patch 1/1] cpufreq_conservative: invert meaning of 'ignore_nice' Alexander Clouter
2005-09-29 11:46 ` Blaisorblade
2005-09-29 21:51   ` Dave Jones
2005-09-30 13:56     ` Stefan Seyfried [this message]
2005-09-30  8:09   ` Alexander Clouter

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=433D4428.3050906@suse.de \
    --to=seife@suse.de \
    --cc=akpm@osdl.org \
    --cc=alex-kernel@digriz.org.uk \
    --cc=alex@digriz.org.uk \
    --cc=blaisorblade@yahoo.it \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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