From: Gagandeep Singh <g.singh@nxp.com>
To: dev@dpdk.org
Cc: david.marchand@redhat.com, hemant.agrawal@nxp.com
Subject: [PATCH v4 0/1] DPAA compilation fix ppc64le and riscv
Date: Mon, 16 Nov 2026 09:36:34 +0530 [thread overview]
Message-ID: <20261116040635.639732-1-g.singh@nxp.com> (raw)
In-Reply-To: <20261027093335.4109017-1-g.singh@nxp.com>
V4-Changes:
- Remove the Patch:
"bus/dpaa: fix maybe-uninitialized in bman_release_fast"
as it is already squashed to the next-net.
V3-changes:
- fixed num usage in bman_release()
V2-changes:
- updated the Author name.
Gagandeep Singh (1):
bus/dpaa: fix unneeded conditional in bman_release
drivers/bus/dpaa/base/qbman/bman.c | 10 ++++------
1 file changed, 4 insertions(+), 6 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2026-11-16 4:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 6:15 [PATCH] bus/dpaa: fix maybe-uninitialized in bman_release_fast Gagandeep Singh
2026-10-27 6:31 ` [PATCH v2 0/1] DPAA compilation fix ppc64le and riscv Gagandeep Singh
2026-10-27 6:31 ` [PATCH v2 1/1] bus/dpaa: fix maybe-uninitialized in bman_release_fast Gagandeep Singh
2026-10-27 7:48 ` David Marchand
2026-10-27 13:46 ` Stephen Hemminger
2026-10-27 9:33 ` [PATCH v3 0/2] DPAA compilation fix ppc64le and riscv Gagandeep Singh
2026-10-27 9:33 ` [PATCH v3 1/2] bus/dpaa: fix maybe-uninitialized in bman_release_fast Gagandeep Singh
2026-10-27 9:33 ` [PATCH v3 2/2] bus/dpaa: fix unneeded conditional in bman_release Gagandeep Singh
2026-11-12 17:00 ` [PATCH v3 0/2] DPAA compilation fix ppc64le and riscv Thomas Monjalon
2026-11-16 4:08 ` Gagandeep Singh
2026-11-16 4:06 ` Gagandeep Singh [this message]
2026-11-16 4:06 ` [PATCH v4 1/1] bus/dpaa: fix unneeded conditional in bman_release Gagandeep Singh
2026-11-16 16:00 ` Thomas Monjalon
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=20261116040635.639732-1-g.singh@nxp.com \
--to=g.singh@nxp.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@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