From: "吳昊澄 Ricky" <ricky_wu@realtek.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
"ricky_wu@realtek.corp-partner.google.com"
<ricky_wu@realtek.corp-partner.google.com>,
"sashal@kernel.org" <sashal@kernel.org>,
"levinale@google.com" <levinale@google.com>,
"keitasuzuki.park@sslab.ics.keio.ac.jp"
<keitasuzuki.park@sslab.ics.keio.ac.jp>,
"kdlnx@doth.eu" <kdlnx@doth.eu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] rtsx: pci: fix device aspm state bug
Date: Thu, 21 Jan 2021 08:15:46 +0000 [thread overview]
Message-ID: <46473ff62a284bf1bdb703e13884beac@realtek.com> (raw)
In-Reply-To: <YAk2NtOqIohpBJIt@kroah.com>
> -----Original Message-----
> From: gregkh@linuxfoundation.org <gregkh@linuxfoundation.org>
> Sent: Thursday, January 21, 2021 4:07 PM
> To: 吳昊澄 Ricky <ricky_wu@realtek.com>
> Cc: arnd@arndb.de; ricky_wu@realtek.corp-partner.google.com;
> sashal@kernel.org; levinale@google.com; keitasuzuki.park@sslab.ics.keio.ac.jp;
> kdlnx@doth.eu; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] rtsx: pci: fix device aspm state bug
>
> On Thu, Jan 21, 2021 at 07:33:03AM +0000, 吳昊澄 Ricky wrote:
> > Hi Greg kh,
> >
> > This patch to fix misc: rtsx bug for kernel 5.4
>
> I do not understand what this means, sorry. Can you please explain it?
>
On the newest upstream we don’t set config space for en/disable aspm,
so it will not happen this issue
but on kernel 5.4 longterm version we need to fix it
>
> ------Please consider the environment before printing this e-mail.
next prev parent reply other threads:[~2021-01-21 8:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 7:28 [PATCH] rtsx: pci: fix device aspm state bug ricky_wu
2021-01-21 7:33 ` 吳昊澄 Ricky
2021-01-21 8:07 ` gregkh
2021-01-21 8:15 ` 吳昊澄 Ricky [this message]
2021-01-21 8:27 ` gregkh
2021-01-21 10:07 ` 吳昊澄 Ricky
2021-01-21 7:45 ` Greg KH
2021-01-21 7:59 ` 吳昊澄 Ricky
-- strict thread matches above, loose matches on Subject: below --
2021-01-21 7:28 ricky_wu
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=46473ff62a284bf1bdb703e13884beac@realtek.com \
--to=ricky_wu@realtek.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=kdlnx@doth.eu \
--cc=keitasuzuki.park@sslab.ics.keio.ac.jp \
--cc=levinale@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ricky_wu@realtek.corp-partner.google.com \
--cc=sashal@kernel.org \
/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