From: "Jürgen Groß" <jgross@suse.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] x86/irqflags: Fix build failure
Date: Mon, 19 Jan 2026 12:52:50 +0100 [thread overview]
Message-ID: <9ba42c1b-0936-4716-b105-c868aced0b82@suse.com> (raw)
In-Reply-To: <20260119113653.GBaW4XVYXXgvJtG-Oy@fat_crate.local>
[-- Attachment #1.1.1: Type: text/plain, Size: 1185 bytes --]
On 19.01.26 12:36, Borislav Petkov wrote:
> On Thu, Jan 15, 2026 at 07:29:37PM +0100, Jürgen Groß wrote:
>> Yes. The problem was introduced by that patch. It was pure luck paravirt.h
>> got included via another header.
>
> So there's no configuration right now which triggers this problem?
I don't know any. This doesn't mean there is none.
>
>> Yes, this would be a possibility. I still can do that, but I saw no real reason
>> to resend the other 5 patches without any change.
>
> You mean, you expect me to read minds? :)
Oh, you can't? ;-)
>
>> TBH I'm quite puzzled that this build failure hasn't been seen before. As I said
>> above: pure luck.
>
> Sorry, we don't do "pure luck."
>
> This either fixes something in the *current* kernel or if not, it should be
> applied as an urgent fix when it does after "pure luck" has been debugged
> properly and explained.
Well, your call in this case.
So do you want me to resend the series triggering the issue with this patch
prepended, or are you fine with applying this patch to the tip branch for
the next merge window, and wait for the other series to get the needed Acks?
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2026-01-19 11:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 16:10 Juergen Gross
2026-01-15 17:45 ` Borislav Petkov
2026-01-15 18:29 ` Jürgen Groß
2026-01-19 11:36 ` Borislav Petkov
2026-01-19 11:52 ` Jürgen Groß [this message]
2026-01-19 13:28 ` Borislav Petkov
2026-01-19 13:52 ` Jürgen Groß
2026-01-19 13:58 ` Jürgen Groß
2026-01-19 14:10 ` Borislav Petkov
2026-01-19 14:22 ` Jürgen Groß
2026-01-19 15:46 ` Borislav Petkov
2026-01-19 16:02 ` Jürgen Groß
2026-01-19 16:24 ` 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=9ba42c1b-0936-4716-b105-c868aced0b82@suse.com \
--to=jgross@suse.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--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®