From: Stephen Boyd <sboyd@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: "kernelci.org bot" <bot@kernelci.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
enric.balletbo@collabora.com, guillaume.tucker@collabora.com,
khilman@baylibre.com, matthew.hart@linaro.org,
mgalka@collabora.com, tomeu.vizoso@collabora.com,
Chen-Yu Tsai <wens@csie.org>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: clk/clk-next boot bisection: v5.3-rc1-79-g31f58d2f58cb on sun8i-h3-libretech-all-h3-cc
Date: Thu, 15 Aug 2019 09:01:01 -0700 [thread overview]
Message-ID: <20190815160101.CC5C2206C1@mail.kernel.org> (raw)
In-Reply-To: <20190815151616.2A298206C1@mail.kernel.org>
Quoting Stephen Boyd (2019-08-15 08:16:15)
> Quoting Mark Brown (2019-08-15 04:26:14)
> > On Wed, Aug 14, 2019 at 09:02:20PM -0700, Stephen Boyd wrote:
> > > Quoting kernelci.org bot (2019-08-14 20:35:25)
> >
> > > > clk/clk-next boot bisection: v5.3-rc1-79-g31f58d2f58cb on sun8i-h3-libretech-all-h3-cc
> >
> > > If this is the only board that failed, great! Must be something in a
> > > sun8i driver that uses the init structure after registration.
> >
> > The infrastructure suppresses duplicate-seeming bisections so I'd not
> > count on it, check the reports on the web site.
>
> Hmm ok. I can remove the change from -next, but I'd still like to figure
> out what is using the init pointer after registration. Is there a way to
> get earlycon logs?
Ok I sent a patch series which may solve the problem for Allwinner.
next prev parent reply other threads:[~2019-08-15 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 3:35 clk/clk-next boot bisection: v5.3-rc1-79-g31f58d2f58cb on sun8i-h3-libretech-all-h3-cc kernelci.org bot
2019-08-15 4:02 ` Stephen Boyd
2019-08-15 11:26 ` Mark Brown
2019-08-15 15:16 ` Stephen Boyd
2019-08-15 16:01 ` Stephen Boyd [this message]
2019-08-15 18:02 ` Stephen Boyd
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=20190815160101.CC5C2206C1@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=bot@kernelci.org \
--cc=broonie@kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=guillaume.tucker@collabora.com \
--cc=khilman@baylibre.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.hart@linaro.org \
--cc=maxime.ripard@bootlin.com \
--cc=mgalka@collabora.com \
--cc=mturquette@baylibre.com \
--cc=s.nawrocki@samsung.com \
--cc=tomeu.vizoso@collabora.com \
--cc=wens@csie.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).