From: Richard Purdie <rpurdie@rpsys.net>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Matthew Garrett <mjg@redhat.com>,
linux-acpi@vger.kernel.org, ibm-acpi-devel@lists.sourceforge.net
Subject: Re: [GIT PATCH] backlight event support enhancements
Date: Mon, 21 Sep 2009 00:41:42 +0100 [thread overview]
Message-ID: <1253490102.564.3.camel@ted> (raw)
In-Reply-To: <1253468688-4933-1-git-send-email-hmh@hmh.eng.br>
On Sun, 2009-09-20 at 14:44 -0300, Henrique de Moraes Holschuh wrote:
> This two-patch patchset adds poll() support to Matthew's backlight event
> work, and also adds backlight event support for thinkpad-acpi.
>
> The thinkpad-acpi changes depend on a patchset I just sent to Len Brown
> for merging in acpi-test.
>
> Is there any timeframe for the backlight event support to be sent to
> mainline?
I'm going to try and get the event patches in this merge window if I
can. I'm going to have intermittent internet access for a few days but I
will send a pull request for the backlight tree over that time period.
Whats the timeframe for acpi-test merging?
Cheers,
Richard
--
Richard Purdie
Intel Open Source Technology Centre
next prev parent reply other threads:[~2009-09-20 23:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 17:44 [GIT PATCH] backlight event support enhancements Henrique de Moraes Holschuh
2009-09-20 17:44 ` [PATCH 1/2] backlight: extend event support to also support poll() Henrique de Moraes Holschuh
2009-09-20 17:44 ` [PATCH 2/2] thinkpad-acpi: issue backlight class events Henrique de Moraes Holschuh
2009-09-20 23:41 ` Richard Purdie [this message]
2009-09-21 12:28 ` [GIT PATCH] backlight event support enhancements Henrique de Moraes Holschuh
2009-09-26 19:55 ` Henrique de Moraes Holschuh
2009-09-26 23:35 ` Richard Purdie
2009-09-26 23:57 ` Henrique de Moraes Holschuh
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=1253490102.564.3.camel@ted \
--to=rpurdie@rpsys.net \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg@redhat.com \
/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