public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Richard Purdie <rpurdie@openedhand.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Richard Hughes <hughsient@gmail.com>,
	"kay.sievers" <kay.sievers@vrfy.org>,
	"Bryn M. Reeves" <breeves@redhat.com>,
	John Lenz <lenz@cs.wisc.edu>
Subject: Re: [patch] Move led attributes out of device name and into sysfs attributes, was Re: LED devices
Date: Sun, 24 Jun 2007 22:06:06 -0700	[thread overview]
Message-ID: <20070625050606.GC30043@kroah.com> (raw)
In-Reply-To: <1181381117.24811.35.camel@localhost.localdomain>

On Sat, Jun 09, 2007 at 10:25:16AM +0100, Richard Purdie wrote:
> Anyhow, time to stop pretending I have any choice in this ;-). I will
> have the LED class use random numbers for busids and add a name
> attribute unless anyone else voices an opinion.

Thank you, I really appreciate it, and so does the people who write the
tools that parse sysfs (like HAL.)

greg k-h

  reply	other threads:[~2007-06-25  5:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01 15:04 [patch] Move led attributes out of device name and into sysfs attributes, was Re: LED devices Richard Hughes
2007-06-01 15:43 ` Richard Purdie
2007-06-01 15:59   ` Richard Hughes
2007-06-01 16:23     ` Richard Purdie
2007-06-08 18:57       ` Greg KH
2007-06-08 23:02         ` Richard Purdie
2007-06-08 23:46           ` Greg KH
2007-06-09  9:25             ` Richard Purdie
2007-06-25  5:06               ` Greg KH [this message]
2007-06-26 10:02                 ` Richard Purdie
2007-06-26 10:46                   ` Richard Hughes
2007-06-28 19:15                     ` Kay Sievers
2007-06-10 10:11         ` Pavel Machek
2007-06-10 20:02           ` Richard Hughes
2007-06-11  1: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=20070625050606.GC30043@kroah.com \
    --to=greg@kroah.com \
    --cc=breeves@redhat.com \
    --cc=hughsient@gmail.com \
    --cc=kay.sievers@vrfy.org \
    --cc=lenz@cs.wisc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@openedhand.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