From: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
To: davem@davemloft.net, netdev@vger.kernel.org, fengguang.wu@intel.com
Cc: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
Subject: [PATCH net-next v2 0/3] net: qualcomm: rmnet: Updates 2018-05-14
Date: Tue, 15 May 2018 18:51:59 -0600 [thread overview]
Message-ID: <1526431922-4132-1-git-send-email-subashab@codeaurora.org> (raw)
Patch 1 adds tx_drops counter to more places.
Patch 2 adds ethtool private stats support to make it easy to debug
the checksum offload path.
Patch 3 is a cleanup in command packet processing path.
v1->v2: Fix the incorrect if / else statement in
rmnet_map_checksum_downlink_packet() and define rmnet_ethtool_ops
as static as mentioned by kbuild test robot.
Subash Abhinov Kasiviswanathan (3):
net: qualcomm: rmnet: Capture all drops in transmit path
net: qualcomm: rmnet: Add support for ethtool private stats
net: qualcomm: rmnet: Remove redundant command check
drivers/net/ethernet/qualcomm/rmnet/rmnet_config.h | 13 +++++
.../net/ethernet/qualcomm/rmnet/rmnet_handlers.c | 21 ++++---
.../ethernet/qualcomm/rmnet/rmnet_map_command.c | 14 +----
.../net/ethernet/qualcomm/rmnet/rmnet_map_data.c | 64 ++++++++++++++++------
drivers/net/ethernet/qualcomm/rmnet/rmnet_vnd.c | 51 +++++++++++++++++
5 files changed, 125 insertions(+), 38 deletions(-)
--
1.9.1
next reply other threads:[~2018-05-16 0:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 0:51 Subash Abhinov Kasiviswanathan [this message]
2018-05-16 0:52 ` [PATCH net-next v2 1/3] net: qualcomm: rmnet: Capture all drops in transmit path Subash Abhinov Kasiviswanathan
2018-05-16 0:52 ` [PATCH net-next v2 2/3] net: qualcomm: rmnet: Add support for ethtool private stats Subash Abhinov Kasiviswanathan
2018-05-16 0:52 ` [PATCH net-next v2 3/3] net: qualcomm: rmnet: Remove redundant command check Subash Abhinov Kasiviswanathan
2018-05-16 18:23 ` [PATCH net-next v2 0/3] net: qualcomm: rmnet: Updates 2018-05-14 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=1526431922-4132-1-git-send-email-subashab@codeaurora.org \
--to=subashab@codeaurora.org \
--cc=davem@davemloft.net \
--cc=fengguang.wu@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).