From: <zhang.yong25@zte.com.cn>
To: <thomas@monjalon.net>
Cc: <dev@dpdk.org>, <wang.yong19@zte.com.cn>, <li.min10@zte.com.cn>,
<ran.ming@zte.com.cn>
Subject: Re: [PATCH] raw/gdtc: introduce gdtc raw device driver
Date: Thu, 14 Nov 2024 17:36:42 +0800 (CST) [thread overview]
Message-ID: <20241114173642862Xr9TbaiXAPrUNAEM3X2I8@zte.com.cn> (raw)
In-Reply-To: <5955475.9Mp67QZiUf@thomas>
[-- Attachment #1.1.1: Type: text/plain, Size: 1110 bytes --]
Hi Thomas,
>> I submitted a patch on October 29 and haven't received response.>> Wondering if any modifications are needed? Could you provide an update on the review?>> Thanks. Looking forward to hearing from you.>>I cannot apply your patches because the format looks wrong.>It looks there an issue with line ending. Windows?
I just modified the patch and resubmitted it. The local git apply is OK.
Can you please try again to see if it is OK?
Original
From: ThomasMonjalon <thomas@monjalon.net>
To: 张勇10313449;
Cc: dev@dpdk.org <dev@dpdk.org>;张勇10313449;汪勇10032886;李敏10314441;冉明10033339;
Date: 2024年11月12日 12:12
Subject: Re: [PATCH] raw/gdtc: introduce gdtc raw device driver
Hello,
04/11/2024 03:15, Yong Zhang:
> Hi thomas,
>
> I submitted a patch on October 29 and haven't received response.
> Wondering if any modifications are needed? Could you provide an update on the review?
> Thanks. Looking forward to hearing from you.
I cannot apply your patches because the format looks wrong.
It looks there an issue with line ending. Windows?
[-- Attachment #1.1.2: Type: text/html , Size: 3519 bytes --]
next prev parent reply other threads:[~2024-11-14 9:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 13:45 [v4,1/5] " Yong Zhang
2024-10-29 13:45 ` [v4,2/5] raw/gdtc: add support for queue setup operation Yong Zhang
2024-11-12 5:05 ` Stephen Hemminger
2024-10-29 13:45 ` [v4,3/5] raw/gdtc: add support for standard rawdev operations Yong Zhang
2024-10-29 13:45 ` [v4,4/5] raw/gdtc: add support for enqueue operation Yong Zhang
2024-10-29 13:45 ` [v4,5/5] raw/gdtc: add support for dequeue operation Yong Zhang
2024-11-04 2:15 ` Re:[PATCH] raw/gdtc: introduce gdtc raw device driver Yong Zhang
2024-11-12 4:12 ` [PATCH] " Thomas Monjalon
2024-11-12 5:13 ` Stephen Hemminger
2024-11-14 9:36 ` zhang.yong25 [this message]
2024-11-12 5:08 ` [v4,1/5] " Stephen Hemminger
2024-11-12 5:08 ` Stephen Hemminger
2024-11-13 9:22 ` zhang.yong25
2024-11-13 14:59 ` Stephen Hemminger
2024-11-12 5:09 ` Stephen Hemminger
2024-11-12 5:48 ` Stephen Hemminger
2024-11-14 9:20 ` [v5,1/5] " Yong Zhang
2024-11-14 9:20 ` [v5,2/5] raw/gdtc: add support for queue setup operation Yong Zhang
2024-11-14 9:20 ` [v5,3/5] raw/gdtc: add support for standard rawdev operations Yong Zhang
2024-11-14 9:20 ` [v5,4/5] raw/gdtc: add support for enqueue operation Yong Zhang
2024-11-14 9:20 ` [v5,5/5] raw/gdtc: add support for dequeue operation Yong Zhang
-- strict thread matches above, loose matches on Subject: below --
2024-08-12 7:31 [v2 1/5] raw/zxdh: introduce zxdh raw device driver Yong Zhang
2024-10-14 8:22 ` Re:[PATCH] raw/gdtc: introduce gdtc " 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=20241114173642862Xr9TbaiXAPrUNAEM3X2I8@zte.com.cn \
--to=zhang.yong25@zte.com.cn \
--cc=dev@dpdk.org \
--cc=li.min10@zte.com.cn \
--cc=ran.ming@zte.com.cn \
--cc=thomas@monjalon.net \
--cc=wang.yong19@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 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).