From: Sameer Vaze <svaze@qti.qualcomm.com>
To: Akhil Goyal <gakhil@marvell.com>, 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: [EXTERNAL] [PATCH] app/compress-perf: support dictionary files
Date: Fri, 19 Sep 2025 16:00:08 +0000 [thread overview]
Message-ID: <SJ2PR02MB97954EB015631E1817D6E3628911A@SJ2PR02MB9795.namprd02.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB4484973EF4D64751A206D8BED811A@CO6PR18MB4484.namprd18.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 3555 bytes --]
I don't see anything specific about creating and pushing a series : 9. Contributing Code to DPDK — Data Plane Development Kit 25.07.0 documentation<https://doc.dpdk.org/guides/contributing/patches.html>.
The only mention to a series above seems to use the depends-on tag.
Thanks
Sameer Vaze
________________________________
From: Akhil Goyal <gakhil@marvell.com>
Sent: Thursday, September 18, 2025 11:08 PM
To: Sameer Vaze <svaze@qti.qualcomm.com>; 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: [EXTERNAL] [PATCH] app/compress-perf: support dictionary files
WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
Hi Sameer,
> Hey Akhil,
>
> I attempted to split the changes into multiple patches and added a depends-on
> the second patch. But automation does not seem to be picking up the patch as a
> dependency. Is there a process step I messed up:
When you have dependent patches, you should send them as a series.
Automation runs on the last patch in the series only.
Currently it is not handling depends-on tag. It is for reviewers for now.
>
>
> Patch 1: compress/zlib: support for dictionary and PDCP checksum - Patchwork
> <https://patches.dpdk.org/project/dpdk/patch/20250918204411.1701035-1-svaze@qti.qualcomm.com/>
> Patch 2 with depends-n: app/compress-perf: support dictionary files - Patchwork
> <https://patches.dpdk.org/project/dpdk/patch/20250918210806.1709958-1-svaze@qti.qualcomm.com/>
>
> Thanks
> Sameer Vaze
> ________________________________
>
> From: Akhil Goyal <gakhil@marvell.com>
> Sent: Tuesday, June 17, 2025 3:34 PM
> To: Sameer Vaze <svaze@qti.qualcomm.com>; 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: [EXTERNAL] [PATCH] app/compress-perf: support dictionary files
>
> WARNING: This email originated from outside of Qualcomm. Please be wary of
> any links or attachments, and do not enable macros.
>
> > compress/zlib: support PDCP checksum
> >
> > compress/zlib: support zlib dictionary
> >
> > compressdev: add PDCP checksum
> >
> > compressdev: support zlib dictionary
> >
> > Adds support to provide predefined dictionaries to zlib. Handles setting
> > and getting of dictionaries using zlib apis. Also includes support to
> > read dictionary files
> >
> > Adds support for passing in and validationg 3GPP PDCP spec defined
> > checksums as defined under the Uplink Data Compression(UDC) feature.
> > Changes also include functions that do inflate or deflate specific
> > checksum operations.
> >
> > Introduces new members to compression api structures to allow setting
> > predefined dictionaries
> >
> > Signed-off-by: Sameer Vaze <svaze@qti.qualcomm.com>
>
> Seems like multiple patches are squashed into a single patch
>
> I see that this patch has ABI breaks.
> We need to defer this patch for next ABI break release.
> Please split the patch appropriately.
> First patch should define the library changes.
> And subsequently logically broken PMD patches
> Followed by application patches.
> Ensure each patch is compilable.
>
> Since this patch is breaking ABI/API,
> Please send a deprecation notice to be merged in this release and
> Implementation for next release.
>
> Also avoid unnecessary and irrelevant code changes.
>
[-- Attachment #2: Type: text/html, Size: 5914 bytes --]
prev parent reply other threads:[~2025-09-19 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 17:16 Sameer Vaze
2025-05-30 21:09 ` Sameer Vaze
2025-06-04 16:41 ` Sameer Vaze
2025-06-17 21:34 ` [EXTERNAL] " Akhil Goyal
2025-09-18 21:18 ` Sameer Vaze
2025-09-19 5:08 ` Akhil Goyal
2025-09-19 16:00 ` Sameer Vaze [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=SJ2PR02MB97954EB015631E1817D6E3628911A@SJ2PR02MB9795.namprd02.prod.outlook.com \
--to=svaze@qti.qualcomm.com \
--cc=ashishg@marvell.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=ssahu@marvell.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).