From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
kernel test robot <lkp@intel.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
"kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ofer Levi <oferle@mellanox.com>,
Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Subject: Re: {standard input}:5973: Error: operand out of range (512 is not between -512 and 511)
Date: Mon, 24 Aug 2020 19:27:44 +0000 [thread overview]
Message-ID: <2c666b4f-d88d-d301-0652-ed021d86de71@synopsys.com> (raw)
In-Reply-To: <28384fea-4a07-c57d-04b0-f44f1c70adc2@synopsys.com>
On 8/24/20 11:21 AM, Vineet Gupta wrote:
>> and the assembler does not like that.
>> After the removal CONFIG_ARC_PLAT_EZNPS I got to stage 2:
>> |drivers/irqchip/irq-eznps.c:80:16: error: 'CTOP_AUX_IACK' undeclared (first use in this function)
>> | 80 | write_aux_reg(CTOP_AUX_IACK, 1 << irq);
>>
> Indeed this is a problem I can reproduce. Enabling CONFIG_EZNPS_GIC on a non
> ARC700 build causes the issue: the ctop header is inside platform code
> (arch/arc/plat-eznps/include/plat/ctop.h) which obviously fails if not building
> for ARC.
>
> My solution is to move ctop.h to include/soc/nps/plat/.
This is turning out to be rat's nest. That header when moved causes other issues.
I don't have time to clean up all the mess so I'll just fix it up by doing the
minimal change.
-Vineet
next prev parent reply other threads:[~2020-08-24 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 2:17 kernel test robot
2020-08-24 9:58 ` Sebastian Andrzej Siewior
2020-08-24 18:21 ` Vineet Gupta
2020-08-24 19:27 ` Vineet Gupta [this message]
2020-08-24 19:35 ` Sebastian Andrzej Siewior
2020-08-24 20:29 ` Vineet Gupta
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=2c666b4f-d88d-d301-0652-ed021d86de71@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=bigeasy@linutronix.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=lkp@intel.com \
--cc=oferle@mellanox.com \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®