From: Richard Weinberger <richard@nod.at>
To: bp <bp@alien8.de>
Cc: "Fabian Franz" <fabian@isomorphic-ai.com>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Thorsten Leemhuis" <regressions@leemhuis.info>,
"anton ivanov" <anton.ivanov@cambridgegreys.com>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Nikolay Borisov" <nik.borisov@suse.com>,
"Xin Li (Intel)" <xin@zytor.com>,
"Ingo Molnar" <mingo@kernel.org>,
"Claude Fable 5" <noreply@anthropic.com>,
linux-um <linux-um@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
regressions <regressions@lists.linux.dev>
Subject: Re: [PATCH REGRESSION] um: Fix cpu_feature_enabled() build breakage
Date: Mon, 24 Aug 2026 16:28:13 +0200 (CEST) [thread overview]
Message-ID: <2060717447.2694.1787581693960.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20260824142048.GBaoxTQKUUtmflxuyB@fat_crate.local>
----- Ursprüngliche Mail -----
> Von: "bp" <bp@alien8.de>
>> However, getting the minimal patch for um in ASAP would also be good,
>> as a broken master is not nice for development.
>
> It happens during the merge window.
Agreed. Nobody got hurt. All hamsters still alive.
>
> UML folks, you wanna take Thomas' patch or should I route it through tip?
If you don't mind, please carry it through tip.
Thanks,
//richard
prev parent reply other threads:[~2026-08-24 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 20:14 [PATCH REGRESSION] um: Fix cpu_feature_enabled() build breakage Fabian Franz
2026-08-24 6:54 ` Thorsten Leemhuis
2026-08-24 7:35 ` Thomas Weißschuh
2026-08-24 10:22 ` Fabian Franz
2026-08-24 14:20 ` Borislav Petkov
2026-08-24 14:28 ` Richard Weinberger [this message]
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=2060717447.2694.1787581693960.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=anton.ivanov@cambridgegreys.com \
--cc=bp@alien8.de \
--cc=fabian@isomorphic-ai.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=mingo@kernel.org \
--cc=nik.borisov@suse.com \
--cc=noreply@anthropic.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=thomas.weissschuh@linutronix.de \
--cc=xin@zytor.com \
/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