From: Hans de Goede <hansg@kernel.org>
To: Andi Kleen <ak@linux.intel.com>, Lukas Wunner <lukas@wunner.de>
Cc: David Airlie <airlied@redhat.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Ben Hutchings <ben@decadent.org.uk>,
Joerg Roedel <joro@8bytes.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Ahmed Salem <x0rw3ll@gmail.com>, Borislav Petkov <bp@alien8.de>,
Hans de Goede <hdegoede@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
dri-devel@lists.freedesktop.org, iommu@lists.linux.dev,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v2] agp/amd64: Check AGP Capability before binding to unsupported devices
Date: Mon, 7 Jul 2025 14:53:32 +0200 [thread overview]
Message-ID: <4ef523a2-48b3-45e9-94da-7811e1bfae76@kernel.org> (raw)
In-Reply-To: <aGbaNd3qCK3WvAe-@tassilo>
Hi Andi,
On 3-Jul-25 21:29, Andi Kleen wrote:
>
> I suspect these days it would be also reasonable to drop it this old
> hack.
>
> If any of these old chipsets are still missing I would rather adds its
> PCI-ID.
>
> There will be certainly not any new unknown ones for these old CPUs.
Right, I plan to submit a patch to disable the probing of unsupported
devices by default. I'll likely even do so today.
But that is not entirely without a risk of regressions and atm this
is causing a regression (breaks flicker free boot) in 6.16-rc# .
So I think we should move forward with Lukas' fix dor 6.16 and then
my patch to disable probing of unsupported devices by default can
be merged into linux-next .
Regards,
Hans
next prev parent reply other threads:[~2025-07-07 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 15:15 [PATCH v2] agp/amd64: Check AGP Capability before binding to unsupported devices Lukas Wunner
2025-07-03 8:46 ` Hans de Goede
2025-07-03 19:29 ` Andi Kleen
2025-07-07 12:53 ` Hans de Goede [this message]
2025-07-07 13:58 ` Lukas Wunner
2025-07-17 23:40 ` 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=4ef523a2-48b3-45e9-94da-7811e1bfae76@kernel.org \
--to=hansg@kernel.org \
--cc=airlied@redhat.com \
--cc=ak@linux.intel.com \
--cc=ben@decadent.org.uk \
--cc=bp@alien8.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=helgaas@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=suravee.suthikulpanit@amd.com \
--cc=tglx@linutronix.de \
--cc=x0rw3ll@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.