From: Mark Rutland <mark.rutland@arm.com>
To: Borislav Petkov <bp@alien8.de>
Cc: 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 14:16:15 +0100 [thread overview]
Message-ID: <aGUxH--v32Bv4T81@J2N7QTR9R3.cambridge.arm.com> (raw)
In-Reply-To: <20250702130915.GEaGUve86iYnv337_Z@fat_crate.local>
On Wed, Jul 02, 2025 at 03:09:15PM +0200, Borislav Petkov wrote:
> Hey,
>
> On Wed, Jul 02, 2025 at 01:58:50PM +0100, Mark Rutland wrote:
> > Hi Boris,
> >
> > [ adding Linux and Jinjie, since this is almost certainly due to the
> > irqentry split ]
I was wrong about the above, sorry for the noise!
> It looks to me like that BUGVERBOSE stuff in tip/core/bugs and it warns
> because core/entry starts using it when it gets merged to the rest of the tip
> pile.
Yep; my bisect fingers:
b940c7b8ea92 ("bugs/s390: Use 'cond_str' in __EMIT_BUG()")
| git bisect start
| # bad: [104f02a7798f7e8aba25545f9d485035532260b2] Merge core/entry into tip/master
| git bisect bad 104f02a7798f7e8aba25545f9d485035532260b2
| # bad: [959770cda97b75bc831267fd939408ec58139cb5] Merge locking/core into tip/master
| git bisect bad 959770cda97b75bc831267fd939408ec58139cb5
| # good: [86731a2a651e58953fc949573895f2fa6d456841] Linux 6.16-rc3
| git bisect good 86731a2a651e58953fc949573895f2fa6d456841
| # good: [7abdafd2343ab199367c8243d6a5f06a9aa6976b] Merge tag 'drm-fixes-2025-06-28' of https://gitlab.freedesktop.org/drm/kernel
| git bisect good 7abdafd2343ab199367c8243d6a5f06a9aa6976b
| # good: [2d41eb1b4a70fd8f3ca7f08ed209ae5c8037af62] Merge x86/kconfig into tip/master
| git bisect good 2d41eb1b4a70fd8f3ca7f08ed209ae5c8037af62
| # good: [b7770ed895ab888d0626802a83939f6a30c35576] Merge x86/bugs into tip/master
| git bisect good b7770ed895ab888d0626802a83939f6a30c35576
| # bad: [244efb663e9ead81d3d258d81f38a38af02e09de] Merge core/bugs into tip/master
| git bisect bad 244efb663e9ead81d3d258d81f38a38af02e09de
| # bad: [e7e26cfad96c57c81156693cbf63032d899fe7c9] bugs/s390: Remove private WARN_ON() implementation
| git bisect bad e7e26cfad96c57c81156693cbf63032d899fe7c9
| # good: [66e94df0dd272b057899b8cdbca906ea1306d7a1] bugs/LoongArch: Pass in 'cond_str' to __BUG_ENTRY()
| git bisect good 66e94df0dd272b057899b8cdbca906ea1306d7a1
| # bad: [4218dedd47c79946bc9e6214f50c0d16096873ce] bugs/riscv: Pass in 'cond_str' to __BUG_FLAGS()
| git bisect bad 4218dedd47c79946bc9e6214f50c0d16096873ce
| # good: [7d9e9021ad7e9dac89b8262fbf95630ead7a787a] bugs/s390: Pass in 'cond_str' to __EMIT_BUG()
| git bisect good 7d9e9021ad7e9dac89b8262fbf95630ead7a787a
| # bad: [b940c7b8ea921fae7a99d305e819883d8311669e] bugs/s390: Use 'cond_str' in __EMIT_BUG()
| git bisect bad b940c7b8ea921fae7a99d305e819883d8311669e
| # first bad commit: [b940c7b8ea921fae7a99d305e819883d8311669e] bugs/s390: Use 'cond_str' in __EMIT_BUG()
> Lemme show it to Peter.
Sounds like a plan.
Mark.
next prev parent reply other threads:[~2025-07-02 13:16 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 [this message]
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
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=aGUxH--v32Bv4T81@J2N7QTR9R3.cambridge.arm.com \
--to=mark.rutland@arm.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=oe-kbuild-all@lists.linux.dev \
--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®