mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Corentin Labbe <clabbe.montjoie@gmail.com>,
	benh@kernel.crashing.org, paulus@samba.org,
	anju@linux.vnet.ibm.com, maddy@linux.vnet.ibm.com
Cc: Corentin Labbe <clabbe.montjoie@gmail.com>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: powerpc: powernv: Fix build error on const discarding
Date: Thu, 31 Aug 2017 21:36:13 +1000 (AEST)	[thread overview]
Message-ID: <3xjgLQ0DTHz9t1t@ozlabs.org> (raw)
In-Reply-To: <20170816123444.5202-1-clabbe.montjoie@gmail.com>

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

On Wed, 2017-08-16 at 12:34:44 UTC, Corentin Labbe wrote:
> When building a random powerpc kernel I hit this build error:
>   CC      arch/powerpc/platforms/powernv/opal-imc.o
> arch/powerpc/platforms/powernv/opal-imc.c: In function « disable_nest_pmu_counters »:
> arch/powerpc/platforms/powernv/opal-imc.c:130:13: error : assignment discards « const » qualifier from pointer target type [-Werror=discarded-qualifiers]
>    l_cpumask = cpumask_of_node(nid);
>              ^
> This patch simply add const to l_cpumask to fix this issue.
> 
> Signed-off-by: Corentin Labbe <clabbe.montjoie@gmail.com>
> Reviewed-by: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>

Applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/6538ac30841638b2fd345725a9fd15

cheers

      parent reply	other threads:[~2017-08-31 11:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16 12:34 [PATCH] " Corentin Labbe
2017-08-17 12:52 ` Michael Ellerman
2017-08-18 12:58   ` Corentin Labbe
2017-08-25  1:26     ` Michael Ellerman
2017-08-31 11:36 ` 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=3xjgLQ0DTHz9t1t@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=anju@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=clabbe.montjoie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.vnet.ibm.com \
    --cc=paulus@samba.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

all inboxes | Powered by JetHome®