linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Colin Cross <ccross@android.com>
Cc: linux-kernel@vger.kernel.org,
	Greg KH <gregkh@linuxfoundation.org>,
	Bryan Wu <bryan.wu@canonical.com>,
	Richard Purdie <rpurdie@rpsys.net>,
	linux-leds@vger.kernel.org
Subject: Re: [PATCH v2] leds: triggers: send uevent when changing triggers
Date: Tue, 7 Aug 2012 22:12:46 -0300	[thread overview]
Message-ID: <20120808011245.GC640@khazad-dum.debian.net> (raw)
In-Reply-To: <1344369495-21943-1-git-send-email-ccross@android.com>

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>

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  parent reply	other threads:[~2012-08-08  1:12 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 [this message]
2012-08-08  2:16   ` Bryan Wu
2012-08-14 11:34     ` Bryan Wu
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=20120808011245.GC640@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=bryan.wu@canonical.com \
    --cc=ccross@android.com \
    --cc=gregkh@linuxfoundation.org \
    --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).