From: Eric Cooper <ecc@cmu.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] add netdev led trigger
Date: Sun, 21 Nov 2010 15:53:41 -0500 [thread overview]
Message-ID: <20101121205341.GB28164@localhost> (raw)
In-Reply-To: <20101117160919.GC10992@kroah.com>
On Wed, Nov 17, 2010 at 08:09:19AM -0800, Greg KH wrote:
> Documentation/ABI is the correct place for it.
Should I just add descriptions of the additional attributes to the end
of the existing Documentation/ABI/testing/sysfs-class-led file? If
so, how should I indicate that these attributes pertain only when the
ledtrig-netdev trigger is in use?
Or should I create a file specific to this trigger, and if so, what
should it be named?
--
Eric Cooper e c c @ c m u . e d u
prev parent reply other threads:[~2010-11-21 20:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 20:58 [PATCH] add netdev led trigger Eric Cooper
2010-11-15 23:41 ` Lars-Peter Clausen
2010-11-17 11:05 ` Pavel Machek
2010-11-17 16:09 ` Greg KH
2010-11-17 19:58 ` Pavel Machek
2010-11-17 20:01 ` Greg KH
2010-11-17 20:06 ` Eric Cooper
2010-11-30 19:20 ` Pavel Machek
2010-11-30 23:22 ` Eric Cooper
2010-12-01 19:56 ` Pavel Machek
2010-11-21 20:53 ` Eric Cooper [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=20101121205341.GB28164@localhost \
--to=ecc@cmu.edu \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox