From: Wolfram Sang <wsa@kernel.org>
To: Seth Heasley <seth.heasley@linux.intel.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Neil Horman <nhorman@tuxdriver.com>,
linux-i2c@vger.kernel.org, mario.posso.escobar@intel.com,
seth.heasley@intel.com
Subject: Re: [PATCH v1] i2c: ismt: Adding support for I2C_SMBUS_BLOCK_PROC_CALL
Date: Thu, 3 Dec 2020 21:21:31 +0100 [thread overview]
Message-ID: <20201203202131.GD3585@kunai> (raw)
In-Reply-To: <989a41d4e72610c8ddf36372e9a84de48f27c246.camel@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 671 bytes --]
On Thu, Dec 03, 2020 at 12:51:02AM -0800, Seth Heasley wrote:
> On Mon, 2020-11-16 at 15:32 +0000, Andy Shevchenko wrote:
> > From: Mario Alejandro Posso Escobar <mario.posso.escobar@intel.com>
> >
> > Expand the driver to support I2C_SMBUS_BLOCK_PROC_CALL since
> > HW supports it already.
> >
> > Co-developed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Signed-off-by: Mario Alejandro Posso Escobar
> > mario.posso.escobar@intel.com>
> Reviewed-by: Seth Heasley <seth.heasley@linux.intel.com>
Thanks! Applied to for-next again, not changing the tags this time.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-12-03 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201116153245.24083-1-andriy.shevchenko () linux ! intel ! com>
2020-12-03 8:51 ` [PATCH v1] i2c: ismt: Adding support for I2C_SMBUS_BLOCK_PROC_CALL Seth Heasley
2020-12-03 20:21 ` Wolfram Sang [this message]
2020-11-16 15:32 Andy Shevchenko
2020-12-02 15:45 ` Wolfram Sang
2020-12-02 16:00 ` Wolfram Sang
2020-12-02 16:24 ` Andy Shevchenko
2020-12-02 16:23 ` Andy Shevchenko
2020-12-02 16:25 ` Wolfram Sang
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=20201203202131.GD3585@kunai \
--to=wsa@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=mario.posso.escobar@intel.com \
--cc=nhorman@tuxdriver.com \
--cc=seth.heasley@intel.com \
--cc=seth.heasley@linux.intel.com \
/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).