From: Dave Hansen <dave.hansen@intel.com>
To: Thorsten Blum <blum@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Jesse Barnes <jbarnes@hobbes.lan>
Cc: 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: Wed, 18 Nov 2026 11:40:59 -0800 [thread overview]
Message-ID: <be480966-3b68-44f5-9afa-f88b3c203092@intel.com> (raw)
In-Reply-To: <av3v7KY64vjxDCk1@kernel.org>
On 11/18/26 10:35, Thorsten Blum wrote:
> Applied to blum/for-7.5 for linux-next testing.
>
> [1/1] x86/early-quirks: Scan all functions in early_pci_scan_bus()
> https://git.kernel.org/blum/c/83e3892f2aadca0123a3b7d452e3f39e74cf5126
>
> I plan to send it to Linus during the next merge window unless there are
> objections or the x86/PCI maintainers would prefer to take it.
I'm confused why you would even consider sending this to Linus. I'm
sorry but I'm not familiar with your work. Is this kind of thing you
normally send to Linus?
Oh, and I guess this is an objection. Please don't send this specific
fix upstream.
next prev parent reply other threads:[~2026-11-18 19:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 0:43 Thorsten Blum
2026-11-18 18:35 ` Thorsten Blum
2026-11-18 19:40 ` Dave Hansen [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=be480966-3b68-44f5-9afa-f88b3c203092@intel.com \
--to=dave.hansen@intel.com \
--cc=bhelgaas@google.com \
--cc=blum@kernel.org \
--cc=bp@alien8.de \
--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
all inboxes | Powered by JetHome®