From: Shahaf Shuler <shahafs@mellanox.com>
To: "Xueming(Steven) Li" <xuemingl@mellanox.com>,
"Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
Cc: "Xueming(Steven) Li" <xuemingl@mellanox.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix invalid flow item check
Date: Sun, 22 Apr 2018 09:19:08 +0000 [thread overview]
Message-ID: <DB7PR05MB4426B347B55C353F33A6578DC38A0@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20180413150036.112498-1-xuemingl@mellanox.com>
Friday, April 13, 2018 6:01 PM, Xueming Li:
> Subject: [dpdk-dev] [PATCH] net/mlx5: fix invalid flow item check
>
> This patch fixed invalid flow item check.
>
> Fixes: 4f1a88e3f9b0 ("net/mlx5: standardize on negative errno values")
> Cc: nelio.laranjeiro@6wind.com
>
> Signed-off-by: Xueming Li <xuemingl@mellanox.com>
> Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Applied to next-net-mlx, thanks.
prev parent reply other threads:[~2018-04-22 9:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 15:00 Xueming Li
2018-04-22 9:19 ` Shahaf Shuler [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=DB7PR05MB4426B347B55C353F33A6578DC38A0@DB7PR05MB4426.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=xuemingl@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).