From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: non-Multiplatform APE6EVM broken in v3.18-rc1
Date: Tue, 28 Oct 2014 09:23:08 +0000 [thread overview]
Message-ID: <20141028092305.GA11937@verge.net.au> (raw)
In-Reply-To: <20141028004131.GA8280@verge.net.au>
On Tue, Oct 28, 2014 at 08:59:28AM +0100, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Tue, Oct 28, 2014 at 1:41 AM, Simon Horman <horms@verge.net.au> wrote:
> > I have noticed that there appears to be a regression between v3.17 and
> > v3.18-rc1 such that non-multiplatform APE6EVM (ape6evm_defconfig) no longer
> > boots. This appears to be the case using both reference DT (MACH_APE6EVM)
>
> How does it manifest itself?
> If you don't get any console output, have you tried my early debug patch?
IIRC, there was no console output.
I have not tried any out-of tree debug code :)
> > and Legacy-C (MACH_APE6EVM_REFERENCE).
> >
> > I have tried bisecting this problem but dew a blank: the problem
> > seems to arise on a merge commit.
>
> Which merge commit?
Looking over things again my bisection seems bogus.
I can try again but it won't be today.
> > This problem also seems to be present in v3.18-rc2 and the devel and next
> > branches of my renesas tree (which are based on v3.18-rc2 and v3.18-rc1
> > respectively).
> >
> > To be clear this problem, whatever it is, does not seem to affect
> > multiplatform APE6EVM (shmobile_defconfig).
>
> AFAIK, there's no APE6EVM support in multiplatform yet?
Yes, true. I must have imagined that part.
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
next prev parent reply other threads:[~2014-10-28 9:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 0:41 non-Multiplatform APE6EVM broken in v3.18-rc1 Simon Horman
2014-10-28 7:59 ` Geert Uytterhoeven
2014-10-28 9:23 ` Simon Horman [this message]
2014-10-28 9:32 ` Geert Uytterhoeven
2014-10-29 0:12 ` Simon Horman
2014-10-29 2:08 ` Simon Horman
2014-10-29 8:13 ` Geert Uytterhoeven
2014-10-29 9:05 ` Simon Horman
2014-10-30 1:34 ` Simon Horman
2014-11-03 10:33 ` Daniel Lezcano
2014-11-04 0:52 ` Simon Horman
2014-10-29 21:31 ` Geert Uytterhoeven
2014-10-29 23:54 ` Simon Horman
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=20141028092305.GA11937@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).