linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Corentin Labbe <clabbe@baylibre.com>,
	benh@kernel.crashing.org, paulus@samba.org,
	nfont@linux.vnet.ibm.com, tyreld@linux.vnet.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	Corentin Labbe <clabbe@baylibre.com>
Subject: Re: powerpc: add empty update_numa_cpu_lookup_table for !CONFIG_NUMA
Date: Sun, 18 Feb 2018 19:55:30 +1100 (AEDT)	[thread overview]
Message-ID: <3zkgh34GJZz9sWK@ozlabs.org> (raw)
In-Reply-To: <1518610667-23406-1-git-send-email-clabbe@baylibre.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]

On Wed, 2018-02-14 at 12:17:47 UTC, Corentin Labbe wrote:
> When CONFIG_NUMA is not set, build fail with:
> arch/powerpc/platforms/pseries/hotplug-cpu.c:335:4: error: déclaration implicite de la fonction « update_numa_cpu_lookup_table » [-Werror=implicit-function-declaration]
> 
> So we have to add update_numa_cpu_lookup_table as an empty function when CONFIG_NUMA is not set.
> 
> Fixes: 1d9a090783be ("powerpc/numa: Invalidate numa_cpu_lookup_table on cpu remove")
> Signed-off-by: Corentin Labbe <clabbe@baylibre.com>

Applied to powerpc fixes, thanks.

https://git.kernel.org/powerpc/c/c1e150ceb61e4a585bad156da15c33

cheers

      reply	other threads:[~2018-02-18  8:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 12:17 [PATCH] powerpc: add empty update_numa_cpu_lookup_table for !CONFIG_NUMA Corentin Labbe
2018-02-18  8:55 ` 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=3zkgh34GJZz9sWK@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=clabbe@baylibre.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nfont@linux.vnet.ibm.com \
    --cc=paulus@samba.org \
    --cc=tyreld@linux.vnet.ibm.com \
    /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).