DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Igor Ryzhov <iryzhov@nfware.com>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
	John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>
Subject: Re: [dpdk-dev] [RFC] kni: remove ethtool support
Date: Tue, 18 Dec 2018 09:20:59 +0000	[thread overview]
Message-ID: <f157ae8b-19f7-8c77-d666-dc1f6ac1d841@intel.com> (raw)
In-Reply-To: <CAF+s_FytboQpL+B7og640i-4F3bv3HjhtQvzDD+2FEz0FWcNaA@mail.gmail.com>

On 12/18/2018 8:20 AM, Igor Ryzhov wrote:
> Hi Ferruh,
> 
> Please, look at my patch http://patches.dpdk.org/patch/48454/ and consider
> rebasing your patch over mine.

Sorry about that, yes I will check it today.

> 
> As we discussed with Stephen, KNI needs to supply ethtool_ops with
> .get_link function, to properly support link status.
> So we should save ethtool_ops and implement .get_link using standard
> ethtool_op_get_link.
> 
> Best regards,
> Igor

  reply	other threads:[~2018-12-18  9:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18  1:25 Ferruh Yigit
2018-12-18  8:20 ` Igor Ryzhov
2018-12-18  9:20   ` Ferruh Yigit [this message]
2018-12-18 18:17     ` Ferruh Yigit
2019-01-05 16:55       ` Igor Ryzhov
2019-02-06 13:12         ` Igor Ryzhov
2019-02-18 12:33           ` Ferruh Yigit
2019-02-18 13:07             ` Igor Ryzhov
2019-02-18 13:18               ` Ferruh Yigit
2019-05-24 16:29 ` [dpdk-dev] [PATCH] " Ferruh Yigit
2019-05-24 16:46   ` Stephen Hemminger
2019-05-24 16:46   ` Ferruh Yigit
2019-05-24 16:55   ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2019-05-24 19:27     ` Neil Horman
2019-05-29 21:44       ` Thomas Monjalon

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=f157ae8b-19f7-8c77-d666-dc1f6ac1d841@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=iryzhov@nfware.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=thomas@monjalon.net \
    /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).