From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ivan Malov <ivan.malov@oktetlabs.ru>, <dev@dpdk.org>
Cc: <stable@dpdk.org>, Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] net/sfc: make EF100 native Rx datapath set FDIR bit for MARK
Date: Thu, 9 Sep 2021 18:54:50 +0100 [thread overview]
Message-ID: <5a14db5b-13d9-4e5e-247a-cb819b8ab334@intel.com> (raw)
In-Reply-To: <20210830143542.19966-1-ivan.malov@oktetlabs.ru>
On 8/30/2021 3:35 PM, Ivan Malov wrote:
> According to flow action MARK definition, PMDs must set both
> PKT_RX_FDIR and PKT_RX_FDIR_ID if the packet contains a mark.
>
> Fixes: 1aacc3d388d3 ("net/sfc: support user mark and flag Rx for EF100")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ivan Malov <ivan.malov@oktetlabs.ru>
> Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-09-09 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 14:35 [dpdk-dev] " Ivan Malov
2021-09-09 17:54 ` 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=5a14db5b-13d9-4e5e-247a-cb819b8ab334@intel.com \
--to=ferruh.yigit@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ivan.malov@oktetlabs.ru \
--cc=stable@dpdk.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).