From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Tomasz Duszynski <tduszynski@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Sachin Saxena <sachin.saxena@nxp.com>,
Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: "jerinj@marvell.com" <jerinj@marvell.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] rawdev: fix device naming
Date: Mon, 24 Jul 2023 13:43:31 +0000 [thread overview]
Message-ID: <PAXPR04MB93287B5305CF0E115748BFE88902A@PAXPR04MB9328.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20230724133646.1385487-1-tduszynski@marvell.com>
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
next prev parent reply other threads:[~2023-07-24 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 13:36 Tomasz Duszynski
2023-07-24 13:43 ` Hemant Agrawal [this message]
2023-10-02 8:34 ` David Marchand
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=PAXPR04MB93287B5305CF0E115748BFE88902A@PAXPR04MB9328.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=sachin.saxena@nxp.com \
--cc=shreyansh.jain@nxp.com \
--cc=stable@dpdk.org \
--cc=tduszynski@marvell.com \
--cc=thomas@monjalon.net \
/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).