From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Rongwei Liu <rongweil@nvidia.com>,
dev@dpdk.org, matan@nvidia.com, viacheslavo@nvidia.com,
orika@nvidia.com, suanmingm@nvidia.com, thomas@monjalon.net
Cc: michaelba@nvidia.com, stable@dpdk.org,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Aman Singh <aman.deep.singh@intel.com>,
Yuying Zhang <yuying.zhang@intel.com>
Subject: Re: [PATCH v1 1/2] app/testpmd: fix modify tag typo
Date: Wed, 21 Feb 2024 16:42:07 +0000 [thread overview]
Message-ID: <787e4cc7-8687-482e-b59e-4826e6ae87d3@amd.com> (raw)
In-Reply-To: <8cec38d8-b7e6-4288-ae32-1ac3732d159e@amd.com>
On 2/21/2024 4:33 PM, Ferruh Yigit wrote:
> On 2/21/2024 7:10 AM, Rongwei Liu wrote:
>> Update the name to the right one: "src_tag_index"
>>
>> Fixes: 7ea38955b ("ethdev: update MPLS header modification API")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Rongwei Liu <rongweil@nvidia.com>
>> Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
>
btw, fixes commit is wrong, it should be [1], I guess this is related to
the tree you are using as other patch has similar issue.
[1]
Fixes: c23626f27b09 ("ethdev: add MPLS header modification")
next prev parent reply other threads:[~2024-02-21 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240221071043.3309205-1-rongweil@nvidia.com>
2024-02-21 7:10 ` Rongwei Liu
2024-02-21 16:33 ` Ferruh Yigit
2024-02-21 16:42 ` Ferruh Yigit [this message]
2024-02-22 3:06 ` rongwei liu
2024-02-21 7:10 ` [PATCH v1 2/2] net/mlx5: fix modify flex item error Rongwei Liu
2024-02-21 16:35 ` Ferruh Yigit
[not found] ` <20240223032155.182162-1-rongweil@nvidia.com>
2024-02-23 3:21 ` [PATCH v2 1/2] app/testpmd: fix modify tag typo Rongwei Liu
2024-02-23 12:06 ` Ferruh Yigit
2024-02-23 3:21 ` [PATCH v2 2/2] net/mlx5: fix modify flex item error Rongwei Liu
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=787e4cc7-8687-482e-b59e-4826e6ae87d3@amd.com \
--to=ferruh.yigit@amd.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=michaelba@nvidia.com \
--cc=orika@nvidia.com \
--cc=rongweil@nvidia.com \
--cc=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.com \
--cc=yuying.zhang@intel.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).