From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: Koelsch on v3.16-rc1
Date: Mon, 16 Jun 2014 12:46:47 +0000 [thread overview]
Message-ID: <20140616124646.GC30357@verge.net.au> (raw)
In-Reply-To: <20140616122903.GB30357@verge.net.au>
On Mon, Jun 16, 2014 at 02:33:11PM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Mon, Jun 16, 2014 at 2:29 PM, Simon Horman <horms@verge.net.au> wrote:
> > I have noticed that Koelsch does not appear to boot on v3.16-rc1.
> > This appears to affect both legacy C (koelsch_defconfig) and
> > multiplatform (shmobile_defconfig).
> >
> > I have not tested to see if this affects any other boards yet.
> >
> > I am currently bisecting the problem (using shmobile_defconfig).
> >
> > However, its a little late in the day and I may not get much further than
> > that today.
>
> https://lkml.org/lkml/2014/6/11/750
Thanks!
I had just arrived at the end of my bisection which isolated that commit.
prev parent reply other threads:[~2014-06-16 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 12:29 Koelsch on v3.16-rc1 Simon Horman
2014-06-16 12:33 ` Geert Uytterhoeven
2014-06-16 12:46 ` Simon Horman [this message]
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=20140616124646.GC30357@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.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).