From: Bryan Wu <bryan.wu@canonical.com>
To: Colin Cross <ccross@android.com>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: linux-kernel@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>,
Richard Purdie <rpurdie@rpsys.net>,
linux-leds@vger.kernel.org
Subject: Re: [PATCH v2] leds: triggers: send uevent when changing triggers
Date: Tue, 14 Aug 2012 19:34:59 +0800 [thread overview]
Message-ID: <CAK5ve-LUaRzhUs4AvVUvT4xZkdvGL-9WcJyJQ0S463CyWe+Jow@mail.gmail.com> (raw)
In-Reply-To: <CAK5ve-L4JJ_HX5+csMbac_PYO=4mR2tVNsP3SGEvTnYYEbg46g@mail.gmail.com>
On Wed, Aug 8, 2012 at 10:16 AM, Bryan Wu <bryan.wu@canonical.com> wrote:
> On Wed, Aug 8, 2012 at 9:12 AM, Henrique de Moraes Holschuh
> <hmh@hmh.eng.br> wrote:
>> On Tue, 07 Aug 2012, Colin Cross wrote:
>>> Some triggers create sysfs files when they are enabled. Send a uevent
>>> "change" notification whenever the trigger is changed to allow userspace
>>> processes such as udev to modify permissions on the new files.
>>>
>>> A change notification will also be sent during registration of led class
>>> devices or led triggers if the default trigger of an led class device
>>> is found.
>>>
>>> Signed-off-by: Colin Cross <ccross@android.com>
>>
>> Acked-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
>>
>
> Colin, could you please resend an update patch with some
> documentations as Henrique pointed out? Then I will add Ack from
> Henrique and Greg and apply this patch.
>
Colin, will you update the patch or just keep this one.
-Bryan
next prev parent reply other threads:[~2012-08-14 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 19:58 [PATCH v2] leds: triggers: send uevent when changing triggers Colin Cross
2012-08-07 20:42 ` Greg KH
2012-08-07 20:47 ` Colin Cross
2012-08-07 20:56 ` Greg KH
2012-08-07 20:57 ` Greg KH
2012-08-08 1:12 ` Henrique de Moraes Holschuh
2012-08-08 2:16 ` Bryan Wu
2012-08-14 11:34 ` Bryan Wu [this message]
2012-08-27 1:43 ` Bryan Wu
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=CAK5ve-LUaRzhUs4AvVUvT4xZkdvGL-9WcJyJQ0S463CyWe+Jow@mail.gmail.com \
--to=bryan.wu@canonical.com \
--cc=ccross@android.com \
--cc=gregkh@linuxfoundation.org \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@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).