From: Thomas Monjalon <thomas@monjalon.net>
To: Nawal Kishor <nkishor@marvell.com>
Cc: dev@dpdk.org, Sachin Saxena <sachin.saxena@nxp.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Shreyansh Jain <shreyansh.jain@nxp.com>,
jerinj@marvell.com, asekhar@marvell.com
Subject: Re: [PATCH] rawdev: fix device ID retrieval function prototype
Date: Wed, 15 Oct 2025 17:05:25 +0200 [thread overview]
Message-ID: <2509677.g5d078U9FE@thomas> (raw)
In-Reply-To: <20250924055654.1986682-1-nkishor@marvell.com>
24/09/2025 07:56, Nawal Kishor:
> Fixed rte_rawdev_get_dev_id() function prototype and its usage.
What? Why?
[...]
> -uint16_t
> +int
> rte_rawdev_get_dev_id(const char *name);
Other functions handle dev_id as uint16_t, so why changing this function?
next prev parent reply other threads:[~2025-10-15 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 5:56 Nawal Kishor
2025-10-15 15:05 ` Thomas Monjalon [this message]
2025-10-16 6:56 ` Nawal Kishor
2025-10-16 8:08 ` 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=2509677.g5d078U9FE@thomas \
--to=thomas@monjalon.net \
--cc=asekhar@marvell.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=nkishor@marvell.com \
--cc=sachin.saxena@nxp.com \
--cc=shreyansh.jain@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).