From: Hemant Agrawal <hemant.agrawal@oss.nxp.com>
To: Gagandeep Singh <g.singh@nxp.com>,
dev@dpdk.org, Sean Morrissey <sean.morrissey@intel.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Cc: stable@dpdk.org
Subject: Re: [PATCH 2/3] examples/l3fwd: fix return value on rules add
Date: Tue, 16 Jul 2024 12:25:37 +0530 [thread overview]
Message-ID: <b66a6f3a-974e-1ca8-50f4-9a356d0f7932@oss.nxp.com> (raw)
In-Reply-To: <20240715101458.645014-2-g.singh@nxp.com>
On 15-07-2024 15:44, Gagandeep Singh wrote:
> fix return value on adding the EM or LPM rules.
>
> Fixes: e7e6dd643092 ("examples/l3fwd: support config file for EM")
> Fixes: 52def963fc1c ("examples/l3fwd: support config file for LPM/FIB")
> Cc: sean.morrissey@intel.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
next prev parent reply other threads:[~2024-07-16 6:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240715101458.645014-1-g.singh@nxp.com>
2024-07-15 10:14 ` Gagandeep Singh
2024-07-16 6:55 ` Hemant Agrawal [this message]
2024-07-15 10:14 ` [PATCH 3/3] examples/l3fwd: fix maximum acceptable port ID in routes Gagandeep Singh
2024-07-17 10:17 ` Konstantin Ananyev
2024-07-18 6:30 ` Gagandeep Singh
2024-07-18 10:01 ` Konstantin Ananyev
2024-07-22 3:28 ` Gagandeep Singh
2024-07-22 4:27 ` Gagandeep Singh
2024-07-23 16:22 ` Konstantin Ananyev
2024-07-24 8:02 ` Konstantin Ananyev
2024-08-02 10:13 ` Gagandeep Singh
[not found] ` <20240806034120.3165295-1-g.singh@nxp.com>
2024-08-06 3:41 ` [v2 2/3] examples/l3fwd: fix return value on rules add Gagandeep Singh
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=b66a6f3a-974e-1ca8-50f4-9a356d0f7932@oss.nxp.com \
--to=hemant.agrawal@oss.nxp.com \
--cc=dev@dpdk.org \
--cc=g.singh@nxp.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=sean.morrissey@intel.com \
--cc=stable@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).