From: Pascal Mazon <pascal.mazon@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: "Wiles, Keith" <keith.wiles@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] net/tap: improve link_update
Date: Mon, 27 Mar 2017 11:45:20 +0200 [thread overview]
Message-ID: <20170327114520.59acbdd4@paques.dev.6wind.com> (raw)
In-Reply-To: <fa8b99ef-b3a7-813e-e692-89f1ff45fe8b@intel.com>
On Fri, 24 Mar 2017 16:02:48 +0000
Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> On 3/22/2017 2:11 PM, Wiles, Keith wrote:
> >
> >> 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>
>
> Series applied to dpdk-next-net/master, thanks.
>
>
> Hi Pascal,
>
> Many features added to the tap PMD in this realease.
>
> Would you mind adding a release notes item, in a single patch, to
> mention from all tap updates?
>
> Thanks,
> ferruh
Hi Ferruh,
Yes there's been a banch of changes in tap. I have still a few things
I'd like to push yet. I'll send a patch with the release note at the end
of those.
Best regards,
Pascal
next prev parent reply other threads:[~2017-03-27 9:46 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 ` [dpdk-dev] [PATCH 1/2] net/tap: improve link_update Wiles, Keith
2017-03-24 16:02 ` Ferruh Yigit
2017-03-27 9:45 ` Pascal Mazon [this message]
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=20170327114520.59acbdd4@paques.dev.6wind.com \
--to=pascal.mazon@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=keith.wiles@intel.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).