From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Aleksa Vučković" <aleksav013@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: PROBLEM: dmesg tracedumps on rtsx_usb module loading during boot
Date: Fri, 8 Jul 2022 15:53:22 +0200 [thread overview]
Message-ID: <Ysg20t2t/S11idyx@kroah.com> (raw)
In-Reply-To: <20220708134942.r3nhwzgh4nchaebi@artix.localdomain>
On Fri, Jul 08, 2022 at 03:49:42PM +0200, Aleksa Vučković wrote:
> [1.] One line summary of the problem:
> dmesg tracedumps on rtsx_usb module loading during boot
This should be fixed in linux-next now, right?
Shuah (on cc:) send in some commits to resolve this, look at this
thread:
https://lore.kernel.org/all/cover.1656642167.git.skhan@linuxfoundation.org/
If you could test those 2 patches, that would be great.
thanks,
greg k-h
next prev parent reply other threads:[~2022-07-08 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 13:49 PROBLEM: dmesg tracedumps on rtsx_usb module loading during boot Aleksa Vučković
2022-07-08 13:53 ` Greg Kroah-Hartman [this message]
2022-07-08 19:09 ` Shuah Khan
2022-07-08 23:06 ` Aleksa Vučković
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=Ysg20t2t/S11idyx@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aleksav013@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.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