From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "shreyansh.jain@nxp.com" <shreyansh.jain@nxp.com>,
"stable@dpdk.org" <stable@dpdk.org>,
Sachin Saxena <sachin.saxena@nxp.com>
Subject: RE: [PATCH] bus/fslmc: fix use after rte_free
Date: Mon, 23 Dec 2024 10:23:24 +0000 [thread overview]
Message-ID: <PAXPR04MB93287C76D50154F42904404989022@PAXPR04MB9328.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20241218170530.140747-1-stephen@networkplumber.org>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
prev parent reply other threads:[~2024-12-23 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 17:05 Stephen Hemminger
[not found] ` <20241219225253.782792-1-stephen@networkplumber.org>
2024-12-19 22:49 ` [PATCH v2 1/5] " Stephen Hemminger
2024-12-19 22:49 ` [PATCH v2 2/5] net/bnxt: fix use after free Stephen Hemminger
2024-12-19 22:49 ` [PATCH v2 4/5] net/qede: " Stephen Hemminger
2024-12-23 10:23 ` Hemant Agrawal [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=PAXPR04MB93287C76D50154F42904404989022@PAXPR04MB9328.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=sachin.saxena@nxp.com \
--cc=shreyansh.jain@nxp.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.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).