From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ivan Malov <ivan.malov@oktetlabs.ru>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH 0/4] net/sfc: support MAC address edits in transfer flows
Date: Wed, 17 Nov 2021 13:17:16 +0000 [thread overview]
Message-ID: <050792b1-ba5a-d3b2-39c1-5583b5b0f4a7@intel.com> (raw)
In-Reply-To: <20211117114438.8347-1-ivan.malov@oktetlabs.ru>
On 11/17/2021 11:44 AM, Ivan Malov wrote:
> Ivan Malov (4):
> net/sfc: refine the order of checks on MAE action set attach
> net/sfc: organise MAE flow action parsing function arguments
> common/sfc_efx/base: support MAC address edit actions in MAE
> net/sfc: support MAC address edits in transfer flows
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-11-17 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 11:44 Ivan Malov
2021-11-17 11:44 ` [PATCH 1/4] net/sfc: refine the order of checks on MAE action set attach Ivan Malov
2021-11-17 11:44 ` [PATCH 2/4] net/sfc: organise MAE flow action parsing function arguments Ivan Malov
2021-11-17 11:44 ` [PATCH 3/4] common/sfc_efx/base: support MAC address edit actions in MAE Ivan Malov
2021-11-17 11:44 ` [PATCH 4/4] net/sfc: support MAC address edits in transfer flows Ivan Malov
2021-11-17 13:17 ` 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=050792b1-ba5a-d3b2-39c1-5583b5b0f4a7@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=ivan.malov@oktetlabs.ru \
/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).