From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Shahaf Shuler" <shahafs@mellanox.com>,
"Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Yongseok Koh <yskoh@mellanox.com>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: remove parser/flow drop queue
Date: Mon, 27 Nov 2017 10:11:20 -0800 [thread overview]
Message-ID: <7ad25928-34b1-9378-f60a-d5f1a35ab6f5@intel.com> (raw)
In-Reply-To: <VI1PR05MB31498471D2FA279D806C888DC3250@VI1PR05MB3149.eurprd05.prod.outlook.com>
On 11/26/2017 11:19 PM, Shahaf Shuler wrote:
> Thursday, November 23, 2017 11:30 AM, Nelio Laranjeiro:
>> This drop queue can be handled efficiently by using the drop flag in the
>> context.
>>
>> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
>> Acked-by: Yongseok Koh <yskoh@mellanox.com>
>
> Applied to next-net-mlx, thanks.
Hi Shahaf,
What do you think updating status of patches applied to vendor sub-trees as
"Awaiting Upstream" in patchwork? To indicate they are in the sub-tree.
Thanks,
ferruh
next prev parent reply other threads:[~2017-11-27 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 7:49 [dpdk-dev] [PATCH] " Nelio Laranjeiro
2017-11-23 9:30 ` [dpdk-dev] [PATCH v2] " Nelio Laranjeiro
2017-11-27 7:19 ` Shahaf Shuler
2017-11-27 18:11 ` Ferruh Yigit [this message]
2017-11-28 10:59 ` Shahaf Shuler
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=7ad25928-34b1-9378-f60a-d5f1a35ab6f5@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=shahafs@mellanox.com \
--cc=yskoh@mellanox.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).