From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: mpartap@gmx.net, merlijn@wizzup.org, martin_rysavy@centrum.cz,
kernel list <linux-kernel@vger.kernel.org>,
sre@kernel.org, nekit1000@gmail.com, linux-omap@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: Droid 4 on 5.5-rc3
Date: Thu, 2 Jan 2020 09:09:49 -0800 [thread overview]
Message-ID: <20200102170949.GA16702@atomide.com> (raw)
In-Reply-To: <20200101201132.GA9612@amd>
Hi,
* Pavel Machek <pavel@ucw.cz> [200101 20:12]:
> I tried v5.5-rc4, and it does not boot either. I'm kexecing from
> 5.3-rc2. Maybe there's Kconfig difference? This is my...
I also tested with your .config and v5.4-rc4 boots just fine
for me on two different droid4s.
The regulator warning is there with built-in drivers that's probably
related to deferred probe and should be fixed though.
But wlan and mmc work meaning what you're seeing is not a regulator
issue.
Regards,
Tony
_______________________________________________
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:[~2020-01-02 17:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-28 16:29 Droid 4 on 5.5-rc3 Pavel Machek
2019-12-28 19:36 ` Pavel Machek
2019-12-30 17:35 ` Tony Lindgren
2020-01-01 20:11 ` Pavel Machek
2020-01-02 17:09 ` Tony Lindgren [this message]
2020-01-01 22:02 ` Pavel Machek
[not found] ` <20200102110025.GA29035@amd>
2020-01-02 11:49 ` Droid 4 regression in 5.5-rc1, armsoc-soc tree Arnd Bergmann
2020-01-02 12:29 ` Pavel Machek
2020-01-02 14:06 ` Pavel Machek
2020-01-02 14:47 ` Arnd Bergmann
2020-01-02 17:11 ` Tony Lindgren
2020-01-02 18:39 ` Pavel Machek
2020-01-02 19:18 ` Pavel Machek
2020-01-02 19:25 ` Tony Lindgren
2020-01-03 15:11 ` Stefan Wahren
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=20200102170949.GA16702@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=martin_rysavy@centrum.cz \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=pavel@ucw.cz \
--cc=sre@kernel.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).