public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Thomas Renninger <trenn@suse.de>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@suse.cz>,
	Stefan Seyfried <seife@suse.de>,
	linux-pm@lists.osdl.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH, RFC] [1/3] Generic in-kernel AC status
Date: Wed, 15 Feb 2006 12:47:29 +0000	[thread overview]
Message-ID: <20060215124729.GA10968@srcf.ucam.org> (raw)
In-Reply-To: <43F3206B.6090902@suse.de>

On Wed, Feb 15, 2006 at 01:36:59PM +0100, Thomas Renninger wrote:

> Maybe I oversaw an issue, but I really don't see a reason for connecting
> the brightness to ac in kernel space.

The backlight class maintainer specified that /sys/../brightness should 
return the *current* brightness. In some cases that's impossible without 
knowing the ac status.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2006-02-15 12:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08 12:57 [PATCH, RFC] [1/3] Generic in-kernel AC status Matthew Garrett
2006-02-08 13:03 ` [PATCH, RFC] [2/3] ACPI support for generic " Matthew Garrett
2006-02-08 13:04 ` [PATCH, RFC] [1/3] Generic " Matthew Garrett
2006-02-08 13:05   ` [PATCH, RFC] [3/3] APM support for generic " Matthew Garrett
2006-02-08 16:58   ` [linux-pm] Re: [PATCH, RFC] [1/3] Generic " Greg KH
2006-02-08 17:08     ` Matthew Garrett
2006-02-08 17:16       ` Greg KH
2006-02-08 17:49         ` Matthew Garrett
2006-02-09  5:46           ` Greg KH
2006-02-09  8:53       ` Gabor Gombas
2006-02-10 12:21         ` Pavel Machek
2006-02-10 13:13           ` Gabor Gombas
2006-02-10 13:19             ` Matthew Garrett
2006-02-10 13:54             ` Pavel Machek
2006-02-10 13:56               ` Gabor Gombas
2006-02-08 22:25   ` Philipp Matthias Hahn
2006-02-10 12:21     ` Pavel Machek
2006-02-10  8:06 ` Stefan Seyfried
2006-02-10 12:19   ` Pavel Machek
2006-02-10 12:32     ` Stefan Seyfried
2006-02-10 13:46       ` Pavel Machek
2006-02-12 10:17         ` Jan Engelhardt
2006-02-12 11:27           ` Kyle Moffett
2006-02-14 17:44     ` Thomas Renninger
2006-02-14 20:17       ` Rafael J. Wysocki
2006-02-15 12:36         ` Thomas Renninger
2006-02-15 12:47           ` Matthew Garrett [this message]
2006-02-15 15:04             ` Thomas Renninger
2006-02-16 22:44           ` Pavel Machek
2006-02-16 22:39         ` Pavel Machek

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=20060215124729.GA10968@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=pavel@suse.cz \
    --cc=rjw@sisk.pl \
    --cc=seife@suse.de \
    --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