From: Greg KH <gregkh@linuxfoundation.org>
To: duanchenghao <duanchenghao@kylinos.cn>
Cc: stern@rowland.harvard.edu, saranya.gopal@intel.com,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-usb@vger.kernel.org, niko.mauno@vaisala.com, pavel@ucw.cz,
rafael@kernel.org, stanley_chang@realtek.com, tj@kernel.org,
xiehongyu1@kylinos.cn, xy521521@gmail.com,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v4] USB: Fix the issue of task recovery failure caused by USB status when S4 wakes up
Date: Thu, 21 Nov 2024 20:09:37 +0100 [thread overview]
Message-ID: <2024112109-joystick-landlord-5957@gregkh> (raw)
In-Reply-To: <2239f30a31d48b326c1b11a2f551439652781419.camel@kylinos.cn>
On Wed, Nov 06, 2024 at 09:29:15AM +0800, duanchenghao wrote:
> Hi Greg k-h & Alan,
>
> Excuse me, both of you. I've noticed that you haven't replied to the
> emails for quite some time, which prompted me to send this one. I'd
> like to inquire if the proposal in the current email is feasible and if
> it can be integrated into the community.
Sorry, I missed this in the last round of patch reviews. I'll queue it
up after 6.13-rc1 is out as the merge window is closed for adding new
stuff to my trees.
thanks,
greg k-h
next prev parent reply other threads:[~2024-11-21 19:11 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 3:05 [PATCH] USB: Fix the issue of task recovery failure caused by USB status when S4 wakes up Duan Chenghao
2024-09-06 14:05 ` Alan Stern
[not found] ` <1725931490447646.3.seg@mailgw.kylinos.cn>
2024-09-10 9:34 ` duanchenghao
2024-09-10 9:36 ` duanchenghao
2024-09-11 14:40 ` Alan Stern
2024-09-12 3:21 ` duanchenghao
2024-09-12 6:26 ` [PATCH v2] " Duan Chenghao
2024-09-12 15:00 ` [PATCH] " Alan Stern
2024-09-13 1:51 ` duanchenghao
2024-09-13 9:38 ` duanchenghao
2024-09-14 2:43 ` Hongyu Xie
2024-09-23 8:00 ` duanchenghao
2024-09-24 13:38 ` Alan Stern
2024-09-29 3:14 ` duanchenghao
2024-10-09 1:19 ` duanchenghao
2024-10-09 1:54 ` Alan Stern
2024-10-09 2:35 ` duanchenghao
2024-10-09 6:29 ` Gopal, Saranya
2024-10-09 15:50 ` Alan Stern
2024-10-10 5:53 ` duanchenghao
2024-10-10 5:59 ` duanchenghao
2024-10-10 14:21 ` Alan Stern
2024-10-11 1:42 ` duanchenghao
2024-10-11 13:53 ` Alan Stern
2024-10-12 9:46 ` [PATCH v3] " Duan Chenghao
2024-10-12 12:39 ` Greg KH
2024-10-12 12:40 ` Greg KH
2024-10-12 15:06 ` Alan Stern
2024-10-12 9:51 ` [PATCH] " duanchenghao
2024-10-12 15:01 ` Alan Stern
2024-10-14 1:32 ` duanchenghao
2024-10-14 1:41 ` duanchenghao
2024-10-14 4:10 ` Gopal, Saranya
2024-10-16 8:57 ` Gopal, Saranya
2024-10-16 9:06 ` duanchenghao
2024-10-24 2:40 ` [PATCH v4] " Duan Chenghao
2024-10-24 2:53 ` duanchenghao
2024-10-24 7:05 ` Greg KH
2024-10-24 8:46 ` duanchenghao
2024-10-29 3:27 ` Greg KH
2024-10-29 8:01 ` duanchenghao
2024-11-06 1:29 ` duanchenghao
2024-11-21 19:09 ` Greg KH [this message]
2024-11-20 2:14 ` 回复：[PATCH " Duan Chenghao
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=2024112109-joystick-landlord-5957@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=duanchenghao@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@intel.com \
--cc=niko.mauno@vaisala.com \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=saranya.gopal@intel.com \
--cc=stanley_chang@realtek.com \
--cc=stern@rowland.harvard.edu \
--cc=tj@kernel.org \
--cc=xiehongyu1@kylinos.cn \
--cc=xy521521@gmail.com \
/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