[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YC/Sz/S1SXgsptq4@rric.localdomain>
Date: Fri, 19 Feb 2021 16:01:35 +0100
From: Robert Richter <rric@...nel.org>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Dejin Zheng <zhengdejin5@...il.com>, corbet@....net,
jarkko.nikula@...ux.intel.com, mika.westerberg@...ux.intel.com,
bhelgaas@...gle.com, wsa@...nel.org, linux-doc@...r.kernel.org,
linux-i2c@...r.kernel.org, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 1/4] PCI: Introduce pcim_alloc_irq_vectors()
On 19.02.21 16:48:57, Andy Shevchenko wrote:
> On Fri, Feb 19, 2021 at 03:40:05PM +0100, Robert Richter wrote:
> > On 18.02.21 23:04:55, Dejin Zheng wrote:
> > > Introduce pcim_alloc_irq_vectors(), a device-managed version of
> > > pci_alloc_irq_vectors(). Introducing this function can simplify
> > > the error handling path in many drivers.
> > >
> > > And use pci_free_irq_vectors() to replace some code in pcim_release(),
> > > they are equivalent, and no functional change. It is more explicit
> > > that pcim_alloc_irq_vectors() is a device-managed function.
>
> ...
>
> > If it is just about having a pcim-* counterpart why not just an inline
> > function like the one below.
>
> It's a good suggestion, thanks!
>
> Still we need to amend pcim_release() to explicitly show that we call
> pci_free_irq_vectors().
Fair enough. Thanks,
-Robert
Powered by blists - more mailing lists