From: <Tharunkumar.Pasumarthi@microchip.com>
To: <linux-i2c@vger.kernel.org>, <christophe.jaillet@wanadoo.fr>,
<linux-kernel@vger.kernel.org>, <wsa@kernel.org>
Cc: <krzk@kernel.org>, <andriy.shevchenko@linux.intel.com>,
<robh@kernel.org>, <jarkko.nikula@linux.intel.com>,
<sven@svenpeter.dev>, <jsd@semihalf.com>,
<semen.protsenko@linaro.org>, <rafal@milecki.pl>,
<UNGLinuxDriver@microchip.com>, <olof@lixom.net>, <arnd@arndb.de>
Subject: Re: [PATCH RFC i2c-master] i2c: microchip: pci1xxxx: Add driver for I2C host controller in multifunction endpoint of pci1xxxx switch
Date: Tue, 30 Aug 2022 14:25:10 +0000 [thread overview]
Message-ID: <929334dcf3b182035e9685f69e5f45836938b125.camel@microchip.com> (raw)
In-Reply-To: <667f1658-cf29-6b19-fd57-0c62f625d536@wanadoo.fr>
On Tue, 2022-08-23 at 13:48 +0200, Christophe JAILLET wrote:
> > +
> > +err_free_region:
> > + pci_free_irq_vectors(pdev);
>
> Should this also be part of the .remove function?
pci_free_irq_vectors API is not needed since pcim_enable_device API is used. I
will remove 'pci_free_irq_vectors' in all the places in upcoming version of the
patch.
Thanks,
Tharun Kumar P
next prev parent reply other threads:[~2022-08-30 14:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 14:56 [PATCH RFC i2c-master] i2c: microchip: pci1xxxx: Add driver for I2C host controller in multifunction endpoint of pci1xxxx switch Tharun Kumar P
2022-08-23 10:31 ` Krzysztof Kozlowski
2022-08-24 13:48 ` Tharunkumar.Pasumarthi
2022-08-30 14:21 ` Tharunkumar.Pasumarthi
2022-08-23 11:48 ` Christophe JAILLET
2022-08-24 13:52 ` Tharunkumar.Pasumarthi
2022-08-30 14:25 ` Tharunkumar.Pasumarthi [this message]
2022-08-23 15:05 ` Andy Shevchenko
2022-08-24 14:38 ` Tharunkumar.Pasumarthi
2022-08-24 18:31 ` Andy Shevchenko
2022-08-25 13:15 ` Tharunkumar.Pasumarthi
2022-08-25 14:22 ` Andy Shevchenko
2022-08-26 4:00 ` Tharunkumar.Pasumarthi
2022-08-26 13:03 ` Tharunkumar.Pasumarthi
2022-08-26 15:37 ` Andy Shevchenko
2022-08-29 3:00 ` Tharunkumar.Pasumarthi
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=929334dcf3b182035e9685f69e5f45836938b125.camel@microchip.com \
--to=tharunkumar.pasumarthi@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=christophe.jaillet@wanadoo.fr \
--cc=jarkko.nikula@linux.intel.com \
--cc=jsd@semihalf.com \
--cc=krzk@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=sven@svenpeter.dev \
--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