linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Fix shmobile build with CONFIG_SMP=n
Date: Mon, 8 Aug 2016 13:01:11 +0200	[thread overview]
Message-ID: <20160808110111.GI17838@verge.net.au> (raw)
In-Reply-To: <20160802193524.GA6423@localhost>

On Tue, Aug 02, 2016 at 12:35:24PM -0700, Olof Johansson wrote:
> Hi,
> 
> On Thu, Jul 21, 2016 at 08:14:17AM +0900, Simon Horman wrote:
> > On Tue, Jul 19, 2016 at 02:02:53PM +0200, Geert Uytterhoeven wrote:
> > > Hi Russell,
> > > 
> > > On Tue, Jul 19, 2016 at 1:57 PM, Russell King - ARM Linux
> > > <linux@armlinux.org.uk> wrote:
> > > > Shmobile currently fails to build when CONFIG_SMP is disabled:
> > > >
> > > > arch/arm/mach-shmobile/built-in.o: In function `shmobile_smp_init_fallback_ops':
> > > > pm-rcar-gen2.c:(.init.text+0x744): undefined reference to `platform_can_secondary_boot'
> > > > make[1]: *** [vmlinux] Error 1
> > > >
> > > > Fix this by providing a stub for this function.
> > > >
> > > > Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
> > > 
> > > Arnd send a smaller one https://patchwork.kernel.org/patch/9207413/,
> > > which seems have fallen through the cracks.
> > 
> > Sorry for missing that. I have queued up Arnd's patch as a fix for v4.8
> > with Acked-by Geert and a Reported-by Russel tags.
> 
> Since I haven't seen this patch yet, I've applied it (Arnd's version) directly
> to our fixes branch.

Thanks. The progression through my tree got delayed by me taking
a holiday last week. I'll drop it from my tree as you have picked it up.

      reply	other threads:[~2016-08-08 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 11:57 [PATCH] Fix shmobile build with CONFIG_SMP=n Russell King - ARM Linux
2016-07-19 12:02 ` Geert Uytterhoeven
2016-07-20 23:14   ` Simon Horman
2016-08-02 19:35     ` Olof Johansson
2016-08-08 11:01       ` 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=20160808110111.GI17838@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.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).