Re: [PATCH v3 00/10] Make PCI's devres API more consistent

2024-03-01 Thread Philipp Stanner
On Thu, 2024-02-29 at 14:57 -0600, Bjorn Helgaas wrote: > On Thu, Feb 29, 2024 at 09:31:20AM +0100, Philipp Stanner wrote: > > @Bjorn: > > Hey Bjorn, are we good with this series? Any more wishes or > > suggestions? > > Sorry, haven't had a chance to go through it yet.  > > FWIW, I just tried

Re: [PATCH v3 00/10] Make PCI's devres API more consistent

2024-02-29 Thread Bjorn Helgaas
On Thu, Feb 29, 2024 at 09:31:20AM +0100, Philipp Stanner wrote: > @Bjorn: > Hey Bjorn, are we good with this series? Any more wishes or > suggestions? Sorry, haven't had a chance to go through it yet. FWIW, I just tried to apply these on top of pci/devres, but it failed here: Applying:

Re: [PATCH v3 00/10] Make PCI's devres API more consistent

2024-02-29 Thread Philipp Stanner
@Bjorn: Hey Bjorn, are we good with this series? Any more wishes or suggestions? P. On Tue, 2024-02-06 at 14:39 +0100, Philipp Stanner wrote: > Changes in v3: >   - Use the term "PCI devres API" in some forgotten places. >   - Fix more grammar errors in patch #3. >   - Remove the comment

[PATCH v3 00/10] Make PCI's devres API more consistent

2024-02-06 Thread Philipp Stanner
Changes in v3: - Use the term "PCI devres API" in some forgotten places. - Fix more grammar errors in patch #3. - Remove the comment advising to call (the outdated) pcim_intx() in pci.c - Rename __pcim_request_region_range() flags-field "exclusive" to "req_flags", since this is what