From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Tharun Kumar P <tharunkumar.pasumarthi@microchip.com>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
wsa@kernel.org, krzk@kernel.org, jarkko.nikula@linux.intel.com,
robh@kernel.org, semen.protsenko@linaro.org, sven@svenpeter.dev,
jsd@semihalf.com, rafal@milecki.pl, olof@lixom.net,
arnd@arndb.de, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH v5 i2c-master] i2c: microchip: pci1xxxx: Add driver for I2C host controller in multifunction endpoint of pci1xxxx switch
Date: Mon, 26 Sep 2022 13:07:33 +0300 [thread overview]
Message-ID: <YzF55ckrtsNaxZUq@smile.fi.intel.com> (raw)
In-Reply-To: <20220926084654.2580827-1-tharunkumar.pasumarthi@microchip.com>
On Mon, Sep 26, 2022 at 02:16:54PM +0530, Tharun Kumar P wrote:
> Microchip pci1xxxx is an unmanaged PCIe3.1a Switch for Consumer,
> Industrial and Automotive applications. This switch has multiple
> downstream ports. In one of the Switch's Downstream port, there
> is a multifunction endpoint for peripherals which includes an I2C
> host controller. The I2C function in the endpoint operates at 100KHz,
> 400KHz and 1 MHz and has buffer depth of 128 bytes.
> This patch provides the I2C controller driver for the I2C function
> of the switch.
> ---
> V4 -> V5:
> 1. Removed autoprobe
> ---
> V3 -> V4:
> 1. Removed typecasting for fields of min_t
> 2. Replaced TRUE with true
> ---
> V2 -> V3:
> 1. Replaced SIMPLE_DEV_PM_OPS with DEFINE_SIMPLE_DEV_PM_OPS
> 2. Used devm_add_action API to avoid mixing devm and non-devm APIs
> ---
> RFC -> V2:
> 1. Removed pci_free_irq_vectors API in code since pcim_enable_device
> is used
> 2. Added pci1xxxx_i2c_shutdown API in failure case of
> pci_alloc_irq_vectors and devm_request_irq
> 3. Used devm variant of i2c_add_adapter
> 4. Resolved name collision and fixed styling issues in comments
> ---
> Signed-off-by: Tharun Kumar P <tharunkumar.pasumarthi@microchip.com>
There is no SoB tag in your message. Homework: to understand what went wrong
and fix in v6. Without SoB tag this may not be considered at all.
Also, if somebody gave you a tag (reviewers/maintainers) in the previous
versions, it's your as a contributor responsibility to bear those tags with
new versions in case there were no drastic functional changes. Otherwise
there is no point to review your changes.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-09-26 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 8:46 [PATCH v5 i2c-master] i2c: microchip: pci1xxxx: Add driver for I2C host controller in multifunction endpoint of pci1xxxx switch Tharun Kumar P
2022-09-26 10:07 ` Andy Shevchenko [this message]
2022-09-27 3:03 ` 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=YzF55ckrtsNaxZUq@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=arnd@arndb.de \
--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=tharunkumar.pasumarthi@microchip.com \
--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