From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Wiles, Keith" <keith.wiles@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/2] net/tap: simplfication and servicabilty improvements
Date: Wed, 6 May 2020 19:41:47 +0100 [thread overview]
Message-ID: <0b81ef73-2c47-a9e5-f358-e7ea9fb41d3c@intel.com> (raw)
In-Reply-To: <AD2C35CB-8509-428C-B30B-05EB5F708409@intel.com>
On 4/25/2020 2:14 PM, Wiles, Keith wrote:
>
>
>> On Apr 24, 2020, at 6:36 PM, Stephen Hemminger <stephen@networkplumber.org> wrote:
>>
>> These are a couple of small fixes to the TAP driver. The first makes it
>> more robust to random signals, and the second one adds better error
>> reporting.
>>
>> Stephen Hemminger (2):
>> net/tap: simplify netlink send/receive functions
>> net/tap: use netlink extended ack support
>>
>> drivers/net/tap/tap_netlink.c | 123 +++++++++++++++++++++++++---------
>> 1 file changed, 92 insertions(+), 31 deletions(-)
>>
>> 2.20.1
>>
>
> Acked-by: Keith Wiles <keith.wiles@intel.com>
>
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2020-05-06 18:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 23:36 Stephen Hemminger
2020-04-24 23:36 ` [dpdk-dev] [PATCH 1/2] net/tap: simplify netlink send/receive functions Stephen Hemminger
2020-04-24 23:36 ` [dpdk-dev] [PATCH 2/2] net/tap: use netlink extended ack support Stephen Hemminger
2020-04-27 11:32 ` Andrzej Ostruszka [C]
2020-05-06 18:41 ` Ferruh Yigit
2020-05-06 20:19 ` Stephen Hemminger
2020-04-25 13:14 ` [dpdk-dev] [PATCH 0/2] net/tap: simplfication and servicabilty improvements Wiles, Keith
2020-05-06 18:41 ` Ferruh Yigit [this message]
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=0b81ef73-2c47-a9e5-f358-e7ea9fb41d3c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
--cc=stephen@networkplumber.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).