From: Patrick Robb <probb@iol.unh.edu>
To: Sameer Vaze <svaze@qti.qualcomm.com>
Cc: Sunila Sahu <ssahu@marvell.com>,
Fan Zhang <fanzhang.oss@gmail.com>,
Ashish Gupta <ashishg@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH] compressdev: fix coverity issue
Date: Fri, 31 Oct 2025 15:18:04 -0400 [thread overview]
Message-ID: <CAJvnSUCRqwCG=DyOXYeibHk=Yt4BRmqtfFaJkWbcD7=jOq3XLw@mail.gmail.com> (raw)
In-Reply-To: <SJ2PR02MB97950C22EE0516E4903D5CF389F8A@SJ2PR02MB9795.namprd02.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2345 bytes --]
Hi Sameer,
Thanks for the heads up. It looks like the Github Robot has a failure but I
think it is a spurious false fail, so I just sent a recheck request for
that. I expect that failure will be overwritten with a PASS soon.
There are also 2 warnings on your patch, which I can address, but they will
not preclude your patch from being merged (as they are only a WARN, not a
FAIL).
Thanks.
On Fri, Oct 31, 2025 at 1:10 PM Sameer Vaze <svaze@qti.qualcomm.com> wrote:
>
> Hey Patrick
>
> I followed https://core.dpdk.org/testing/#requesting-a-patch-retest to
> request a rebase and recheck since the failures don't seem related to my
> changes. It doesn't look like the retests were picked up. Did I miss
> something?
>
> Thanks
> Sameer Vaze
> ------------------------------
> *From:* Sameer Vaze <svaze@qti.qualcomm.com>
> *Sent:* Tuesday, October 28, 2025 11:19 AM
> *To:* Sunila Sahu <ssahu@marvell.com>; Fan Zhang <fanzhang.oss@gmail.com>;
> Ashish Gupta <ashishg@marvell.com>
> *Cc:* dev@dpdk.org <dev@dpdk.org>
> *Subject:* Re: [PATCH] compressdev: fix coverity issue
>
>
> *WARNING:* This email originated from outside of Qualcomm. Please be wary
> of any links or attachments, and do not enable macros.
> Recheck-request: rebase=main, iol-sample-apps-testing,
> iol-compile-amd64-testing
> ------------------------------
> *From:* Sameer Vaze <svaze@qti.qualcomm.com>
> *Sent:* Friday, October 24, 2025 12:47 PM
> *To:* Sunila Sahu <ssahu@marvell.com>; Fan Zhang <fanzhang.oss@gmail.com>;
> Ashish Gupta <ashishg@marvell.com>
> *Cc:* dev@dpdk.org <dev@dpdk.org>; Sameer Vaze <svaze@qti.qualcomm.com>
> *Subject:* [PATCH] compressdev: fix coverity issue
>
> Adds missing free before end of function
>
> Signed-off-by: Sameer Vaze <svaze@qti.qualcomm.com>
> ---
> drivers/compress/zlib/zlib_pmd.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/compress/zlib/zlib_pmd.c
> b/drivers/compress/zlib/zlib_pmd.c
> index 3a2485b54e..1d7651dd7d 100644
> --- a/drivers/compress/zlib/zlib_pmd.c
> +++ b/drivers/compress/zlib/zlib_pmd.c
> @@ -126,6 +126,7 @@ process_zlib_inflate_chksum(struct rte_comp_op *op,
> free(dictionary);
> return;
> }
> + free(dictionary);
> }
>
> static void
> --
> 2.31.1
>
>
[-- Attachment #2: Type: text/html, Size: 5609 bytes --]
next prev parent reply other threads:[~2025-10-31 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 18:47 Sameer Vaze
2025-10-28 17:19 ` Sameer Vaze
2025-10-31 17:10 ` Sameer Vaze
2025-10-31 19:18 ` Patrick Robb [this message]
2025-10-31 19:13 ` Patrick Robb
2025-10-24 19:11 Sameer Vaze
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='CAJvnSUCRqwCG=DyOXYeibHk=Yt4BRmqtfFaJkWbcD7=jOq3XLw@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=ashishg@marvell.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=ssahu@marvell.com \
--cc=svaze@qti.qualcomm.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).