From: Andreas Schwab <schwab@suse.de>
To: Tony Lindgren <tony@atomide.com>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
linux-arm-kernel@lists.infradead.org,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Linux-OMAP <linux-omap@vger.kernel.org>
Subject: Re: 6.7 regression: platform 4809c000.mmc: deferred probe pending
Date: Thu, 15 Feb 2024 11:28:27 +0100 [thread overview]
Message-ID: <mvmeddeyqb8.fsf@suse.de> (raw)
In-Reply-To: <20240215094640.GS52537@atomide.com> (Tony Lindgren's message of "Thu, 15 Feb 2024 11:46:40 +0200")
On Feb 15 2024, Tony Lindgren wrote:
> There was a regression recently with the PMIC which would cause NFSroot
> on devices to keep working but may have affected MMC. Please check that
> commit 7a29fa05aeca ("mfd: twl6030-irq: Revert to use of_match_device()")
> is applied.
That commit hasn't hit stable yet. Maybe it's because it references a
non-existant commit id (1e0c866887f4 instead of 830fafce06e6).
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@suse.de>
To: Tony Lindgren <tony@atomide.com>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
linux-arm-kernel@lists.infradead.org,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Linux-OMAP <linux-omap@vger.kernel.org>
Subject: Re: 6.7 regression: platform 4809c000.mmc: deferred probe pending
Date: Thu, 15 Feb 2024 11:28:27 +0100 [thread overview]
Message-ID: <mvmeddeyqb8.fsf@suse.de> (raw)
In-Reply-To: <20240215094640.GS52537@atomide.com> (Tony Lindgren's message of "Thu, 15 Feb 2024 11:46:40 +0200")
On Feb 15 2024, Tony Lindgren wrote:
> There was a regression recently with the PMIC which would cause NFSroot
> on devices to keep working but may have affected MMC. Please check that
> commit 7a29fa05aeca ("mfd: twl6030-irq: Revert to use of_match_device()")
> is applied.
That commit hasn't hit stable yet. Maybe it's because it references a
non-existant commit id (1e0c866887f4 instead of 830fafce06e6).
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-15 10:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 13:46 6.7 regression: platform 4809c000.mmc: deferred probe pending Andreas Schwab
2024-02-14 14:00 ` Linux regression tracking (Thorsten Leemhuis)
2024-02-14 14:00 ` Linux regression tracking (Thorsten Leemhuis)
2024-02-15 9:46 ` Tony Lindgren
2024-02-15 9:46 ` Tony Lindgren
2024-02-15 10:28 ` Andreas Schwab [this message]
2024-02-15 10:28 ` Andreas Schwab
2024-02-15 11:16 ` Greg KH
2024-02-15 11:16 ` Greg KH
2024-02-16 12:08 ` Tony Lindgren
2024-02-16 12:08 ` Tony Lindgren
2024-02-19 9:17 ` Andreas Schwab
2024-02-19 9:17 ` Andreas Schwab
2024-02-20 14:35 ` Greg KH
2024-02-20 14:35 ` Greg KH
2024-02-29 7:33 ` Linux regression tracking (Thorsten Leemhuis)
2024-02-29 7:33 ` Linux regression tracking (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=mvmeddeyqb8.fsf@suse.de \
--to=schwab@suse.de \
--cc=aaro.koskinen@iki.fi \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.