From: Randy Dunlap <rdunlap@infradead.org>
To: Philip Schwartz <philquadra@gmail.com>,
linux-kernel@vger.kernel.org, RickyWu <ricky_wu@realtek.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: Bug in your kernel since version 5.2
Date: Mon, 1 Jun 2020 17:35:08 -0700 [thread overview]
Message-ID: <0fc7c8c2-ac6a-2b66-074b-92b5d03219b6@infradead.org> (raw)
In-Reply-To: <CACYmiSfM00o864c5pxxWEQNZsgFMkNwJePCGvae6P7o31NXMyw@mail.gmail.com>
[adding Cc:s and comments]
On 6/1/20 3:52 PM, Philip Schwartz wrote:
> This is my sixth attempt to send a bug report.
>
> The first time you didn't like my email address.
> The second time you didn't like that I copied the whole url.
> The third time you didn't like that the part of the url that I copied
> looked a bit like a url.
> The fourth time you complained that "The message contains HTML
> subpart,therefore we consider it SPAM"
Yes.
> The fifth time you didn't like ?????????.
>
> Kernel dot org Bugzilla I D equals 204003
>
>
> I look forward to your email rejection message.
Please see https://bugzilla.kernel.org/show_bug.cgi?id=204003
Several people are having problems with Intel NUCs and/or
the RTS5229 PCI Express Card Reader/driver, beginning with
5.1-rc1.
Here is one bugzilla comment:
Did a git bisect and found the culprit.
bede03a579b3b4a036003c4862cc1baa4ddc351f is the first bad commit
commit bede03a579b3b4a036003c4862cc1baa4ddc351f
Author: RickyWu <ricky_wu@realtek.com>
Date: Tue Feb 19 20:49:58 2019 +0800
misc: rtsx: Enable OCP for rts522a rts524a rts525a rts5260
this enables and adds OCP function for Realtek A series cardreader chips
and fixes some OCP flow in rts5260.c
Signed-off-by: RickyWu <ricky_wu@realtek.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
:040000 040000 65bfdc473b7b85cb423ff528309fc92d73eae5b4 1292d8564f678027d0e5c77550e37d696b134b28 M drivers
Just revert that and you'll be golden.
rts522a,rts524a,rts525a,rts5260
So somehow OCP got enabled for rts5229 unless a means rts522x. I guess they need to make sure its not enabled for 5229.
{end of bugzilla comment}
--
~Randy
next prev parent reply other threads:[~2020-06-02 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 22:52 Philip Schwartz
2020-06-02 0:35 ` Randy Dunlap [this message]
2020-06-02 0:51 ` Philip Schwartz
2020-06-02 7:13 ` 吳昊澄 Ricky
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=0fc7c8c2-ac6a-2b66-074b-92b5d03219b6@infradead.org \
--to=rdunlap@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=philquadra@gmail.com \
--cc=ricky_wu@realtek.com \
--cc=ulf.hansson@linaro.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
all inboxes | Powered by JetHome®