From: Stephen Hemminger <stephen@networkplumber.org>
To: David Hendel <david@silicom.co.il>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Elad Blatt <eladb@silicom.co.il>
Subject: Re: ethtool patch to support bypass / fail-to-wire function
Date: Wed, 11 Jun 2014 11:35:58 -0700 [thread overview]
Message-ID: <20140611113558.6d0c6296@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <3BFAEADE799AF145974162DF00E013AF018F79A137@exchange2010.silicom.local>
On Wed, 11 Jun 2014 16:55:27 +0000
David Hendel <david@silicom.co.il> wrote:
> Stephen,
> OK, so what should be the next step? How do we move forward with that?
>
> Regards, David
>
>
> -----Original Message-----
> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> Sent: Wednesday, June 11, 2014 7:18 PM
> To: David Hendel
> Cc: netdev@vger.kernel.org; Elad Blatt
> Subject: Re: ethtool patch to support bypass / fail-to-wire function
>
> The driver using this is not upstream. You need to get that driver reviewed and incorporated in upstream kernel before the changes to ethtool will be considered.
>
> I expect that the driver will not be accepted as is, and therefore you will have to make changes (including API changes), that render this ethtool API moot.
>
>
Read kernel/Documentation/SubmittingPatches
next prev parent reply other threads:[~2014-06-11 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3BFAEADE799AF145974162DF00E013AF018F794DE5@exchange2010.silicom.local>
[not found] ` <1402322812.23860.76.camel@deadeye.wl.decadent.org.uk>
2014-06-09 20:27 ` ethtool patch to support bypass / fail-to-wire function David Hendel
2014-06-11 7:06 ` David Hendel
2014-06-11 16:17 ` Stephen Hemminger
2014-06-11 16:55 ` David Hendel
2014-06-11 18:35 ` Stephen Hemminger [this message]
2014-07-30 12:55 ` FW: " David Hendel
2014-07-30 22:03 ` Francois Romieu
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=20140611113558.6d0c6296@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=david@silicom.co.il \
--cc=eladb@silicom.co.il \
--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).