From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org, Huisong Li <lihuisong@huawei.com>
Cc: stephen@networkplumber.org, liuyonglong@huawei.com, lihuisong@huawei.com
Subject: Re: [PATCH v1 2/2] ethdev: fix some APIs can be used in the new event
Date: Wed, 15 Jan 2025 12:36:13 +0100 [thread overview]
Message-ID: <1837683.3VsfAaAtOV@thomas> (raw)
In-Reply-To: <20250115034110.15245-3-lihuisong@huawei.com>
15/01/2025 04:41, Huisong Li:
> The rte_eth_dev_socket_id() and rte_eth_dev_owner_*() can be used after
> allocating an ethdev. So this patch relaxes the conditions for using them.
You should be more explicit:
"during probing, before it becomes generally available and considered as valid".
Should we add these functions in the comment for RTE_ETH_EVENT_NEW?
prev parent reply other threads:[~2025-01-15 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 3:41 [PATCH v1 0/2] ethdev: clarify something about " Huisong Li
2025-01-15 3:41 ` [PATCH v1 1/2] ethdev: clarify do not something in the " Huisong Li
2025-01-15 11:31 ` Thomas Monjalon
2025-01-15 3:41 ` [PATCH v1 2/2] ethdev: fix some APIs can be used " Huisong Li
2025-01-15 11:36 ` Thomas Monjalon [this message]
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=1837683.3VsfAaAtOV@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=lihuisong@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=stephen@networkplumber.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).