From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: Qu Wenruo <wqu@suse.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
broonie@kernel.org
Subject: Re: About regression caused by commit aea6cb99703e ("regulator: resolve supply after creating regulator")
Date: Mon, 23 Nov 2020 07:47:27 +0100 [thread overview]
Message-ID: <85cc66a3-2625-acd5-ca28-6ef0abaadd21@siemens.com> (raw)
In-Reply-To: <20201122163534.GA16669@qmqm.qmqm.pl>
On 22.11.20 17:35, Michał Mirosław wrote:
> On Sun, Nov 22, 2020 at 03:43:33PM +0100, Jan Kiszka wrote:
>> On 09.11.20 00:28, Qu Wenruo wrote:
>>> On 2020/11/9 上午1:18, Michał Mirosław wrote:
>>>> On Sun, Nov 08, 2020 at 03:35:33PM +0800, Qu Wenruo wrote:
> [...]
>>>>> It turns out that, commit aea6cb99703e ("regulator: resolve supply after
>>>>> creating regulator") seems to be the cause.
> [...]
>> We are still missing some magic fix for stable trees: On the STM32MP15x,
>> things are broken since 5.4.73 now. And 5.9.y is not booting as well on
>> that board. Reverting the original commit make it boot again.
>>
>> Linus master is fine, though, but I'm tired of bisecting. Any
>> suggestions? Or is there something queued up already?
>
> You might want to look at `git log --grep=aea6cb99703e` if you can't
> wait for a stable backport.
>
Good. Is that flagged and tested for 5.9/5.4 (and whatever is also
affected) already?
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2020-11-23 6:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-08 7:35 About regression caused by commit aea6cb99703e ("regulator: resolve supply after creating regulator") Qu Wenruo
2020-11-08 7:40 ` Qu Wenruo
2020-11-08 17:18 ` Michał Mirosław
2020-11-08 23:28 ` Qu Wenruo
2020-11-22 14:43 ` Jan Kiszka
2020-11-22 16:35 ` Michał Mirosław
2020-11-23 6:47 ` Jan Kiszka [this message]
2020-11-23 8:01 ` Qu Wenruo
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=85cc66a3-2625-acd5-ca28-6ef0abaadd21@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=alexandre.torgue@st.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=mirq-linux@rere.qmqm.pl \
--cc=wqu@suse.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 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).