From: Tony Lindgren <tony@atomide.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: "kernelci.org bot" <bot@kernelci.org>, Tejun Heo <tj@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
tomeu.vizoso@collabora.com, guillaume.tucker@collabora.com,
mgalka@collabora.com, Thomas Gleixner <tglx@linutronix.de>,
broonie@kernel.org, matthew.hart@linaro.org,
khilman@baylibre.com, enric.balletbo@collabora.com,
Ingo Molnar <mingo@kernel.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Kevin Hilman <khilman@kernel.org>,
linux-omap@vger.kernel.org
Subject: Re: next/master boot bisection: next-20190430 on beagle-xm
Date: Wed, 1 May 2019 14:17:49 -0700 [thread overview]
Message-ID: <20190501211749.GN8007@atomide.com> (raw)
In-Reply-To: <20190501211344.v5n7bmb2p5kksa47@linutronix.de>
* Sebastian Andrzej Siewior <bigeasy@linutronix.de> [190501 21:14]:
> On 2019-05-01 13:21:49 [-0700], Tony Lindgren wrote:
> > Hi,
> Hi,
>
> > OK I found two issues. It seems that d_can also needs osc clock
> > on am335x. And there's no revision register for d_can.. We're now
> > reading the CTL register unnecessarily.
> >
> > Below is what I hope fixes the boot issue for you, care to boot
> > test?
>
> yup, that boots.
OK good to hear and thanks a lot for testing it. I'll post two
patches shortly.
Regards,
Tony
next prev parent reply other threads:[~2019-05-01 21:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 20:51 next/master boot bisection: next-20190430 on beagle-xm kernelci.org bot
2019-05-01 15:37 ` Sebastian Andrzej Siewior
2019-05-01 16:29 ` Tony Lindgren
2019-05-01 16:44 ` Sebastian Andrzej Siewior
2019-05-01 16:52 ` Tony Lindgren
2019-05-01 17:01 ` Sebastian Andrzej Siewior
2019-05-01 17:44 ` Tony Lindgren
2019-05-01 19:03 ` Sebastian Andrzej Siewior
2019-05-01 20:21 ` Tony Lindgren
2019-05-01 21:13 ` Sebastian Andrzej Siewior
2019-05-01 21:17 ` Tony Lindgren [this message]
2019-05-01 21:48 ` Kevin Hilman
2019-05-02 7:16 ` Sebastian Andrzej Siewior
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=20190501211749.GN8007@atomide.com \
--to=tony@atomide.com \
--cc=bigeasy@linutronix.de \
--cc=bot@kernelci.org \
--cc=broonie@kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=guillaume.tucker@collabora.com \
--cc=hannes@cmpxchg.org \
--cc=jiangshanlai@gmail.com \
--cc=khilman@baylibre.com \
--cc=khilman@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=matthew.hart@linaro.org \
--cc=mgalka@collabora.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=tomeu.vizoso@collabora.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