From: Andrew Morton <akpm@linux-foundation.org>
To: Len Brown <lenb@kernel.org>
Cc: mjg59@srcf.ucam.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH] Rationalise ACPI backlight implementation
Date: Sat, 26 Jan 2008 22:00:45 -0800 [thread overview]
Message-ID: <20080126220045.b93db7c9.akpm@linux-foundation.org> (raw)
In-Reply-To: <200801241644.49114.lenb@kernel.org>
> On Thu, 24 Jan 2008 16:44:48 -0500 Len Brown <lenb@kernel.org> wrote:
> On Tuesday 25 December 2007 21:03, Matthew Garrett wrote:
> > The sysfs backlight class provides no mechanism for querying the
> > acceptable brightness for a backlight. The ACPI spec states that values
> > are only valid if they are reported as available by the firmware. Since
> > we can't provide that information to userspace, instead collapse the
> > range to the number of actual values that can be set.
> >
> > Signed-off-by: Matthew Garrett <mjg59@srcf.ucam.org>
>
> I wish we did this in the first place.
> But doing it now is an API change -- since
> with the old way 100 always meant 100% brightness, yes?
>
> so my concern is that if we change what "10" means, somebody like akpm
> with an existing script gets grumpy.
It takes more than that to make me grumpy. I've been very grumpy lately.
- Create a new /sys node with a new name which has the new semantics.
- Deprecate the old /sys entry by emitting an angry printk when someone
uses it.
- Wait 12 months
- Kill the old one.
next prev parent reply other threads:[~2008-01-27 6:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-26 2:03 [PATCH] Rationalise ACPI backlight implementation Matthew Garrett
2008-01-14 1:51 ` Matthew Garrett
2008-01-22 8:33 ` Zhang Rui
2008-01-22 11:46 ` Matthew Garrett
2008-01-22 12:39 ` Henrique de Moraes Holschuh
2008-01-24 21:44 ` Len Brown
2008-01-27 2:06 ` Matthew Garrett
2008-01-27 6:00 ` Andrew Morton [this message]
2008-01-28 1:25 ` Matthew Garrett
2008-01-28 5:10 ` Andrew Morton
2008-01-28 5:28 ` Matthew Garrett
2008-01-28 15:51 ` Henrique de Moraes Holschuh
2008-02-02 3:46 ` Len Brown
2008-02-02 11:30 ` Henrique de Moraes Holschuh
2008-02-06 10:09 ` Romano Giannetti
2008-02-06 10:09 ` Romano Giannetti
2008-02-02 3:43 ` Len Brown
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=20080126220045.b93db7c9.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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 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.