From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 2/2] bus/pci: rename probe/remove operation types
Date: Thu, 1 Apr 2021 00:34:23 +0200 [thread overview]
Message-ID: <20210331223423.2089467-3-thomas@monjalon.net> (raw)
In-Reply-To: <20210331223423.2089467-1-thomas@monjalon.net>
The names of the prototypes pci_probe_t and pci_remove_t
are missing a prefix rte_.
These function types are simply renamed.
No compatibility break is expected for the applications
because it is considered as an internal name in the driver interface.
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
drivers/bus/pci/rte_bus_pci.h | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/bus/pci/rte_bus_pci.h b/drivers/bus/pci/rte_bus_pci.h
index 3a092bc6d5..64886b4731 100644
--- a/drivers/bus/pci/rte_bus_pci.h
+++ b/drivers/bus/pci/rte_bus_pci.h
@@ -112,12 +112,12 @@ struct rte_pci_device {
/**
* Initialisation function for the driver called during PCI probing.
*/
-typedef int (pci_probe_t)(struct rte_pci_driver *, struct rte_pci_device *);
+typedef int (rte_pci_probe_t)(struct rte_pci_driver *, struct rte_pci_device *);
/**
* Uninitialisation function for the driver called during hotplugging.
*/
-typedef int (pci_remove_t)(struct rte_pci_device *);
+typedef int (rte_pci_remove_t)(struct rte_pci_device *);
/**
* Driver-specific DMA mapping. After a successful call the device
@@ -164,8 +164,8 @@ struct rte_pci_driver {
TAILQ_ENTRY(rte_pci_driver) next; /**< Next in list. */
struct rte_driver driver; /**< Inherit core driver. */
struct rte_pci_bus *bus; /**< PCI bus reference. */
- pci_probe_t *probe; /**< Device Probe function. */
- pci_remove_t *remove; /**< Device Remove function. */
+ rte_pci_probe_t *probe; /**< Device probe function. */
+ rte_pci_remove_t *remove; /**< Device remove function. */
pci_dma_map_t *dma_map; /**< device dma map function. */
pci_dma_unmap_t *dma_unmap; /**< device dma unmap function. */
const struct rte_pci_id *id_table; /**< ID table, NULL terminated. */
--
2.30.1
next prev parent reply other threads:[~2021-03-31 22:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 22:34 [dpdk-dev] [PATCH 0/2] pci: add rte prefix Thomas Monjalon
2021-03-31 22:34 ` [dpdk-dev] [PATCH 1/2] pci: rename catch-all ID Thomas Monjalon
2021-04-01 7:58 ` David Marchand
2021-04-01 8:15 ` Thomas Monjalon
2021-04-05 10:42 ` Parav Pandit
2021-03-31 22:34 ` Thomas Monjalon [this message]
2021-04-05 9:15 ` [dpdk-dev] [PATCH v2 0/2] pci: add rte prefix Thomas Monjalon
2021-04-05 9:15 ` [dpdk-dev] [PATCH v2 1/2] pci: rename catch-all ID Thomas Monjalon
2021-04-06 6:23 ` Xueming(Steven) Li
2021-04-06 9:33 ` Thomas Monjalon
2021-04-05 9:15 ` [dpdk-dev] [PATCH v2 2/2] bus/pci: rename probe/remove operation types Thomas Monjalon
2021-04-06 6:32 ` Xueming(Steven) Li
2021-04-06 9:38 ` Thomas Monjalon
2021-04-06 10:51 ` Xueming(Steven) Li
2021-04-06 8:55 ` [dpdk-dev] [PATCH v2 0/2] pci: add rte prefix David Marchand
2021-04-06 10:28 ` [dpdk-dev] [PATCH v3 " Thomas Monjalon
2021-04-06 10:28 ` [dpdk-dev] [PATCH v3 1/2] pci: rename catch-all ID Thomas Monjalon
2021-04-06 10:28 ` [dpdk-dev] [PATCH v3 2/2] bus/pci: rename probe/remove operation types Thomas Monjalon
2021-04-06 13:04 ` [dpdk-dev] [PATCH v3 0/2] pci: add rte prefix 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=20210331223423.2089467-3-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=dev@dpdk.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).