From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>
Cc: Wolfram Sang <wsa@kernel.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Lori Hikichi <lori.hikichi@broadcom.com>,
Robert Richter <rrichter@marvell.com>,
Nishka Dasgupta <nishkadg.linux@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] add PEC support on slave side
Date: Wed, 22 Jul 2020 14:07:11 +0300 [thread overview]
Message-ID: <20200722110711.GY3703480@smile.fi.intel.com> (raw)
In-Reply-To: <20200717090155.10383-1-rayagonda.kokatanur@broadcom.com>
On Fri, Jul 17, 2020 at 02:31:53PM +0530, Rayagonda Kokatanur wrote:
> This patch set adds support for PEC on Slave side.
LGTM! FWIW,
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Changes from v1:
> -Address review comments from Andy Shevchenko
> Update commit message,
> Rewrite bcm_iproc_smbus_check_slave_pec() to remove local
> variable ret and type casting,
> Use positive condition.
>
> Rayagonda Kokatanur (2):
> i2c: add PEC error event
> i2c: iproc: add slave pec support
>
> drivers/i2c/busses/i2c-bcm-iproc.c | 49 +++++++++++++++++++++++++++---
> include/linux/i2c.h | 1 +
> 2 files changed, 46 insertions(+), 4 deletions(-)
>
> --
> 2.17.1
>
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2020-07-22 11:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 9:01 [PATCH v2 0/2] add PEC support on slave side Rayagonda Kokatanur
2020-07-17 9:01 ` [PATCH v2 1/2] i2c: add PEC error event Rayagonda Kokatanur
2020-07-23 20:16 ` Wolfram Sang
2020-07-24 9:22 ` Rayagonda Kokatanur
2020-07-17 9:01 ` [PATCH v2 2/2] i2c: iproc: add slave pec support Rayagonda Kokatanur
2020-07-23 20:20 ` Wolfram Sang
2020-07-24 9:37 ` Rayagonda Kokatanur
2020-07-22 11:07 ` Andy Shevchenko [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=20200722110711.GY3703480@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lori.hikichi@broadcom.com \
--cc=nishkadg.linux@gmail.com \
--cc=rayagonda.kokatanur@broadcom.com \
--cc=rjui@broadcom.com \
--cc=rrichter@marvell.com \
--cc=sbranden@broadcom.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;
as well as URLs for NNTP newsgroup(s).