From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] net/sfc: support transfer rule proxy
Date: Mon, 18 Oct 2021 20:16:33 +0100 [thread overview]
Message-ID: <e8de8d0d-90b3-54e0-1855-6050d68c49d5@intel.com> (raw)
In-Reply-To: <20211015064903.3302489-1-andrew.rybchenko@oktetlabs.ru>
On 10/15/2021 7:49 AM, Andrew Rybchenko wrote:
> Prepare driver infrastructure and add support for transfer rules
> proxy. The API allows to find out right entry point for transfer
> rules (which require corresponding priviledges).
>
> Viacheslav Galaktionov (3):
> common/sfc_efx/base: support unprivileged MAE clients
> net/sfc: allow ports without MAE privilege
> net/sfc: implement the transfer proxy port callback
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-10-18 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 6:49 Andrew Rybchenko
2021-10-15 6:49 ` [dpdk-dev] [PATCH 1/3] common/sfc_efx/base: support unprivileged MAE clients Andrew Rybchenko
2021-10-15 6:49 ` [dpdk-dev] [PATCH 2/3] net/sfc: allow ports without MAE privilege Andrew Rybchenko
2021-10-15 6:49 ` [dpdk-dev] [PATCH 3/3] net/sfc: implement the transfer proxy port callback Andrew Rybchenko
2021-10-18 19:16 ` 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=e8de8d0d-90b3-54e0-1855-6050d68c49d5@intel.com \
--to=ferruh.yigit@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@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).