From: Michael Ellerman <mpe@ellerman.id.au>
To: Scott Wood <scottwood@freescale.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [BUG] Revert 0b05e2d671c4 'powerpc/32: cacheable_memcpy becomes memcpy'
Date: Thu, 17 Sep 2015 10:38:11 +1000 [thread overview]
Message-ID: <1442450291.8456.1.camel@ellerman.id.au> (raw)
In-Reply-To: <1442420984.2909.179.camel@freescale.com>
On Wed, 2015-09-16 at 11:29 -0500, Scott Wood wrote:
> On Wed, 2015-09-16 at 18:23 +0200, Thomas Gleixner wrote:
> > With this commit applied, my MPC5200 board fails to boot 4.3-rc1. The
> > boot failure is silent.
> >
> > Bisection pointed straight to this commit. Reverting it on top of
> > 4.3-rc1 works like a charm.
>
> Yes, we've been iterating on a fix for this, and I think the patches posted
> earlier today are ready to go in:
>
> http://patchwork.ozlabs.org/patch/518321/
> http://patchwork.ozlabs.org/patch/518323/
Yeah, sorry it took a few iterations, maybe we should have reverted first.
Anyway I'll take that as an ack from you Scott and put these in my fixes branch
with Thomas' Tested-by.
cheers
prev parent reply other threads:[~2015-09-17 0:38 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
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 [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=1442450291.8456.1.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.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 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).