From: Tomer Tayar <Tomer.Tayar@qlogic.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: <yuval.mintz@qlogic.com>, Tomer Tayar <Tomer.Tayar@qlogic.com>
Subject: [PATCH v2 net-next 0/2] qed*: Debug data collection
Date: Wed, 7 Sep 2016 16:36:23 +0300 [thread overview]
Message-ID: <1473255385-1702-1-git-send-email-Tomer.Tayar@qlogic.com> (raw)
This patch series adds the support of debug data collection in the qed driver,
and the means to extract it in the qede driver via the get_regs operation.
Hi Dave,
Please consider applying this to 'net-next'.
Thanks,
Tomer
Changes from V1:
- Respin of the series after rebasing next-next.
- Remove the first patch as it seems that its V1 version was already applied
(commit '4102426f9b7b3627c8c23a54d70363e81c93f9b7').
Tomer Tayar (2):
qed: Add support for debug data collection
qed*: Add support for the ethtool get_regs operation
drivers/net/ethernet/qlogic/qed/Makefile | 2 +-
drivers/net/ethernet/qlogic/qed/qed.h | 20 +
drivers/net/ethernet/qlogic/qed/qed_debug.c | 6898 +++++++++++++++++++++++
drivers/net/ethernet/qlogic/qed/qed_debug.h | 54 +
drivers/net/ethernet/qlogic/qed/qed_hsi.h | 1056 +++-
drivers/net/ethernet/qlogic/qed/qed_main.c | 6 +
drivers/net/ethernet/qlogic/qed/qed_reg_addr.h | 894 +++
drivers/net/ethernet/qlogic/qede/qede_ethtool.c | 24 +
include/linux/qed/common_hsi.h | 3 +
include/linux/qed/qed_if.h | 4 +
10 files changed, 8949 insertions(+), 12 deletions(-)
create mode 100644 drivers/net/ethernet/qlogic/qed/qed_debug.c
create mode 100644 drivers/net/ethernet/qlogic/qed/qed_debug.h
--
1.8.3.1
next reply other threads:[~2016-09-07 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 13:36 Tomer Tayar [this message]
2016-09-07 13:36 ` [PATCH v2 net-next 1/2] qed: Add support for debug data collection Tomer Tayar
2016-09-07 13:36 ` [PATCH v2 net-next 2/2] qed*: Add support for the ethtool get_regs operation Tomer Tayar
2016-09-08 0:47 ` [PATCH v2 net-next 0/2] qed*: Debug data collection David Miller
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=1473255385-1702-1-git-send-email-Tomer.Tayar@qlogic.com \
--to=tomer.tayar@qlogic.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=yuval.mintz@qlogic.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;
as well as URLs for NNTP newsgroup(s).