From: David Miller <davem@davemloft.net>
To: f.fainelli@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: document sysfs entries
Date: Mon, 31 Mar 2014 16:11:00 -0400 (EDT) [thread overview]
Message-ID: <20140331.161100.642930165214073947.davem@davemloft.net> (raw)
In-Reply-To: <1396041958-2471-1-git-send-email-f.fainelli@gmail.com>
From: Florian Fainelli <f.fainelli@gmail.com>
Date: Fri, 28 Mar 2014 14:25:56 -0700
> This patchset attempts to document the basic set of sysfs entries that are
> exposed by netdevices in /sys/class/net/<iface>/
>
> I did not go before the pre-git era, so the oldest entries are marked with
> the 2.6.12 kernel version and dated of April 2005.
>
> Future patches will document the queues/ and statistics/ directories as well.
Series applied, thanks for doing this Florian.
prev parent reply other threads:[~2014-03-31 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 21:25 [PATCH net-next 0/2] net: document sysfs entries Florian Fainelli
2014-03-28 21:25 ` [PATCH net-next 1/2] net: sysfs: add Documentation entries for basic set of attributes Florian Fainelli
2014-03-28 21:25 ` [PATCH net-next 2/2] net: export NET_ADDR_* values to user-space API Florian Fainelli
2014-03-31 20:11 ` David Miller [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=20140331.161100.642930165214073947.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).