From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Scott Wood <scottwood@freescale.com>,
linuxppc-dev@lists.ozlabs.org,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [BUG] Revert 0b05e2d671c4 'powerpc/32: cacheable_memcpy becomes memcpy'
Date: Fri, 18 Sep 2015 09:32:04 -0500 [thread overview]
Message-ID: <20150918143204.GE29692@gate.crashing.org> (raw)
In-Reply-To: <1442570517.5528.3.camel@ellerman.id.au>
On Fri, Sep 18, 2015 at 08:01:57PM +1000, Michael Ellerman wrote:
> Weird.
>
> Can you try:
>
> d690740f22f6 ("powerpc/powernv: Enable LEDS support")
>
> That is the commit before my merge of Scott's tree, which had all the Freescale
> & 32-bit stuff.
>
> If that works, it would isolate it to only about 30 commits from Scott's tree.
My theory is it is not a kernel problem at all; instead, uboot overwrites
some little part of the kernel image.
Segher
next prev parent reply other threads:[~2015-09-18 14:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 16:23 [BUG] Revert 0b05e2d671c4 'powerpc/32: cacheable_memcpy becomes memcpy' Thomas Gleixner
2015-09-16 16:29 ` Scott Wood
2015-09-16 20:01 ` Thomas Gleixner
2015-09-17 1:54 ` Steven Rostedt
2015-09-17 2:50 ` Michael Ellerman
2015-09-17 3:18 ` Segher Boessenkool
2015-09-17 9:47 ` David Laight
2015-09-17 14:01 ` Segher Boessenkool
2015-09-17 10:13 ` Thomas Gleixner
2015-09-17 13:29 ` Steven Rostedt
2015-09-17 14:38 ` Thomas Gleixner
2015-09-17 14:52 ` Steven Rostedt
2015-09-17 15:22 ` Thomas Gleixner
2015-09-17 15:38 ` Segher Boessenkool
2015-09-18 10:01 ` Michael Ellerman
2015-09-18 14:32 ` Segher Boessenkool [this message]
2015-09-18 14:45 ` Thomas Gleixner
2015-09-21 7:10 ` Michael Ellerman
2015-09-21 20:45 ` Scott Wood
2015-09-17 0:38 ` Michael Ellerman
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=20150918143204.GE29692@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=rostedt@goodmis.org \
--cc=scottwood@freescale.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.