DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: smadarf@marvell.com, jerinj@marvell.com
Cc: lironh@marvell.com, guyk@marvell.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] net/octeontx2: support flow action port id
Date: Thu, 8 Apr 2021 16:18:40 +0100	[thread overview]
Message-ID: <ddcfe8fb-6b63-d303-1951-8ce64b188544@intel.com> (raw)
In-Reply-To: <20210408102113.5545-1-smadarf@marvell.com>

On 4/8/2021 11:21 AM, smadarf@marvell.com wrote:
> From: Smadar Fuks <smadarf@marvell.com>
> Action port_id was not supported until now.
> In this patch the action port_id supports passing from input
> port PF to output port which is one of input port respective VF
> Signed-off-by: Smadar Fuks <smadarf@marvell.com>

Carrying ack from previous version:
Acked-by: Jerin Jacob <jerinj@marvell.com>

Applied to dpdk-next-net/main, thanks.

      reply	other threads:[~2021-04-08 15:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-08 10:21 smadarf
2021-04-08 15:18 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ddcfe8fb-6b63-d303-1951-8ce64b188544@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=guyk@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=lironh@marvell.com \
    --cc=smadarf@marvell.com \


* 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).