From: "Wiles, Keith" <keith.wiles@intel.com>
To: Pascal Mazon <pascal.mazon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] net/tap: improve link_update
Date: Wed, 22 Mar 2017 14:11:55 +0000 [thread overview]
Message-ID: <B5A10B9B-3DBA-42C7-883D-167F9A8BB3EB@intel.com> (raw)
In-Reply-To: <fa9ce2ddc2cac000570b6ed58fa607e235992a3f.1490171928.git.pascal.mazon@6wind.com>
> On Mar 22, 2017, at 3:40 AM, Pascal Mazon <pascal.mazon@6wind.com> wrote:
>
> Reflect device link status according to the state of the tap netdevice
> and the remote netdevice (if any). If both are UP and RUNNING, then the
> device link status is set to ETH_LINK_UP, otherwise ETH_LINK_DOWN.
>
> Signed-off-by: Pascal Mazon <pascal.mazon@6wind.com>
Acked-by: Keith Wiles <keith.wiles@intel.com>
Regards,
Keith
next prev parent reply other threads:[~2017-03-22 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 8:40 Pascal Mazon
2017-03-22 8:40 ` [dpdk-dev] [PATCH 2/2] net/tap: add link status notification Pascal Mazon
2017-03-22 14:10 ` Wiles, Keith
2017-03-22 14:11 ` Wiles, Keith [this message]
2017-03-24 16:02 ` [dpdk-dev] [PATCH 1/2] net/tap: improve link_update Ferruh Yigit
2017-03-27 9:45 ` Pascal Mazon
2017-03-27 11:21 ` Ferruh Yigit
2017-03-27 11:34 ` Pascal Mazon
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=B5A10B9B-3DBA-42C7-883D-167F9A8BB3EB@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
--cc=pascal.mazon@6wind.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).