From: Jerin Jacob <jerinjacobk@gmail.com>
To: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Cc: Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
Harman Kalra <hkalra@marvell.com>,
dev@dpdk.org, jerinj@marvell.com
Subject: Re: [PATCH v2 5/5] net/cnxk: enable CPT CQ for outbound traffic
Date: Wed, 5 Nov 2025 10:41:19 +0530 [thread overview]
Message-ID: <CALBAE1Nboip1UhNtQkUTkdPareKEekzJCniK7E3WD1s4sWLr2w@mail.gmail.com> (raw)
In-Reply-To: <20251029130023.1637177-5-rkudurumalla@marvell.com>
On Wed, Oct 29, 2025 at 6:31 PM Rakesh Kudurumalla
<rkudurumalla@marvell.com> wrote:
>
> enable CPT CQ in cpt instruction to read outbound
> error packets from CQ
>
> Signed-off-by: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Please fix below issues. Good to merge next version
Wrong headline prefix:
net/cnxk: handle soft expiry support (expected prefix "drivers:")
net/cnxk: enable CPT CQ for outbound traffic (expected prefix
"drivers:")
Invalid patch(es) found - checked 5 patches
check-git-log failed
### [PATCH] net/cnxk: enable CPT CQ for outbound traffic
__rte_packed_begin and __rte_packed_end should always be used in pairs.
3/5 valid patches
next prev parent reply other threads:[~2025-11-05 5:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 5:13 [PATCH 1/5] common/cnxk: add CPT CQ configuration Rakesh Kudurumalla
2025-10-06 5:13 ` [PATCH 2/5] common/cnxk: add params to register IRQ handler Rakesh Kudurumalla
2025-10-06 5:14 ` [PATCH 3/5] common/cnxk: add routines to operate CPT CQ Rakesh Kudurumalla
2025-10-06 5:14 ` [PATCH 4/5] net/cnxk: handle soft expiry support Rakesh Kudurumalla
2025-10-07 6:56 ` Jerin Jacob
2025-10-06 5:14 ` [PATCH 5/5] net/cnxk: enable CPT CQ for outbound traffic Rakesh Kudurumalla
2025-10-29 13:00 ` [PATCH v2 1/5] common/cnxk: add CPT CQ configuration Rakesh Kudurumalla
2025-10-29 13:00 ` [PATCH v2 2/5] common/cnxk: add params to register IRQ handler Rakesh Kudurumalla
2025-10-29 13:00 ` [PATCH v2 3/5] common/cnxk: add routines to operate CPT CQ Rakesh Kudurumalla
2025-10-29 13:00 ` [PATCH v2 4/5] net/cnxk: handle soft expiry support Rakesh Kudurumalla
2025-10-29 13:00 ` [PATCH v2 5/5] net/cnxk: enable CPT CQ for outbound traffic Rakesh Kudurumalla
2025-11-05 5:11 ` Jerin Jacob [this message]
2025-11-05 6:58 ` David Marchand
2025-11-05 7:09 ` [PATCH v3 1/5] common/cnxk: add CPT CQ configuration Rakesh Kudurumalla
2025-11-05 7:09 ` [PATCH v3 2/5] common/cnxk: add params to register IRQ handler Rakesh Kudurumalla
2025-11-05 7:09 ` [PATCH v3 3/5] common/cnxk: add routines to operate CPT CQ Rakesh Kudurumalla
2025-11-05 7:09 ` [PATCH v3 4/5] drivers: net/cnxk: handle soft expiry support Rakesh Kudurumalla
2025-11-05 7:09 ` [PATCH v3 5/5] drivers: net/cnxk: enable CPT CQ for outbound traffic Rakesh Kudurumalla
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=CALBAE1Nboip1UhNtQkUTkdPareKEekzJCniK7E3WD1s4sWLr2w@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=rkudurumalla@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@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).