From: Catherine Sullivan <catherine.sullivan@intel.com>
To: netdev@vger.kernel.org
Subject: [NET_NEXT RFC PATCH 0/3] Series short description
Date: Wed, 09 May 2012 16:09:34 -0700 [thread overview]
Message-ID: <20120509230814.31910.80709.stgit@localhost6.localdomain6> (raw)
The following patches add debugfs support to the ixgbe driver to give users the
ability to call functions registered in netdev_ops (simulating kernel actions)
as well as the ability to read and write to individual HW registers on the fly.
These options can be useful when debugging and unit testing ixgbe.
The following series implements...
---
Catherine Sullivan (3):
ixgbe: added reg_ops file to debugfs
ixgbe: added netdev_ops file to debugfs
ixgbe: add debugfs support
drivers/net/ethernet/intel/ixgbe/Makefile | 2
drivers/net/ethernet/intel/ixgbe/ixgbe.h | 10 +
drivers/net/ethernet/intel/ixgbe/ixgbe_debugfs.c | 293 ++++++++++++++++++++++
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 17 +
4 files changed, 320 insertions(+), 2 deletions(-)
create mode 100644 drivers/net/ethernet/intel/ixgbe/ixgbe_debugfs.c
--
Catherine Sullivan
next reply other threads:[~2012-05-09 23:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 23:09 Catherine Sullivan [this message]
2012-05-09 23:09 ` [NET_NEXT RFC PATCH 1/3] ixgbe: add debugfs support Catherine Sullivan
2012-05-09 23:10 ` Stephen Hemminger
2012-05-18 17:10 ` Sullivan, Catherine
2012-05-09 23:09 ` [NET_NEXT RFC PATCH 2/3] ixgbe: added netdev_ops file to debugfs Catherine Sullivan
2012-05-09 23:10 ` Stephen Hemminger
2012-05-09 23:13 ` Stephen Hemminger
2012-05-10 20:28 ` Sullivan, Catherine
2012-05-10 20:32 ` David Miller
2012-05-10 21:14 ` Sullivan, Catherine
2012-05-10 21:21 ` David Miller
2012-05-10 21:35 ` Stephen Hemminger
2012-05-10 22:29 ` Sullivan, Catherine
2012-05-09 23:09 ` [NET_NEXT RFC PATCH 3/3] ixgbe: added reg_ops " Catherine Sullivan
2012-05-09 23:14 ` Stephen Hemminger
2012-05-10 0:18 ` Ben Hutchings
2012-05-10 3:54 ` Stephen Hemminger
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=20120509230814.31910.80709.stgit@localhost6.localdomain6 \
--to=catherine.sullivan@intel.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).