From: "Dingyan Li" <18500469033@163.com>
To: "Greg KH" <gregkh@linuxfoundation.org>
Cc: stern@rowland.harvard.edu, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re:Re: [PATCH v2] USB: Use EHCI control transfer pid macros instead of constant values.
Date: Sat, 16 Mar 2024 13:35:34 +0800 (CST) [thread overview]
Message-ID: <7ac221bb.256b.18e45c223ba.Coremail.18500469033@163.com> (raw)
In-Reply-To: <2024030910-hurled-ibuprofen-1b52@gregkh>
At 2024-03-09 15:14:48, "Greg KH" <gregkh@linuxfoundation.org> wrote:
>On Sat, Mar 09, 2024 at 11:37:09AM +0800, Dingyan Li wrote:
>> Macros with good names offer better readability. Besides, also move
>> the definition to ehci.h.
>>
>> Signed-off-by: Dingyan Li <18500469033@163.com>
>> Reviewed-by: Alan Stern <stern@rowland.harvard.edu>
>> ---
>> V1 -> V2: Replacement in more places where Alan pointed out.
>>
>
>This should be v3, as you have added Alan's reviewed-by, and added the
>proper versioning information. Please resend it as such as our tools
>can't dig it out from the end of the thread like this :(
>
>thanks,
>
>greg k-h
Hi Greg,
Sorry that I'm not quite familiar with the process. Since I haven't
got any feedback for a while after sending the v3 patch. Do that mean
the patch is accepted? Or anything else I still need to improve?
Regards,
Dingyan
prev parent reply other threads:[~2024-03-16 5:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 17:31 [PATCH] USB: Use EHCI control transfer pid macros instead of constant values Dingyan Li
2024-03-07 18:42 ` Alan Stern
2024-03-08 1:08 ` [PATCH v2] " Dingyan Li
2024-03-08 7:55 ` Greg KH
2024-03-08 20:34 ` Alan Stern
2024-03-09 3:37 ` Dingyan Li
2024-03-09 7:14 ` Greg KH
2024-03-09 9:18 ` [PATCH v3] " Dingyan Li
2024-03-16 5:35 ` Dingyan Li [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=7ac221bb.256b.18e45c223ba.Coremail.18500469033@163.com \
--to=18500469033@163.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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