From: Yuval Mintz <Yuval.Mintz@qlogic.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: Yuval Mintz <Yuval.Mintz@qlogic.com>
Subject: [PATCH net-next v2 0/4] qed*: driver updates
Date: Fri, 22 Apr 2016 08:41:00 +0300 [thread overview]
Message-ID: <1461303664-15961-1-git-send-email-Yuval.Mintz@qlogic.com> (raw)
[Was previous termed 'eeprom access et al.', but seemed a bit
inappropriate given we've dropped the eeprom patch for now.
Still waiting for some inputs on that one, BTW]
This patch series contains some ethtool-related enhancements.
Dave,
Please consider applying this to `net-next'.
Thanks [and happy Passover],
Yuval
Changes
-------
- V1: Dropped eeprom access until it's decided how to address that.
Semantically changed patch #2 [Feedback from Sergei Shtylyov].
Sudarsana Reddy Kalluru (1):
qed: add support for link pause configuration.
Yuval Mintz (3):
qed*: Align statistics names
qede: Add support for ethtool private flags
qed*: Conditions for changing link
drivers/net/ethernet/qlogic/qed/qed_l2.c | 20 ++++-----
drivers/net/ethernet/qlogic/qed/qed_main.c | 20 +++++++++
drivers/net/ethernet/qlogic/qede/qede.h | 20 ++++-----
drivers/net/ethernet/qlogic/qede/qede_ethtool.c | 57 +++++++++++++++++++------
drivers/net/ethernet/qlogic/qede/qede_main.c | 29 ++++++++-----
include/linux/qed/qed_if.h | 30 ++++++++-----
6 files changed, 122 insertions(+), 54 deletions(-)
--
1.9.3
next reply other threads:[~2016-04-22 5:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 5:41 Yuval Mintz [this message]
2016-04-22 5:41 ` [PATCH net-next v2 1/4] qed*: Align statistics names Yuval Mintz
2016-04-22 5:41 ` [PATCH net-next v2 2/4] qede: Add support for ethtool private flags Yuval Mintz
2016-04-22 5:41 ` [PATCH net-next v2 3/4] qed*: Conditions for changing link Yuval Mintz
2016-04-22 5:41 ` [PATCH net-next v2 4/4] qed: add support for link pause configuration Yuval Mintz
2016-04-25 19:59 ` [PATCH net-next v2 0/4] qed*: driver updates 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=1461303664-15961-1-git-send-email-Yuval.Mintz@qlogic.com \
--to=yuval.mintz@qlogic.com \
--cc=davem@davemloft.net \
--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).