From: Stephen Hemminger <stephen@networkplumber.org>
To: vanshika.shukla@nxp.com
Cc: dev@dpdk.org
Subject: Re: [v1 00/10] DPAA specific fixes
Date: Wed, 28 May 2025 07:25:38 -0700 [thread overview]
Message-ID: <20250528072538.23cbbb58@hermes.local> (raw)
In-Reply-To: <20250528115513.1023689-1-vanshika.shukla@nxp.com>
On Wed, 28 May 2025 17:25:03 +0530
vanshika.shukla@nxp.com wrote:
> From: Vanshika Shukla <vanshika.shukla@nxp.com>
>
> This series includes fixes for NXP DPAA drivers.
>
> Gagandeep Singh (1):
> bus/dpaa: improve DPAA cleanup
>
> Hemant Agrawal (2):
> bus/dpaa: avoid using same structure and variable name
> bus/dpaa: optimize qman enqueue check
>
> Jun Yang (5):
> bus/dpaa: add FMan node
> bus/dpaa: enhance DPAA SoC version
> bus/dpaa: optimize bman acquire/release
> mempool/dpaa: fast acquire and release
> mempool/dpaa: adjust pool element for LS1043A errata
>
> Vanshika Shukla (1):
> net/dpaa: add devargs for enabling err packets on main queue
>
> Vinod Pullabhatla (1):
> net/dpaa: add Tx rate limiting DPAA PMD API
>
> .mailmap | 1 +
> doc/guides/nics/dpaa.rst | 3 +
> drivers/bus/dpaa/base/fman/fman.c | 278 ++++++++++++---------
> drivers/bus/dpaa/base/fman/netcfg_layer.c | 8 +-
> drivers/bus/dpaa/base/qbman/bman.c | 149 +++++++++--
> drivers/bus/dpaa/base/qbman/qman.c | 50 ++--
> drivers/bus/dpaa/base/qbman/qman_driver.c | 2 -
> drivers/bus/dpaa/bus_dpaa_driver.h | 9 +-
> drivers/bus/dpaa/dpaa_bus.c | 179 +++++++++----
> drivers/bus/dpaa/include/fman.h | 40 +--
> drivers/bus/dpaa/include/fsl_bman.h | 20 +-
> drivers/bus/dpaa/include/fsl_qman.h | 2 +-
> drivers/bus/dpaa/include/netcfg.h | 14 --
> drivers/mempool/dpaa/dpaa_mempool.c | 230 +++++++++++++----
> drivers/mempool/dpaa/dpaa_mempool.h | 13 +-
> drivers/net/dpaa/dpaa_ethdev.c | 291 +++++++++++++++-------
> drivers/net/dpaa/dpaa_flow.c | 87 ++++++-
> drivers/net/dpaa/dpaa_ptp.c | 12 +-
> drivers/net/dpaa/dpaa_rxtx.c | 4 +-
> drivers/net/dpaa/fmlib/fm_lib.c | 30 +++
> drivers/net/dpaa/fmlib/fm_port_ext.h | 2 +-
> drivers/net/dpaa/rte_pmd_dpaa.h | 21 +-
> 22 files changed, 1022 insertions(+), 423 deletions(-)
>
Don't resend same patch series, twice in 24 hours.
If the series is revised please mark it as v2.
There are multiple compile failures, please fix and resubmit.
next prev parent reply other threads:[~2025-05-28 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 11:55 vanshika.shukla
2025-05-28 11:55 ` [v1 01/10] bus/dpaa: avoid using same structure and variable name vanshika.shukla
2025-05-28 14:26 ` Stephen Hemminger
2025-05-28 14:25 ` Stephen Hemminger [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-28 10:39 [v1 00/10] DPAA specific fixes vanshika.shukla
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=20250528072538.23cbbb58@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@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).