From: Pavel Machek <pavel@ucw.cz>
To: James Simmons <jsimmons@infradead.org>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Alessandro Guido <alessandro.guido@gmail.com>,
linux-kernel@vger.kernel.org, akpm@osdl.org,
linux-acpi@vger.kernel.org, len.brown@intel.com
Subject: Re: [PATCH] acpi: add backlight support to the sony_acpi driver (v2)
Date: Wed, 6 Dec 2006 19:54:04 +0100 [thread overview]
Message-ID: <20061206185404.GA3230@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0612061525140.28745@pentafluge.infradead.org>
Please don't top-post...
> Its nice to see acpi moving to the backlight api. Will acpi also move to
> hwmon and led class support ?
It would be nice... ACPI does not drive many leds ... usually ... but
creating battery API based on hwmon and moving ACPI battery support to
that API would certainly be nice... and I believe it is ongoing work.
Pavel
> > Hi!
> >
> > > > Looks okay to me. We really want unified interface for backlight.
> > >
> > > Then I request some help to get
> > > http://article.gmane.org/gmane.linux.acpi.devel/19792
> > > merged.
> > >
> > > Without it, the backlight interface becomes annoying on laptops. Your
> > > screen will be powered off when you remove the modules providing the
> > > backlight interface. This is not consistent with the needs of laptop
> > > backlight devices, or with the behaviour the drivers had before the
> > > backlight sysfs support was added.
> >
> > Just retransmit it to akpm and list, and add acked-by headers with
> > people who said patch is okay... that included me IIRC.
> >
> >
--
Thanks, Sharp!
prev parent reply other threads:[~2006-12-06 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 16:43 [PATCH] acpi: add backlight support to the sony_acpi driver (v2) Alessandro Guido
2006-12-01 13:35 ` Pavel Machek
2006-12-01 19:43 ` Henrique de Moraes Holschuh
2006-12-02 16:23 ` Pavel Machek
2006-12-06 15:25 ` James Simmons
2006-12-06 18:54 ` Pavel Machek [this message]
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=20061206185404.GA3230@atrey.karlin.mff.cuni.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=alessandro.guido@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=jsimmons@infradead.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--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