regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	linux-amlogic@lists.infradead.org,  linux-mmc@vger.kernel.org,
	Brian Norris <briannorris@chromium.org>,
	 Shawn Lin <shawn.lin@rock-chips.com>,
	Luca Weiss <luca@z3ntu.xyz>
Subject: Re: Odroid-C1 regression with commit 4bc31edebde5 ("mmc: core: Set HS clock speed before sending HS CMD13")
Date: Mon, 5 Jun 2023 23:01:31 +0200	[thread overview]
Message-ID: <CAFBinCAh3s6pHa6q20=cB86qJCaYRq3bKwZtwah2_DGLcGFB6g@mail.gmail.com> (raw)
In-Reply-To: <5eb7694f-8c45-bab8-4d4c-2852f125f0eb@leemhuis.info>

Hi Thorsten,

On Fri, Jun 2, 2023 at 3:17 PM Linux regression tracking (Thorsten
Leemhuis) <regressions@leemhuis.info> wrote:
>
> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
> for once, to make this easily accessible to everyone.
>
> Ulf, Martin, what happened to this? It looks like we didn't get any
> closer to fixing this regression in the last two weeks. Did it fall
> through the cracks? Or was progress made and I just missed it?
Life got in the way so there's no progress on my end.
I'm hoping that Ulf has some more ideas that I can work with though.


Best regards,
Martin

  reply	other threads:[~2023-06-05 21:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFBinCD0RT0p-jk86W0JuMT3ufohRh1RqWCcM35DKZJpuc10HQ@mail.gmail.com>
2023-04-13 14:00 ` Odroid-C1 regression with commit 4bc31edebde5 ("mmc: core: Set HS clock speed before sending HS CMD13") Linux regression tracking (Thorsten Leemhuis)
     [not found] ` <CAPDyKFqgYnBfm-NespEZF8AJ5Ou4Bya8jLfVEnfyZvfAZ05Q7Q@mail.gmail.com>
     [not found]   ` <CAFBinCDjPJHEhN-Jx3DhhhHJ3yi8oEoW7u4-Ld6Rd1+W826ttA@mail.gmail.com>
     [not found]     ` <CAPDyKFqKSWJkJwgCO89jgKQ6AB==P9BWkuX6XtKj=ASOH15y9g@mail.gmail.com>
     [not found]       ` <CAFBinCDwgYw3v31hP4AtV3+Z1o+esDqMKugRwMMMLqSX0Acjzw@mail.gmail.com>
     [not found]         ` <CAPDyKFr+hQo+N31r=3f58taf9sYW0UF0ApCJhwz9vRsyNizcvg@mail.gmail.com>
     [not found]           ` <CAFBinCDSv_vdu5887vveotvaOGFrZvaSX4jM+7Q3QvDhTdazzw@mail.gmail.com>
2023-06-02 13:17             ` Linux regression tracking (Thorsten Leemhuis)
2023-06-05 21:01               ` Martin Blumenstingl [this message]
     [not found]             ` <CAPDyKFpS-UwiaRPMqSpX0mNPrS5p=yJzu3g0=pGyCkWHSYyqWg@mail.gmail.com>
     [not found]               ` <CAFBinCCnB=po9x6tsxCzRM99ZqgV9=5jBxS9LaoJqLPGZYSH6g@mail.gmail.com>
     [not found]                 ` <CAPDyKFpAGUudAJKAmzMbcM=LrALU6ELpwaD-ijy18o7yrPgOqA@mail.gmail.com>
2023-08-29  9:59                   ` Linux regression tracking (Thorsten Leemhuis)
2023-09-11  8:48                     ` Thorsten Leemhuis

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='CAFBinCAh3s6pHa6q20=cB86qJCaYRq3bKwZtwah2_DGLcGFB6g@mail.gmail.com' \
    --to=martin.blumenstingl@googlemail.com \
    --cc=briannorris@chromium.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=luca@z3ntu.xyz \
    --cc=regressions@lists.linux.dev \
    --cc=shawn.lin@rock-chips.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;
as well as URLs for NNTP newsgroup(s).