From: Dejin Zheng <zhengdejin5@gmail.com>
To: Robert Richter <rric@kernel.org>
Cc: corbet@lwn.net, jarkko.nikula@linux.intel.com,
andriy.shevchenko@linux.intel.com,
mika.westerberg@linux.intel.com, bhelgaas@google.com,
wsa@kernel.org, linux-doc@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/4] Introduce pcim_alloc_irq_vectors()
Date: Sun, 28 Feb 2021 19:17:25 +0800 [thread overview]
Message-ID: <20210228111725.GB1091046@nuc8i5> (raw)
In-Reply-To: <YDlKF1MP0p7l8vxb@rric.localdomain>
On Fri, Feb 26, 2021 at 08:20:55PM +0100, Robert Richter wrote:
> On 26.02.21 23:50:52, Dejin Zheng wrote:
> > Introduce pcim_alloc_irq_vectors(), a device-managed version of
> > pci_alloc_irq_vectors(), In some i2c drivers, If pcim_enable_device()
> > has been called before, then pci_alloc_irq_vectors() is actually a
> > device-managed function. It is used as a device-managed function, So
> > replace it with pcim_alloc_irq_vectors().
>
> For the whole series:
>
> Reviewed-by: Robert Richter <rric@kernel.org>
>
Robert, Thanks very much for your help!
> Thanks.
next prev parent reply other threads:[~2021-02-28 11:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 15:50 [PATCH v5 0/4] Introduce pcim_alloc_irq_vectors() Dejin Zheng
2021-02-26 15:50 ` [PATCH v5 1/4] PCI: " Dejin Zheng
2021-02-26 16:23 ` Andy Shevchenko
2021-02-28 11:16 ` Dejin Zheng
2021-03-23 22:47 ` Bjorn Helgaas
2021-05-05 16:27 ` Dejin Zheng
2021-06-02 8:51 ` Andy Shevchenko
2021-06-06 6:51 ` Dejin Zheng
2021-06-07 16:15 ` Bjorn Helgaas
2021-02-26 15:50 ` [PATCH v5 2/4] Documentation: devres: Add pcim_alloc_irq_vectors() Dejin Zheng
2021-02-26 15:50 ` [PATCH v5 3/4] i2c: designware: Use pcim_alloc_irq_vectors() to allocate IRQ vectors Dejin Zheng
2021-03-03 9:27 ` Jarkko Nikula
2021-02-26 15:50 ` [PATCH v5 4/4] i2c: thunderx: " Dejin Zheng
2021-02-26 19:19 ` Robert Richter
2021-02-26 19:20 ` [PATCH v5 0/4] Introduce pcim_alloc_irq_vectors() Robert Richter
2021-02-28 11:17 ` Dejin Zheng [this message]
2021-04-21 15:23 ` Andy Shevchenko
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=20210228111725.GB1091046@nuc8i5 \
--to=zhengdejin5@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rric@kernel.org \
--cc=wsa@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;
as well as URLs for NNTP newsgroup(s).