From: Eric Cooper <ecc@cmu.edu>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Richard Purdie <rpurdie@rpsys.net>,
Randy Dunlap <rdunlap@xenotime.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH v2] add netdev led trigger
Date: Tue, 30 Nov 2010 19:03:00 -0500 [thread overview]
Message-ID: <20101201000300.GJ21496@localhost> (raw)
In-Reply-To: <87ipzgl9k8.fsf@basil.nowhere.org>
On Mon, Nov 29, 2010 at 11:15:51AM +0100, Andi Kleen wrote:
> Using the device name as an identifier is not reliable, they may not
> be unique.
I'm confused about this -- how else can the user specify the desired network
interface?
> rwlocks are deprecated.
In favor of what? Should I use a spinlock?
Thanks for the feedback.
--
Eric Cooper e c c @ c m u . e d u
next prev parent reply other threads:[~2010-12-01 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1290998056-8310-1-git-send-email-ecc@cmu.edu>
2010-11-29 10:15 ` [PATCH v2] add netdev led trigger Andi Kleen
2010-12-01 0:03 ` Eric Cooper [this message]
2010-12-01 14:03 ` Andi Kleen
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=20101201000300.GJ21496@localhost \
--to=ecc@cmu.edu \
--cc=andi@firstfloor.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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).