public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vineet Gupta <vgupta@synopsys.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>, Arnd Bergmann <arnd@arndb.de>
Cc: Jason Cooper <jason@lakedaemon.net>,
	Noam Camus <noamc@ezchip.com>,
	arcml <linux-snps-arc@lists.infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Marc Zyngier <marc.zyngier@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] irqchip: nps: add 64BIT dependency
Date: Fri, 20 May 2016 13:52:10 +0530	[thread overview]
Message-ID: <573EC932.5060106@synopsys.com> (raw)
In-Reply-To: <CAMuHMdUGsgix3-r60rhv8ds+1n6mMbNGxsLR1h5PP3oHVsuBSw@mail.gmail.com>

On Friday 20 May 2016 01:04 PM, Geert Uytterhoeven wrote:
> Hi Arnd,
> 
> On Thu, May 12, 2016 at 11:03 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>> The newly added nps irqchip driver causes build warnings on ARM64.
>>
>> include/soc/nps/common.h: In function 'nps_host_reg_non_cl':
>> include/soc/nps/common.h:148:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
>>
>> As the driver is only used on ARC, we don't need to see it without
>> COMPILE_TEST elsewhere, and we can avoid the warnings by only
>> building on 32-bit architectures even with CONFIG_COMPILE_TEST.
>>
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>> ---
>>  drivers/irqchip/Kconfig | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/irqchip/Kconfig b/drivers/irqchip/Kconfig
>> index 83775f148158..37289cf6b449 100644
>> --- a/drivers/irqchip/Kconfig
>> +++ b/drivers/irqchip/Kconfig
>> @@ -253,6 +253,7 @@ config MVEBU_ODMI
>>
>>  config EZNPS_GIC
>>         bool "NPS400 Global Interrupt Manager (GIM)"
>> +       depends on ARC || (COMPILE_TEST && !64BIT)
>>         select IRQ_DOMAIN
>>         help
>>           Support the EZchip NPS400 global interrupt controller
> 
> As ARC_PLAT_EZNPS already selects EZNPS_GIC, I'd like to suggest
> the slight simpler (whitespace-damaged):

I'm afraid you are late to party - this has been sent Linus' way earlier today !
But it does look prettier so we can do this after rc1

> 
> --- a/drivers/irqchip/Kconfig
> +++ b/drivers/irqchip/Kconfig
> @@ -255,7 +255,8 @@ config PARTITION_PERCPU
>         bool
> 
>  config EZNPS_GIC
> -       bool "NPS400 Global Interrupt Manager (GIM)"
> +       bool "NPS400 Global Interrupt Manager (GIM)" if COMPILE_TEST
> +       depends on !64BIT
>         select IRQ_DOMAIN
>         help
>           Support the EZchip NPS400 global interrupt controller
> 
> Gr{oetje,eeting}s,
> 
>                         Geert
> 

  reply	other threads:[~2016-05-20  8:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 21:03 [PATCH] irqchip: nps: add 64BIT dependency Arnd Bergmann
2016-05-13  8:24 ` Marc Zyngier
2016-05-13  8:35   ` Vineet Gupta
2016-05-13  8:39     ` Marc Zyngier
2016-05-13  9:51     ` Arnd Bergmann
2016-05-13 10:25       ` Marc Zyngier
2016-05-13 10:39         ` Vineet Gupta
2016-05-17 19:39           ` Thomas Gleixner
2016-05-20  7:34 ` Geert Uytterhoeven
2016-05-20  8:22   ` Vineet Gupta [this message]
2016-05-20  8:25     ` Geert Uytterhoeven

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=573EC932.5060106@synopsys.com \
    --to=vgupta@synopsys.com \
    --cc=arnd@arndb.de \
    --cc=geert@linux-m68k.org \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=marc.zyngier@arm.com \
    --cc=noamc@ezchip.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