linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Akhil R <akhilrajeev@nvidia.com>,
	christian.koenig@amd.com, jonathanh@nvidia.com,
	ldewangan@nvidia.com, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
	mperttunen@nvidia.com, p.zabel@pengutronix.de,
	sumit.semwal@linaro.org, thierry.reding@gmail.com
Subject: Re: [PATCH RESEND] i2c: tegra: Add SMBus block read function
Date: Wed, 16 Feb 2022 23:32:57 +0300	[thread overview]
Message-ID: <0497d0a9-c512-5472-c705-756c62ccccb3@gmail.com> (raw)
In-Reply-To: <20220210153603.61894-1-akhilrajeev@nvidia.com>

10.02.2022 18:36, Akhil R пишет:
> Emulate SMBus block read using ContinueXfer to read the length byte
> 
> Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
> ---
>  drivers/i2c/busses/i2c-tegra.c | 18 ++++++++++++++++--
>  1 file changed, 16 insertions(+), 2 deletions(-)

Reviewed-by: Dmitry Osipenko <digetx@gmail.com>

  parent reply	other threads:[~2022-02-16 20:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 15:36 [PATCH RESEND] i2c: tegra: Add SMBus block read function Akhil R
2022-02-10 20:25 ` Dmitry Osipenko
2022-02-11  9:11   ` Akhil R
2022-02-12 16:15     ` Dmitry Osipenko
2022-02-12 16:20       ` Dmitry Osipenko
2022-02-12 20:08         ` Dmitry Osipenko
2022-02-14  4:49           ` Akhil R
2022-02-15 21:33             ` Dmitry Osipenko
2022-02-16  3:54               ` Akhil R
2022-02-16 18:50                 ` Dmitry Osipenko
2022-02-16 20:32 ` Dmitry Osipenko [this message]
2022-02-25 13:03 ` Thierry Reding
2022-03-01 19:37 ` 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=0497d0a9-c512-5472-c705-756c62ccccb3@gmail.com \
    --to=digetx@gmail.com \
    --cc=akhilrajeev@nvidia.com \
    --cc=christian.koenig@amd.com \
    --cc=jonathanh@nvidia.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mperttunen@nvidia.com \
    --cc=p.zabel@pengutronix.de \
    --cc=sumit.semwal@linaro.org \
    --cc=thierry.reding@gmail.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).