From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jerin Jacob <jerinjacobk@gmail.com>, smadarf@marvell.com
Cc: Jerin Jacob <jerinj@marvell.com>, Liron Himi <lironh@marvell.com>,
Guy Kaneti <guyk@marvell.com>, dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1] net/octeontx2: support flow action port id
Date: Wed, 31 Mar 2021 17:08:38 +0100 [thread overview]
Message-ID: <033fa14b-2e40-80b1-72e0-b2bcd37f1d08@intel.com> (raw)
In-Reply-To: <CALBAE1Pc5brpxJYEvwx_TX2incVP0_o8BRm1w93QQfCgYvYAig@mail.gmail.com>
On 3/27/2021 2:29 PM, Jerin Jacob wrote:
> On Fri, Mar 26, 2021 at 3:18 PM <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>
>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
> Applied to dpdk-next-net-mrvl/for-main. Thanks
>
Can you please update release notes too?
prev parent reply other threads:[~2021-03-31 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 16:03 smadarf
2021-03-27 14:29 ` Jerin Jacob
2021-03-31 16:08 ` 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=033fa14b-2e40-80b1-72e0-b2bcd37f1d08@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=guyk@marvell.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=lironh@marvell.com \
--cc=smadarf@marvell.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).