From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 954] rte_eth_dev_info::device missing from API reference
Date: Tue, 08 Mar 2022 07:45:46 +0000 [thread overview]
Message-ID: <bug-954-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=954
Bug ID: 954
Summary: rte_eth_dev_info::device missing from API reference
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: minor
Priority: Normal
Component: doc
Assignee: dev@dpdk.org
Reporter: bmerry@sarao.ac.za
Target Milestone: ---
http://doc.dpdk.org/api/structrte__eth__dev__info.html doesn't list the
"device" field. Looking at the source header file, I think it is missing the
`<` in the Doxygen string:
struct rte_eth_dev_info {
struct rte_device *device; /** Generic device information */
const char *driver_name; /**< Device Driver name. */
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-03-08 7:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-954-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).