From: Andrew Lunn <andrew@lunn.ch>
To: Jose Abreu <Jose.Abreu@synopsys.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
David Miller <davem@redhat.com>,
Jakub Jelinek <jj@ultra.linux.cz>,
Jeff Garzik <jgarzik@pobox.com>, Tim Hockin <thockin@sun.com>,
Eli Kupermann <eli.kupermann@intel.com>,
Chris Leech <christopher.leech@intel.com>,
Scott Feldman <scott.feldman@intel.com>,
Ben Hutchings <ben@decadent.org.uk>,
netdev@vger.kernel.org, Joao Pinto <Joao.Pinto@synopsys.com>
Subject: Re: [RFC] ethtool: Support for driver private ioctl's
Date: Fri, 6 Apr 2018 16:47:01 +0200 [thread overview]
Message-ID: <20180406144701.GO17495@lunn.ch> (raw)
In-Reply-To: <27c05ec7-1f85-8e4a-be06-70d6d80e8a10@synopsys.com>
On Fri, Apr 06, 2018 at 02:51:15PM +0100, Jose Abreu wrote:
> Hi Florian,
>
> On 05-04-2018 16:50, Florian Fainelli wrote:
> >
> > On 04/05/2018 03:47 AM, Jose Abreu wrote:
> >> Hi All,
> >>
> >> I would like to know your opinion regarding adding support for
> >> driver private ioctl's in ethtool.
> >>
> >> Background: Synopsys Ethernet IP's have a certain number of
> >> features which can be reconfigured at runtime. Giving you two
> >> examples: One of the most recent one is the safety features,
> >> which can be enabled/disabled and forced at runtime.
Hi Jose
Is there a reason somebody would decide to use the Ethernet in
'unsafe' mode? Cannot you just turn it on by default?
Andrew
next prev parent reply other threads:[~2018-04-06 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 10:47 [RFC] ethtool: Support for driver private ioctl's Jose Abreu
2018-04-05 15:50 ` Florian Fainelli
2018-04-06 9:07 ` Michal Kubecek
2018-04-06 13:57 ` Jose Abreu
2018-04-06 13:51 ` Jose Abreu
2018-04-06 14:47 ` Andrew Lunn [this message]
2018-04-06 14:51 ` Jose Abreu
2018-04-07 19:58 ` Florian Fainelli
2018-04-24 9:37 ` Jose Abreu
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=20180406144701.GO17495@lunn.ch \
--to=andrew@lunn.ch \
--cc=Joao.Pinto@synopsys.com \
--cc=Jose.Abreu@synopsys.com \
--cc=ben@decadent.org.uk \
--cc=christopher.leech@intel.com \
--cc=davem@redhat.com \
--cc=eli.kupermann@intel.com \
--cc=f.fainelli@gmail.com \
--cc=jgarzik@pobox.com \
--cc=jj@ultra.linux.cz \
--cc=netdev@vger.kernel.org \
--cc=scott.feldman@intel.com \
--cc=thockin@sun.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.