All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: "Pavel Machek" <pavel@ucw.cz>,
	"Pali Rohár" <pali.rohar@gmail.com>,
	ibm-acpi-devel@lists.sourceforge.net,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Fabio D'Urso" <fabiodurso@hotmail.it>
Subject: Re: [PATCH] thinkpad_acpi: Add support for keyboard backlight
Date: Tue, 12 Jan 2016 08:59:19 -0800	[thread overview]
Message-ID: <20160112165919.GA1989@malice.jf.intel.com> (raw)
In-Reply-To: <1452540480.2848000.489039714.26068C20@webmail.messagingengine.com>

On Mon, Jan 11, 2016 at 05:28:00PM -0200, Henrique de Moraes Holschuh wrote:
 > 
> > Henrique, so are you taking back your Ack from 10 minutes prior?
> 
> Hmm? No, the ACK stands.
> 
> Pavel was talking about another feature altogether, apparently: older
> thinkpads did not have "keyboard backlight" (as in light from below the
> keys).  They had a "ThinkLight", which is an overhead light that shines
> down on the keyboard.
> 
> The two features are not the same (and are handled differently by the
> firmware, for whatever reason), although they do serve the same purpose.
>  I don't think a thinkpad will ever have both features at the same time,
> so I have no idea why they changed the firmware interface.
> 
> The patch adds support to the "keyboard backlight" feature, which was
> previously NOT supported.
> 
> > I've dropped this patch. Please let me know if I should pick it back up.
> 
> Please pick it back up.
> 

Gah, these two threads landed next to each other in my Inbox and I didn't pick
up the split. Apologies.

This is queued in testing (again).

-- 
Darren Hart
Intel Open Source Technology Center

  parent reply	other threads:[~2016-01-12 16:59 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-24 18:46 [PATCH] thinkpad_acpi: Add support for keyboard backlight Pali Rohár
2015-12-27 23:14 ` Henrique de Moraes Holschuh
2015-12-28 14:48   ` Pali Rohár
2015-12-30 22:28     ` Pali Rohár
2016-01-06  8:45       ` Pali Rohár
2016-01-09 17:36         ` Henrique de Moraes Holschuh
2015-12-30 22:27 ` [PATCH v2] " Pali Rohár
2016-01-04 20:04   ` Darren Hart
2016-01-04 20:26     ` Pali Rohár
2016-01-04 20:40       ` Darren Hart
2016-01-04 20:51         ` Pali Rohár
2016-01-04 21:42           ` Darren Hart
2016-01-09 17:34         ` Henrique de Moraes Holschuh
2016-01-04 20:12 ` [PATCH] " Pavel Machek
2016-01-04 20:23   ` Pali Rohár
2016-01-04 20:40     ` Pali Rohár
2016-01-09 17:39   ` Henrique de Moraes Holschuh
     [not found]     ` <1452361154.673684.487414482.6CCEAE4B-2RFepEojUI2N1INw9kWLP6GC3tUn3ZHUQQ4Iyu8u01E@public.gmane.org>
2016-01-09 17:46       ` Henrique de Moraes Holschuh
2016-01-09 17:46         ` Henrique de Moraes Holschuh
2016-01-11 19:04         ` Darren Hart
2016-01-11 19:28           ` Henrique de Moraes Holschuh
2016-01-11 20:03             ` Pali Rohár
2016-01-11 21:12               ` Johannes Stezenbach
2016-01-12 16:07                 ` Henrique de Moraes Holschuh
2016-01-12 16:23                   ` [ibm-acpi-devel] " Yves-Alexis Perez
2016-01-12 16:35                   ` Johannes Stezenbach
2016-01-12 17:56                     ` Henrique de Moraes Holschuh
2016-01-12 22:07                       ` Johannes Stezenbach
2016-01-12 18:11                   ` [ibm-acpi-devel] " Kevin Locke
2016-01-12 18:20                     ` Henrique de Moraes Holschuh
2016-01-12 18:36                       ` Kevin Locke
2016-01-12 16:04               ` Henrique de Moraes Holschuh
2016-01-12 21:58               ` Pavel Machek
2016-01-13  8:54                 ` Pali Rohár
2016-01-13 19:07                   ` Pavel Machek
2016-01-13 19:10                     ` Pavel Machek
2016-01-21  8:57                       ` Pali Rohár
2016-01-11 22:44             ` [ibm-acpi-devel] " Yves-Alexis Perez
2016-01-12 16:59             ` Darren Hart [this message]
2016-01-12 17:51               ` 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=20160112165919.GA1989@malice.jf.intel.com \
    --to=dvhart@infradead.org \
    --cc=fabiodurso@hotmail.it \
    --cc=hmh@hmh.eng.br \
    --cc=ibm-acpi-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=platform-driver-x86@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 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.