From: "John W. Linville" <linville@tuxdriver.com>
To: Scott Branden <scott.branden@broadcom.com>
Cc: BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
Steve Lin <steven.lin1@broadcom.com>,
Michael Chan <michael.chan@broadcom.com>,
netdev@vger.kernel.org, Paul Greenwalt <paul.greenwalt@intel.com>,
Stephen Hemminger <shemminger@vyatta.com>
Subject: Re: [PATCH v3 3/3] ethtool: Add ETHTOOL_RESET support via --reset command
Date: Thu, 14 Dec 2017 14:23:33 -0500 [thread overview]
Message-ID: <20171214192332.GF19705@tuxdriver.com> (raw)
In-Reply-To: <1513110003-10543-4-git-send-email-scott.branden@broadcom.com>
Applied.
On Tue, Dec 12, 2017 at 12:20:03PM -0800, Scott Branden wrote:
> Add ETHTOOL_RESET support via --reset command.
>
> ie. ethtool --reset DEVNAME <flagname(s)>
>
> flagnames currently match the ETH_RESET_xxx names:
> mgmt,irq,dma,filter,offload,mac,phy,ram,ap,dedicated,all
>
> Add -shared onto end of components to specified shared version.
>
> Alternatively, you can specific component bitfield directly using
> ethtool --reset DEVNAME flags %x
>
> Signed-off-by: Scott Branden <scott.branden@broadcom.com>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2017-12-14 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 20:20 [PATCH v3 0/3] ethtool: add ETHTOOL_RESET support via --reset command Scott Branden
2017-12-12 20:20 ` [PATCH v3 1/3] Revert "ethtool: Add DMA Coalescing support" Scott Branden
2017-12-14 19:03 ` John W. Linville
2017-12-12 20:20 ` [PATCH v3 2/3] ethtool-copy.h: sync with net-next Scott Branden
2017-12-14 19:23 ` John W. Linville
2017-12-12 20:20 ` [PATCH v3 3/3] ethtool: Add ETHTOOL_RESET support via --reset command Scott Branden
2017-12-14 19:23 ` John W. Linville [this message]
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=20171214192332.GF19705@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=paul.greenwalt@intel.com \
--cc=scott.branden@broadcom.com \
--cc=shemminger@vyatta.com \
--cc=steven.lin1@broadcom.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).