From: Stephen Hemminger <stephen@networkplumber.org>
To: <zhang.yong25@zte.com.cn>
Cc: <thomas@monjalon.net>, <techboard@dpdk.org>, <dev@dpdk.org>,
<wang.yong19@zte.com.cn>, <li.min10@zte.com.cn>,
<ran.ming@zte.com.cn>
Subject: Re: [PATCH] raw/zxdh: introduce zxdh raw device driver
Date: Tue, 8 Oct 2024 09:12:32 -0700 [thread overview]
Message-ID: <20241008091232.7b4b13e6@hermes.local> (raw)
In-Reply-To: <20241008144011827qVSyg8Utmz0oFDCt8yghi@zte.com.cn>
On Tue, 8 Oct 2024 14:40:11 +0800 (CST)
<zhang.yong25@zte.com.cn> wrote:
> >> Hi thomas,>> >> I hope this message finds you well.>> I initially submitted the zxdh rawdev driver on June 12th, and the final version was submitted on August 12th. Since then, I have not received any feedback from the community.>> I would appreciate it if you could provide any suggestions for modifications. If there is no problem with the submitted driver, please merge it as soon as possible.>> Thank you for your time and assistance.>> >> Thanks>Just looked at the patch today, and marked it as "Changes requested" based on>the feedback from Ferruh, and an attempt at merging it into local tree.>>Check in patchwork:>https://patchwork.dpdk.org/project/dpdk/patch/20240910120020.4031035-1-wang.junlong1@zte.com.cn/
>
> Hi Stephen,
>
> I wanted to check if you might have sent your previous email to me by mistake. It seems like it might have been intended for someone else.
> Additionally, I wanted to clarify that there are two types of ZXDH drivers:
>
>
>
> net/zxdh: Managed by Junlong Wang
>
> raw/zxdh: Managed by me
Sorry, I got confused.
The raw driver looks to be ready, I set the patch state back.
next prev parent reply other threads:[~2024-10-08 16:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 7:31 [v2 1/5] raw/zxdh: introduce zxdh raw device driver Yong Zhang
2024-08-12 7:31 ` [v2 2/5] raw/zxdh: add support for queue setup operation Yong Zhang
2024-08-12 7:31 ` [v2 3/5] raw/zxdh: add support for standard rawdev operations Yong Zhang
2024-08-12 7:31 ` [v2 4/5] raw/zxdh: add support for enqueue operation Yong Zhang
2024-08-12 7:31 ` [v2 5/5] raw/zxdh: add support for dequeue operation Yong Zhang
2024-09-02 8:55 ` Re:[PATCH] raw/zxdh: introduce zxdh raw device driver Yong Zhang
2024-09-06 6:20 ` Yong Zhang
2024-09-09 8:31 ` [PATCH] " David Marchand
2024-09-09 9:26 ` Yong Zhang
2024-09-20 2:07 ` Yong Zhang
2024-09-23 1:49 ` Yong Zhang
2024-09-26 9:44 ` Yong Zhang
2024-09-29 1:26 ` Yong Zhang
2024-10-08 1:18 ` Yong Zhang
2024-10-08 2:58 ` [PATCH] " Stephen Hemminger
2024-10-08 6:40 ` zhang.yong25
2024-10-08 16:12 ` Stephen Hemminger [this message]
2024-10-08 16:21 ` [v2 1/5] " Stephen Hemminger
2024-10-14 8:09 ` [v3 1/5] raw/gdtc: introduce gdtc " Yong Zhang
2024-10-14 8:09 ` [v3 2/5] raw/gdtc: add support for queue setup operation Yong Zhang
2024-10-14 8:09 ` [v3 3/5] raw/gdtc: add support for standard rawdev operations Yong Zhang
2024-10-14 8:09 ` [v3 4/5] raw/gdtc: add support for enqueue operation Yong Zhang
2024-10-14 8:09 ` [v3 5/5] raw/gdtc: add support for dequeue operation Yong Zhang
2024-10-15 16:50 ` Patrick Robb
2024-10-15 16:52 ` Patrick Robb
2024-10-14 8:22 ` Re:[PATCH] raw/gdtc: introduce gdtc raw device driver Yong Zhang
2024-10-14 8:33 ` [PATCH] " Morten Brørup
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=20241008091232.7b4b13e6@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=li.min10@zte.com.cn \
--cc=ran.ming@zte.com.cn \
--cc=techboard@dpdk.org \
--cc=thomas@monjalon.net \
--cc=wang.yong19@zte.com.cn \
--cc=zhang.yong25@zte.com.cn \
/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.