From: Thomas Monjalon <thomas@monjalon.net>
To: Huisong Li <lihuisong@huawei.com>
Cc: dev@dpdk.org, stephen@networkplumber.org, liuyonglong@huawei.com
Subject: Re: [PATCH v2 1/2] ethdev: clarify something about the new event
Date: Thu, 16 Jan 2025 16:17:30 +0100 [thread overview]
Message-ID: <2023760.8hb0ThOEGa@thomas> (raw)
In-Reply-To: <20250116114034.9858-2-lihuisong@huawei.com>
16/01/2025 12:40, Huisong Li:
> If application verify the validity of the port id or configure this port in
> the new event callback, application may happen to the port id is invalid.
>
> In case of similar confusion, this patch have to clarify something about
> RTE_ETH_EVENT_NEW in code.
>
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
> ---
> - RTE_ETH_EVENT_NEW, /**< port is probed */
> + /** The port is being probed, i.e. allocated and not yet available.
> + * It is too early to check validity, query infos, and configure
> + * the port.
> + */
> + RTE_ETH_EVENT_NEW,
Acked-by: Thomas Monjalon <thomas@monjalon.net>
next prev parent reply other threads:[~2025-01-16 15:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 3:41 [PATCH v1 0/2] ethdev: clarify something about new event 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-16 6:16 ` lihuisong (C)
2025-01-16 9:15 ` Thomas Monjalon
2025-01-16 9:35 ` lihuisong (C)
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
2025-01-16 6:14 ` lihuisong (C)
2025-01-16 9:09 ` Thomas Monjalon
2025-01-16 9:35 ` lihuisong (C)
2025-01-16 11:40 ` [PATCH v2 0/2] ethdev: clarify something about " Huisong Li
2025-01-16 11:40 ` [PATCH v2 1/2] ethdev: clarify something about the " Huisong Li
2025-01-16 15:17 ` Thomas Monjalon [this message]
2025-01-16 18:31 ` Stephen Hemminger
2025-01-17 8:43 ` lihuisong (C)
2025-01-16 11:40 ` [PATCH v2 2/2] ethdev: fix some functions are available in " Huisong Li
2025-01-16 15:18 ` Thomas Monjalon
2025-01-17 8:43 ` lihuisong (C)
2025-01-17 9:12 ` [PATCH v3 0/2] ethdev: clarify something about " Huisong Li
2025-01-17 9:12 ` [PATCH v3 1/2] ethdev: clarify something about the " Huisong Li
2025-01-17 9:12 ` [PATCH v3 2/2] ethdev: fix some functions are available in " Huisong Li
2025-01-24 7:25 ` [PATCH v3 0/2] ethdev: clarify something about " fengchengwen
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=2023760.8hb0ThOEGa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.