From: Borislav Petkov <bp@alien8.de>
To: Thorsten Blum <blum@kernel.org>
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: Wed, 18 Nov 2026 16:56:09 -0800 [thread overview]
Message-ID: <20261119005609.GDav5JKc8mhIet5j_a@fat_crate.local> (raw)
In-Reply-To: <av5DE5hlpItQzD8m@kernel.org>
On Thu, Nov 19, 2026 at 01:30:11AM +0100, Thorsten Blum wrote:
> My intention was to get this patch into linux-next for broader testing,
> not to bypass the maintainers. Apologies if it came across that way.
How about all those other things I asked? Any thoughts on them or does
everything remain business-as-usual - you keep hammering us with patches and
nothing really changes?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2026-11-19 0:56 UTC|newest]
Thread overview: 19+ 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
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 [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=20261119005609.GDav5JKc8mhIet5j_a@fat_crate.local \
--to=bp@alien8.de \
--cc=bhelgaas@google.com \
--cc=blum@kernel.org \
--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
all inboxes | Powered by JetHome®