From: Borislav Petkov <bp@alien8.de>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Heiko Carstens <hca@linux.ibm.com>,
Mark Rutland <mark.rutland@arm.com>,
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>
Subject: Re: [tip:master 19/19] include/linux/irq-entry-common.h:201:2: error: unexpected token
Date: Wed, 2 Jul 2025 20:12:36 +0200 [thread overview]
Message-ID: <20250702181236.GGaGV2lAMxdCg_7MoX@fat_crate.local> (raw)
In-Reply-To: <20250702180136.GA3452438@ax162>
On Wed, Jul 02, 2025 at 11:01:36AM -0700, Nathan Chancellor wrote:
> Thanks Peter. Did something go awry with the latest rebase? It looks
> like current core/bugs has the loongarch issue fixed but "bugs/s390: Use
> 'cond_str' in __EMIT_BUG()" seems to have reverted to the broken
> version?
Ah crap, lemme fix that.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2025-07-02 18:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 21:56 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
2025-07-02 16:10 ` Peter Zijlstra
2025-07-02 18:01 ` Nathan Chancellor
2025-07-02 18:12 ` Borislav Petkov [this message]
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=20250702181236.GGaGV2lAMxdCg_7MoX@fat_crate.local \
--to=bp@alien8.de \
--cc=hca@linux.ibm.com \
--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
all inboxes | Powered by JetHome®