Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: Heiko Carstens <hca@linux.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Borislav Petkov <bp@alien8.de>, kernel test robot <lkp@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Jinjie Ruan <ruanjinjie@huawei.com>,
	Nathan Chancellor <nathan@kernel.org>
Subject: Re: [tip:master 19/19] include/linux/irq-entry-common.h:201:2: error: unexpected token
Date: Wed, 2 Jul 2025 17:41:37 +0200	[thread overview]
Message-ID: <20250702154137.71390C24-hca@linux.ibm.com> (raw)
In-Reply-To: <20250702150739.GT1613376@noisy.programming.kicks-ass.net>

On Wed, Jul 02, 2025 at 05:07:39PM +0200, Peter Zijlstra wrote:
> > > > diff --git a/arch/s390/include/asm/bug.h b/arch/s390/include/asm/bug.h
> > > > index a185855ab158..46d9eb64bd18 100644
> > > > --- a/arch/s390/include/asm/bug.h
> > > > +++ b/arch/s390/include/asm/bug.h
> > > > @@ -9,7 +9,7 @@
> > > >  #else
> > > >  #define __BUGVERBOSE_LOCATION(file, line)			\
> > > >  		.pushsection .rodata.str, "aMS", @progbits, 1;	\
> > > > -	10002:	.string file;					\
> > > > +	10002:	.ascii file;					\
> > > >  		.popsection;					\
> > > >  								\
> > > >  		.long 10002b - .;				\
> > > > 
> > > 
> > > IIUC this also needs a trailing "\0" as per the link above, or this
> > > won't get a NUL-terminator (but will build just fine).
> > 
> > Yup, I ran into this before. Let me go fix that commit.
> 
>  + e7e26cfad96c...2a20b2730147 core/bugs -> core/bugs (forced update)

Thank you! But wouldn't you also need to merge Nathan's patch [1] into
the loongarch commit (or maybe you are just about to do that)?

[1] https://lore.kernel.org/all/20250616-loongarch-fix-warn-cond-llvm-ias-v1-1-6c6d90bb4466@kernel.org/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=core/bugs&id=5d476f66e6add0b709a09d60feecff3a2d156800

  reply	other threads:[~2025-07-02 15:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01 21:56 [tip:master 19/19] include/linux/irq-entry-common.h:201:2: error: unexpected token kernel test robot
2025-07-02 12:32 ` Borislav Petkov
2025-07-02 12:58   ` Mark Rutland
2025-07-02 13:09     ` Borislav Petkov
2025-07-02 13:16       ` Mark Rutland
2025-07-02 13:24         ` Borislav Petkov
2025-07-02 14:16           ` Mark Rutland
2025-07-02 14:54             ` Peter Zijlstra
2025-07-02 15:07               ` Peter Zijlstra
2025-07-02 15:41                 ` Heiko Carstens [this message]
2025-07-02 16:10                   ` Peter Zijlstra
2025-07-02 18:01                     ` Nathan Chancellor
2025-07-02 18:12                       ` Borislav Petkov
2025-07-02 18:29                         ` Borislav Petkov
2025-07-02 18:38                           ` Nathan Chancellor
2025-07-02 18:40                             ` Borislav Petkov

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=20250702154137.71390C24-hca@linux.ibm.com \
    --to=hca@linux.ibm.com \
    --cc=bp@alien8.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=mark.rutland@arm.com \
    --cc=nathan@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=peterz@infradead.org \
    --cc=ruanjinjie@huawei.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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