patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Gagandeep Singh <g.singh@nxp.com>
Cc: dev@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>,
	Sachin Saxena <sachin.saxena@nxp.com>,
	Vanshika Shukla <vanshika.shukla@nxp.com>,
	stable@dpdk.org
Subject: Re: [PATCH v5 6/6] net/dpaa: fix resource leak coverity issue
Date: Fri, 17 Oct 2025 18:53:38 -0700	[thread overview]
Message-ID: <20251017185338.4e1e6d51@phoenix.lan> (raw)
In-Reply-To: <20251017044848.3269627-7-g.singh@nxp.com>

On Fri, 17 Oct 2025 10:18:48 +0530
Gagandeep Singh <g.singh@nxp.com> wrote:

> From: Vanshika Shukla <vanshika.shukla@nxp.com>
> 
> Fix CID:362787 issue. This patch correct the cleanup
> order of PCD and FMan handles to prevent resource leaks.
> 
> Fixes: 4defbc8cbb6d ("net/dpaa: support FMCless mode")
> Cc: sachin.saxena@nxp.com
> Cc: stable@dpdk.org
> 
> Signed-off-by: Vanshika Shukla <vanshika.shukla@nxp.com>

Patches that fix Coverity issues should use standard tag.

Coverity ID: 362787

      reply	other threads:[~2025-10-17 18:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251008043519.2461707-1-g.singh@nxp.com>
     [not found] ` <20251014101716.2885563-1-g.singh@nxp.com>
2025-10-14 10:17   ` [PATCH v3 5/5] " Gagandeep Singh
     [not found]   ` <20251017044256.3264737-1-g.singh@nxp.com>
2025-10-17  4:42     ` [PATCH v4 6/6] " Gagandeep Singh
     [not found]     ` <20251017044848.3269627-1-g.singh@nxp.com>
2025-10-17  4:48       ` [PATCH v5 " Gagandeep Singh
2025-10-18  1:53         ` Stephen Hemminger [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=20251017185338.4e1e6d51@phoenix.lan \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=g.singh@nxp.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=sachin.saxena@nxp.com \
    --cc=stable@dpdk.org \
    --cc=vanshika.shukla@nxp.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).