From: Hans de Goede <hdegoede@redhat.com>
To: "Jacek Anaszewski" <j.anaszewski@samsung.com>,
"Darren Hart" <dvhart@infradead.org>,
"Matthew Garrett" <mjg59@srcf.ucam.org>,
"Pali Rohár" <pali.rohar@gmail.com>,
"Henrique de Moraes Holschuh" <ibm-acpi@hmh.eng.br>,
"Richard Purdie" <rpurdie@rpsys.net>
Cc: ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH v4 1/4] leds: core: Add support for poll()ing the sysfs brightness attr for changes.
Date: Tue, 8 Nov 2016 14:16:27 +0100 [thread overview]
Message-ID: <b703c452-4b9d-639d-24e7-490812a1e9f6@redhat.com> (raw)
In-Reply-To: <0c67637a-af0d-4974-eed6-efb186e91635@samsung.com>
Hi,
On 08-11-16 14:08, Jacek Anaszewski wrote:
> On 11/08/2016 01:31 PM, Hans de Goede wrote:
>> Hi,
>>
>> On 08-11-16 12:52, Jacek Anaszewski wrote:
>>> Hi Hans,
>>>
>>> I've tested it with userspace test application and it seems to work
>>> well both with hardware leds-aat1290 driver and drivers/leds/uleds.c.
>>>
>>> Applied to the for-next branch of linux-leds.git.
>>
>> Great, thank you. Can you also add a stable branch / tag with this
>> commit which the platform/x86 maintainer can merge into his tree,
>> so that he can merge the platform/x86 driver changes which depend
>> up on the new led_notify_brightness_change() function ?
>
> Sure. I've created stable led_brightness_pollpri branch on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git
Thank you.
Darren, can you merge this tag and patches 2-4 of this series please ?
Regards,
Hans
prev parent reply other threads:[~2016-11-08 13:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161101133800eucas1p19df1b7f85ad751fcf98e60277b207296@eucas1p1.samsung.com>
2016-11-01 13:37 ` [PATCH v4 1/4] leds: core: Add support for poll()ing the sysfs brightness attr for changes Hans de Goede
2016-11-01 13:37 ` [PATCH v4 2/4] platform: x86: thinkpad: Call led_notify_brightness_change on kbd brightness change Hans de Goede
2016-11-11 14:12 ` Pali Rohár
2016-11-11 14:33 ` Hans de Goede
2016-11-11 14:46 ` Pali Rohár
[not found] ` <f90bd318-9f3f-62e4-be49-e03cae4eac14-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-11-11 18:40 ` Kevin Locke
2016-11-12 11:52 ` [ibm-acpi-devel] " Pali Rohár
2016-11-12 12:07 ` Hans de Goede
2016-11-01 13:37 ` [PATCH v4 3/4] platform: x86: dell-*: Add a generic dell-laptop notifier chain Hans de Goede
2016-11-11 14:17 ` Pali Rohár
2016-11-11 14:36 ` Hans de Goede
2016-11-01 13:37 ` [PATCH v4 4/4] platform: x86: dell-*: Call led_notify_brightness_change on kbd brightness change Hans de Goede
2016-11-08 11:52 ` [PATCH v4 1/4] leds: core: Add support for poll()ing the sysfs brightness attr for changes Jacek Anaszewski
[not found] ` <5021470c-705b-6920-708e-dd5fca13951f-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2016-11-08 12:31 ` Hans de Goede
2016-11-08 13:08 ` Jacek Anaszewski
2016-11-08 13:16 ` Hans de Goede [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=b703c452-4b9d-639d-24e7-490812a1e9f6@redhat.com \
--to=hdegoede@redhat.com \
--cc=dvhart@infradead.org \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ibm-acpi@hmh.eng.br \
--cc=j.anaszewski@samsung.com \
--cc=linux-leds@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=pali.rohar@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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;
as well as URLs for NNTP newsgroup(s).