From: Govindarajulu Varadarajan <_govind@gmx.com>
To: davem@davemloft.net, netdev@vger.kernel.org
Cc: Govindarajulu Varadarajan <_govind@gmx.com>,
David Dillow <dave@thedillows.org>,
Don Fry <pcnet32@frontier.com>,
Francois Romieu <romieu@fr.zoreil.com>
Subject: [PATCH net-next 0/3] Remove rx_copybreak module param, use ethtool to change its value
Date: Wed, 17 Sep 2014 02:21:24 +0530 [thread overview]
Message-ID: <1410900687-9686-1-git-send-email-_govind@gmx.com> (raw)
Recently rx_copybreak support for ethtool has been added in
commit: f0db9b073415848709dd59a6394969882f517da9
ethtool: Add generic options for tunables
we can use ethtool to change the rx_copybreak value.
This series removes the rx_copybreak module param and adds ethtool support for
the same.
I could only compile test the changes. I do not have the hardware.
Cc: David Dillow <dave@thedillows.org>
Cc: Don Fry <pcnet32@frontier.com>
Cc: Francois Romieu <romieu@fr.zoreil.com>
Govindarajulu Varadarajan (3):
typhoon: use ethtool for changing rx_copybreak
pcnet32: use ethtool for changing rx_copybreak
sis190: use ethtool for changing rx_copybreak
drivers/net/ethernet/3com/typhoon.c | 49 ++++++++++++++++++++++++++++++++-----
drivers/net/ethernet/amd/pcnet32.c | 49 +++++++++++++++++++++++++++++++++----
drivers/net/ethernet/sis/sis190.c | 47 ++++++++++++++++++++++++++++++++---
3 files changed, 130 insertions(+), 15 deletions(-)
--
2.1.0
next reply other threads:[~2014-09-16 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 20:51 Govindarajulu Varadarajan [this message]
2014-09-16 20:51 ` [PATCH net-next 1/3] typhoon: use ethtool for changing rx_copybreak Govindarajulu Varadarajan
2014-09-16 20:51 ` [PATCH net-next 2/3] pcnet32: " Govindarajulu Varadarajan
2014-09-16 20:51 ` [PATCH net-next 3/3] sis190: " Govindarajulu Varadarajan
2014-09-16 20:57 ` [PATCH net-next 0/3] Remove rx_copybreak module param, use ethtool to change its value 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=1410900687-9686-1-git-send-email-_govind@gmx.com \
--to=_govind@gmx.com \
--cc=dave@thedillows.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pcnet32@frontier.com \
--cc=romieu@fr.zoreil.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).