From: fengchengwen <fengchengwen@huawei.com>
To: Huisong Li <lihuisong@huawei.com>, <dev@dpdk.org>
Cc: <thomas@monjalon.net>, <stephen@networkplumber.org>,
<liuyonglong@huawei.com>
Subject: Re: [PATCH v3 0/2] ethdev: clarify something about new event
Date: Fri, 24 Jan 2025 15:25:05 +0800 [thread overview]
Message-ID: <9ae7146f-ec95-4d09-bbdf-5d11a699c0f9@huawei.com> (raw)
In-Reply-To: <20250117091210.12419-1-lihuisong@huawei.com>
Series-acked-by: Chengwen Feng <fengchengwen@huawei.com>
On 2025/1/17 17:12, Huisong Li wrote:
> I've had some issues when I add the verification of the port id in the
> event callback, which are discussed in another patch series[1]. So this
> series clarify something about RTE_ETH_EVENT_NEW based on the previous
> discussion.
>
> [1] https://patches.dpdk.org/project/dpdk/cover/20250113025521.32703-1-lihuisong@huawei.com/
>
> ---
> -v3:
> - add "the" before application as Thomas suggested.
> - add Acked-by Thomas Monjalon <thomas@monjalon.net>
> -v2: fix some descriptions as Thomas suggested.
>
> Huisong Li (2):
> ethdev: clarify something about the new event
> ethdev: fix some functions are available in the new event
>
> lib/ethdev/rte_ethdev.c | 14 +++++++++++---
> lib/ethdev/rte_ethdev.h | 7 ++++++-
> 2 files changed, 17 insertions(+), 4 deletions(-)
>
prev parent reply other threads:[~2025-01-24 7:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 3:41 [PATCH v1 " 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
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 ` fengchengwen [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=9ae7146f-ec95-4d09-bbdf-5d11a699c0f9@huawei.com \
--to=fengchengwen@huawei.com \
--cc=dev@dpdk.org \
--cc=lihuisong@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=stephen@networkplumber.org \
--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).