From: <Tharunkumar.Pasumarthi@microchip.com>
To: <andriy.shevchenko@linux.intel.com>
Cc: <UNGLinuxDriver@microchip.com>, <wsa@kernel.org>,
<krzk@kernel.org>, <sven@svenpeter.dev>, <robh@kernel.org>,
<semen.protsenko@linaro.org>, <linux-kernel@vger.kernel.org>,
<jarkko.nikula@linux.intel.com>, <olof@lixom.net>,
<linux-i2c@vger.kernel.org>, <jsd@semihalf.com>, <arnd@arndb.de>,
<rafal@milecki.pl>
Subject: Re: [PATCH v5 i2c-master] i2c: microchip: pci1xxxx: Add driver for I2C host controller in multifunction endpoint of pci1xxxx switch
Date: Tue, 27 Sep 2022 03:03:01 +0000 [thread overview]
Message-ID: <8369deb67f979b25dad8a9cd51da8c846b2d76e9.camel@microchip.com> (raw)
In-Reply-To: <YzF55ckrtsNaxZUq@smile.fi.intel.com>
On Mon, 2022-09-26 at 13:07 +0300, Andy Shevchenko wrote:
> 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.
Okay Andy. I will address these issues in the upcoming version of the patch.
Thanks,
Tharun Kumar P
prev parent reply other threads:[~2022-09-27 3:11 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
2022-09-27 3:03 ` Tharunkumar.Pasumarthi [this message]
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=8369deb67f979b25dad8a9cd51da8c846b2d76e9.camel@microchip.com \
--to=tharunkumar.pasumarthi@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andriy.shevchenko@linux.intel.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=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