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 14:52:44 +0100 [thread overview]
Message-ID: <b6c93e2b-a3d8-448a-8783-697715b968ea@suse.com> (raw)
In-Reply-To: <20260119132811.GDaW4xazonIcw9g0DY@fat_crate.local>
[-- Attachment #1.1.1: Type: text/plain, Size: 1035 bytes --]
On 19.01.26 14:28, Borislav Petkov wrote:
> On Mon, Jan 19, 2026 at 12:52:50PM +0100, Jürgen Groß wrote:
>> 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?
>
> Or, you could redesign your set in a way so that the build error doesn't
> happen and there's no need for an urgent patch with a questionable Fixes: tag?
>
> Also, the "pure luck" thing would need debugging too, to figure out why the
> build error happens.
>
Well, the patch IS the fix for the build error.
paravirt.h just needs to be included if CONFIG_PARAVIRT is set. It isn't
enough to include it only if CONFIG_PARAVIRT_XXL is set.
The patch listed under "Fixes:" moved the halt related functions from the
CONFIG_PARAVIRT_XXL to the CONFIG_PARAVIRT umbrella, but missed to move
the #include of paravirt.h, too. This is what my patch is doing.
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 13: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ß
2026-01-19 13:28 ` Borislav Petkov
2026-01-19 13:52 ` Jürgen Groß [this message]
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=b6c93e2b-a3d8-448a-8783-697715b968ea@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®