From: Thorsten Blum <blum@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Dave Hansen <dave.hansen@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Jesse Barnes <jbarnes@hobbes.lan>, Lukas Wunner <lukas@wunner.de>,
Ingo Molnar <mingo@elte.hu>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v2] x86/early-quirks: Scan all functions in early_pci_scan_bus()
Date: Sun, 22 Nov 2026 02:56:00 +0100 [thread overview]
Message-ID: <awJLsDWI0OgdWhph@kernel.org> (raw)
In-Reply-To: <20261118222141.GBav4k9eZ5-QMjOem4@fat_crate.local>
On Wed, Nov 18, 2026 at 02:21:41PM -0800, Borislav Petkov wrote:
> On Wed, Nov 18, 2026 at 10:40:27PM +0100, Thorsten Blum wrote:
> > The patch has been reviewed and acked for quite some time. Bjorn offered
> > to take it via the PCI tree at the end of October, pending an ack from
> > one of the x86 maintainers, but there hasn't been any further feedback.
>
> Why, because after sifting through all that gibberish in the commit message,
> it is basically telling me that some mac laptops have trouble with Linux?
v1 (submitted on August 7) didn't mention the iMacs as examples because
this bug may also affect other early quirks.
Lukas then asked for an example, which is why I added both iMacs to the
commit message in v2 (submitted on August 16, with no code changes).
> And because of this we need to stop the presses and take your patch
> immediately?
I never suggested the patch had to be taken immediately. And 3+ months
doesn't seem particularly immediate to me for a bug either.
I resent the patch twice (September 16 and November 6) and pinged once
(October 3), which should be well within the community guidelines:
https://www.kernel.org/doc/html/latest/process/submitting-patches.html
next prev parent reply other threads:[~2026-11-22 1:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 0:43 [PATCH RESEND v2] x86/early-quirks: Scan all functions in early_pci_scan_bus() Thorsten Blum
2026-11-18 18:35 ` Thorsten Blum
2026-11-18 19:40 ` Dave Hansen
2026-11-18 21:40 ` Thorsten Blum
2026-11-18 22:21 ` Borislav Petkov
2026-11-19 0:30 ` Thorsten Blum
2026-11-19 0:56 ` Borislav Petkov
2026-11-22 1:56 ` Thorsten Blum [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-16 10:02 Thorsten Blum
2026-10-03 11:49 ` Thorsten Blum
2026-10-03 11:55 ` Dave Hansen
2026-10-05 0:35 ` Thorsten Blum
2026-10-12 18:28 ` Thorsten Blum
2026-10-25 8:07 ` Maciej W. Rozycki
2026-10-25 17:50 ` H. Peter Anvin
2026-10-26 18:37 ` Bjorn Helgaas
2026-10-27 10:40 ` Thorsten Blum
2026-10-27 20:13 ` Bjorn Helgaas
2026-10-27 20:31 ` Thorsten Blum
2026-10-27 20:59 ` Bjorn Helgaas
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=awJLsDWI0OgdWhph@kernel.org \
--to=blum@kernel.org \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jbarnes@hobbes.lan \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mingo@elte.hu \
--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