* [PATCH] rawdev: fix device naming
@ 2023-07-24 13:36 Tomasz Duszynski
2023-07-24 13:43 ` Hemant Agrawal
2023-10-02 8:34 ` David Marchand
0 siblings, 2 replies; 3+ messages in thread
From: Tomasz Duszynski @ 2023-07-24 13:36 UTC (permalink / raw)
To: dev, Sachin Saxena, Hemant Agrawal, Shreyansh Jain
Cc: jerinj, thomas, Tomasz Duszynski, stable
Use proper naming when dealing with a raw device.
Fixes: c88b3f2558ed ("rawdev: introduce raw device library")
Cc: shreyansh.jain@nxp.com
Cc: stable@dpdk.org
Signed-off-by: Tomasz Duszynski <tduszynski@marvell.com>
---
lib/rawdev/rte_rawdev.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/lib/rawdev/rte_rawdev.c b/lib/rawdev/rte_rawdev.c
index dacaa60e22..474bdc9540 100644
--- a/lib/rawdev/rte_rawdev.c
+++ b/lib/rawdev/rte_rawdev.c
@@ -505,8 +505,7 @@ rte_rawdev_pmd_allocate(const char *name, size_t dev_priv_size, int socket_id)
uint16_t dev_id;
if (rte_rawdev_pmd_get_named_dev(name) != NULL) {
- RTE_RDEV_ERR("Event device with name %s already allocated!",
- name);
+ RTE_RDEV_ERR("Raw device with name %s already allocated!", name);
return NULL;
}
--
2.34.1
^ permalink raw reply [flat|nested] 3+ messages in thread* RE: [PATCH] rawdev: fix device naming
2023-07-24 13:36 [PATCH] rawdev: fix device naming Tomasz Duszynski
@ 2023-07-24 13:43 ` Hemant Agrawal
2023-10-02 8:34 ` David Marchand
1 sibling, 0 replies; 3+ messages in thread
From: Hemant Agrawal @ 2023-07-24 13:43 UTC (permalink / raw)
To: Tomasz Duszynski, dev, Sachin Saxena, Shreyansh Jain
Cc: jerinj, thomas, stable
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> -----Original Message-----
> From: Tomasz Duszynski <tduszynski@marvell.com>
> Sent: Monday, July 24, 2023 7:07 PM
> To: dev@dpdk.org; Sachin Saxena <sachin.saxena@nxp.com>; Hemant
> Agrawal <hemant.agrawal@nxp.com>; Shreyansh Jain
> <shreyansh.jain@nxp.com>
> Cc: jerinj@marvell.com; thomas@monjalon.net; Tomasz Duszynski
> <tduszynski@marvell.com>; stable@dpdk.org
> Subject: [PATCH] rawdev: fix device naming
> Importance: High
>
> Use proper naming when dealing with a raw device.
>
> Fixes: c88b3f2558ed ("rawdev: introduce raw device library")
> Cc: shreyansh.jain@nxp.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Tomasz Duszynski <tduszynski@marvell.com>
> ---
> lib/rawdev/rte_rawdev.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/lib/rawdev/rte_rawdev.c b/lib/rawdev/rte_rawdev.c index
> dacaa60e22..474bdc9540 100644
> --- a/lib/rawdev/rte_rawdev.c
> +++ b/lib/rawdev/rte_rawdev.c
> @@ -505,8 +505,7 @@ rte_rawdev_pmd_allocate(const char *name, size_t
> dev_priv_size, int socket_id)
> uint16_t dev_id;
>
> if (rte_rawdev_pmd_get_named_dev(name) != NULL) {
> - RTE_RDEV_ERR("Event device with name %s already
> allocated!",
> - name);
> + RTE_RDEV_ERR("Raw device with name %s already
> allocated!", name);
> return NULL;
> }
>
> --
> 2.34.1
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [PATCH] rawdev: fix device naming
2023-07-24 13:36 [PATCH] rawdev: fix device naming Tomasz Duszynski
2023-07-24 13:43 ` Hemant Agrawal
@ 2023-10-02 8:34 ` David Marchand
1 sibling, 0 replies; 3+ messages in thread
From: David Marchand @ 2023-10-02 8:34 UTC (permalink / raw)
To: Tomasz Duszynski
Cc: dev, Sachin Saxena, Hemant Agrawal, Shreyansh Jain, jerinj,
thomas, stable
On Mon, Jul 24, 2023 at 3:37 PM Tomasz Duszynski <tduszynski@marvell.com> wrote:
>
> Use proper naming when dealing with a raw device.
>
> Fixes: c88b3f2558ed ("rawdev: introduce raw device library")
> Cc: stable@dpdk.org
>
> Signed-off-by: Tomasz Duszynski <tduszynski@marvell.com>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
Applied, thanks.
--
David Marchand
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-10-02 8:35 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-07-24 13:36 [PATCH] rawdev: fix device naming Tomasz Duszynski
2023-07-24 13:43 ` Hemant Agrawal
2023-10-02 8:34 ` David Marchand
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).