All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <oss@buserror.net>
To: Michael Ellerman <mpe@ellerman.id.au>, benh@kernel.crashing.org
Cc: linuxppc-dev@lists.ozlabs.org, galak@kernel.crashing.org,
	Christophe Leroy <christophe.leroy@c-s.fr>,
	chenhui.zhao@freescale.com
Subject: Re: Pull request: scottwood/linux.git next
Date: Tue, 15 Mar 2016 02:01:51 -0500	[thread overview]
Message-ID: <1458025311.12370.18.camel@buserror.net> (raw)
In-Reply-To: <1458001168.8059.3.camel@ellerman.id.au>

On Tue, 2016-03-15 at 11:19 +1100, Michael Ellerman wrote:
> On Fri, 2016-03-11 at 21:15 -0600, Scott Wood wrote:
> 
> > Highlights include 8xx optimizations, 32-bit checksum optimizations, 86xx
> > consolidation, e5500/e6500 cpu hotplug, more fman and other dt bits, and
> > minor fixes/cleanup.
> 
> Hi Scott,
> 
> This one's giving me a few troubles.
> 
> > chenhui zhao (6):
> >       powerpc/mm: any thread in one core can be the first to setup TLB1
> >       powerpc/cache: add cache flush operation for various e500
> >       powerpc/rcpm: add RCPM driver
> 
> That commit doesn't build with SMP=n, as reported by Guenter:
> 
>   arch/powerpc/sysdev/fsl_rcpm.c:32:2: error: implicit declaration of
> function 'get_hard_smp_processor_id' [-Werror=implicit-function-declaration]
> 
> That's not a biggy, I can probably fix it up here.

By adding asm/smp.h?

I missed this since we don't have a non-SMP defconfig that includes this.

> >       powerpc/mpc85xx: Add CPU hotplug support for E6500
> 
> And this one breaks with old binutils (<= 2.22) because of:
> 
>   arch/powerpc/kernel/head_64.S:210: Error: Unrecognized opcode: `mttmr'
> 
> If you're happy to break the build on older bintuils for those configs then
> that's OK with me.

I'm not too bothered, but it's also an easy fix -- patch sent.

> > Christophe Leroy (31):
> >       powerpc/8xx: Handle CPU6 ERRATA directly in mtspr() macro
> 
> This breaks mpc866_ads_defconfig for me, with lots of:
> 
>   arch/powerpc/mm/8xx_mmu.c:139:2: error: memory input 1 is not directly
> addressable
> 
> That's using gcc < 4.9. With >= 4.9 it builds OK. So again your call on
> whether
> we drop support for those compilers for that config.

I'd rather not require something that new, especially for a chip so old.

I've sent an untested patch that should fix it.

-Scott

  reply	other threads:[~2016-03-15  7:01 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-12  3:15 Pull request: scottwood/linux.git next Scott Wood
2016-03-15  0:19 ` Michael Ellerman
2016-03-15  7:01   ` Scott Wood [this message]
2016-03-15  9:07     ` Michael Ellerman
2016-03-15 17:50       ` Scott Wood
2016-03-15 10:27     ` Christophe Leroy
  -- strict thread matches above, loose matches on Subject: below --
2019-11-17  9:44 Scott Wood
2019-10-22 23:21 Scott Wood
2019-10-31  2:01 ` Jason Yan
2019-11-01 17:01   ` Scott Wood
2019-11-04  2:36     ` Jason Yan
2019-11-02 10:38   ` Michael Ellerman
2019-11-04  2:38     ` Jason Yan
2019-11-13  9:23 ` Michael Ellerman
2019-11-14  6:00   ` Jason Yan
2018-12-22  4:42 Scott Wood
2018-12-22 10:50 ` christophe leroy
2018-12-22 20:01   ` Scott Wood
2018-12-23 13:13 ` Michael Ellerman
2018-12-24  2:09   ` Scott Wood
2018-12-27 13:10     ` Christoph Hellwig
2018-12-28  0:03       ` Scott Wood
2018-10-23  0:22 Scott Wood
2018-08-11  5:29 Scott Wood
2018-01-21  7:55 Scott Wood
2018-01-23  5:24 ` Michael Ellerman
2017-08-29  4:20 Scott Wood
2017-05-06  3:42 Scott Wood
2017-01-27 23:53 Scott Wood
2017-02-17 11:08 ` Scott Wood
2017-02-18  8:00   ` Michael Ellerman
2016-12-12  8:17 Scott Wood
2016-12-13 15:49 ` Aneesh Kumar K.V
2016-12-13 18:34   ` Aneesh Kumar K.V
2016-09-27 22:08 Scott Wood
2016-07-21 17:09 Scott Wood
2016-05-17  1:37 Scott Wood
2016-05-19 12:35 ` Michael Ellerman
2016-01-04 21:38 Scott Wood
2016-01-14 13:05 ` Michael Ellerman
2015-10-28 21:56 Scott Wood
2015-08-18  4:30 Scott Wood
2015-08-26 14:14 ` Scott Wood
2015-08-27  1:14   ` Michael Ellerman
2015-06-05 23:06 Scott Wood
2015-04-02 22:47 Scott Wood
2015-02-03 17:20 Scott Wood
2015-02-04  0:58 ` Michael Ellerman
2015-02-04  1:05   ` Scott Wood
2015-02-04  2:25     ` Michael Ellerman
2014-11-18  5:20 Scott Wood
2014-09-22 22:21 Scott Wood
2014-09-23  3:52 ` Bob Cochran
2014-09-23  5:45   ` Scott Wood
2014-09-23 10:47     ` Joakim Tjernlund
2014-09-23 12:37       ` Scott Wood
2014-09-23 16:19     ` Bob Cochran
2014-10-03 19:52 ` Scott Wood
2014-10-03 23:06   ` Stephen Rothwell
2014-08-01 19:54 Scott Wood
2014-07-03  0:51 Scott Wood
2014-03-20  4:25 Scott Wood
2014-03-23 23:16 ` Benjamin Herrenschmidt
2014-03-23 23:33   ` Benjamin Herrenschmidt
2014-03-25  1:09     ` Scott Wood
2013-10-29  2:44 Scott Wood
2013-10-29  3:05 ` Scott Wood
2013-08-24  1:07 Scott Wood
2013-08-26 15:48 ` Scott Wood
2013-08-08 22:45 Scott Wood
2013-08-09  6:03 ` Benjamin Herrenschmidt
2013-08-09 14:43   ` Kumar Gala
2013-08-09 16:30     ` Scott Wood
2013-08-14  4:18 ` Benjamin Herrenschmidt
2013-08-14 17:02   ` Scott Wood
2013-08-14 21:01     ` Benjamin Herrenschmidt
2013-08-19 22:56       ` Scott Wood
2013-08-19 23:47         ` Benjamin Herrenschmidt
2013-08-19 23:49           ` Josh Boyer
2013-08-20  0:49             ` Benjamin Herrenschmidt
2013-07-01 23:43 Scott Wood
2013-07-02  7:43 ` Benjamin Herrenschmidt

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=1458025311.12370.18.camel@buserror.net \
    --to=oss@buserror.net \
    --cc=benh@kernel.crashing.org \
    --cc=chenhui.zhao@freescale.com \
    --cc=christophe.leroy@c-s.fr \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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.