From: Shani Peretz <shperetz@nvidia.com>
To: <dev@dpdk.org>
Cc: <stephen@networkplumber.org>, Shani Peretz <shperetz@nvidia.com>
Subject: [PATCH v5 0/4] fix comparison between devices
Date: Thu, 6 Feb 2025 02:08:34 +0200 [thread overview]
Message-ID: <20250206000838.23428-1-shperetz@nvidia.com> (raw)
In-Reply-To: <20250129085416.226718-1-shperetz@nvidia.com>
This series fixes two issues:
1. saving PCI name as the parsed one instead of user-provided string when registering a new device
2. fixes rte_cmp_dev_name function that currently compares the names by compering 2 strings
Also added test to check the functionality of rte_cmp_dev_name.
Shani Peretz (4):
bus/pci: fix registration of PCI device
lib: fix comparison between devices
app/test: add tests to find devices
lib: change find device and cmp dev name functions
app/test/test_devargs.c | 140 ++++++++++++++++++++++-
app/test/test_vdev.c | 29 +++--
drivers/bus/auxiliary/auxiliary_common.c | 19 ++-
drivers/bus/auxiliary/auxiliary_params.c | 10 +-
drivers/bus/cdx/cdx.c | 25 ++--
drivers/bus/dpaa/dpaa_bus.c | 9 +-
drivers/bus/fslmc/fslmc_bus.c | 11 +-
drivers/bus/ifpga/ifpga_bus.c | 16 ++-
drivers/bus/pci/pci_common.c | 23 ++--
drivers/bus/pci/pci_params.c | 10 +-
drivers/bus/platform/platform.c | 18 ++-
drivers/bus/platform/platform_params.c | 10 +-
drivers/bus/uacce/uacce.c | 27 +++--
drivers/bus/vdev/vdev.c | 25 +++-
drivers/bus/vdev/vdev_params.c | 10 +-
drivers/bus/vdev/vdev_private.h | 2 +-
drivers/bus/vmbus/vmbus_common.c | 11 +-
drivers/dma/idxd/idxd_bus.c | 13 ++-
drivers/net/bonding/rte_eth_bond_args.c | 15 +--
drivers/net/vdev_netvsc/vdev_netvsc.c | 8 +-
drivers/raw/ifpga/ifpga_rawdev.c | 12 +-
lib/eal/common/eal_common_bus.c | 12 +-
lib/eal/common/eal_common_dev.c | 49 +++++++-
lib/eal/common/hotplug_mp.c | 19 +--
lib/eal/include/bus_driver.h | 26 ++++-
lib/eal/include/rte_dev.h | 22 +++-
lib/eal/linux/eal_dev.c | 16 +--
lib/eal/version.map | 1 +
28 files changed, 444 insertions(+), 144 deletions(-)
--
2.34.1
next prev parent reply other threads:[~2025-02-06 0:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 20:01 [PATCH] eal/common: fix inconsistent representation of PCI numbers Shani Peretz
2024-07-01 22:00 ` Stephen Hemminger
2024-07-08 16:51 ` [PATCH v3] " Shani Peretz
2024-07-12 13:49 ` David Marchand
2024-07-12 17:55 ` Thomas Monjalon
2025-01-29 8:54 ` [PATCH v4] bus: " Shani Peretz
2025-01-29 9:45 ` Bruce Richardson
2025-01-29 16:25 ` Stephen Hemminger
2025-02-05 16:36 ` Shani Peretz
2025-02-05 16:42 ` Stephen Hemminger
2025-02-05 17:37 ` Shani Peretz
2025-02-05 18:46 ` Stephen Hemminger
2025-02-05 20:16 ` Shani Peretz
2025-02-06 0:40 ` Stephen Hemminger
2025-01-29 17:17 ` Stephen Hemminger
2025-01-29 18:06 ` Bruce Richardson
2025-02-05 1:55 ` fengchengwen
2025-02-06 0:08 ` Shani Peretz [this message]
2025-02-06 0:08 ` [PATCH v5 1/4] bus/pci: fix registration of PCI device Shani Peretz
2025-02-06 0:08 ` [PATCH v5 2/4] lib: fix comparison between devices Shani Peretz
2025-02-06 0:08 ` [PATCH v5 3/4] app/test: add tests to find devices Shani Peretz
2025-02-06 1:03 ` Stephen Hemminger
2025-02-06 0:08 ` [PATCH v5 4/4] lib: change find device and cmp dev name functions Shani Peretz
2024-10-04 22:21 ` [PATCH] eal/common: fix inconsistent representation of PCI numbers Stephen Hemminger
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=20250206000838.23428-1-shperetz@nvidia.com \
--to=shperetz@nvidia.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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).