Re: [PATCH 0/37] PCI/MSI: Enforce explicit IRQ vector management by removing devres auto-free

From
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date
2026-02-24 10:40:01
Also in
dmaengine, dri-devel, linux-arm-msm, linux-crypto, linux-cxl, linux-gpio, linux-i2c, linux-i3c, linux-iommu, linux-media, linux-mmc, linux-pci, linux-riscv, linux-serial, linux-spi, linux-usb, netdev, platform-driver-x86
Reply to
Philipp Stanner, 2026-02-24
On Tue, Feb 24, 2026 at 11:30:28AM +0100, Philipp Stanner wrote:
On Tue, 2026-02-24 at 11:12 +0200, Andy Shevchenko wrote:
quoted
On Tue, Feb 24, 2026 at 08:39:43AM +0100, Philipp Stanner wrote:
quoted
On Tue, 2026-02-24 at 13:14 +0900, Simon Richter wrote:
...
quoted
quoted
If I could design it from scratch I would probably try to tell users to
use the unmanaged versions instead of revoking the devres consequence.
+many.
hm?
I'm supporting you with many hands up (more than I possess)!
quoted
quoted
Devres is actually about your consequence always happening whenever the
driver unloads, for whatever reason.
I believe you meant "unbinds". The device<-->driver link can be broken
without unloading the driver.
Yes, thx for pointing that out. Greg KH AFAIK always calls it "driver
detach".
-- 
With Best Regards,
Andy Shevchenko

Thread (22 messages) 22 messages, 8 authors, last reply 2026-07-09
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help