linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
	linux-i2c@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [GIT PULL] i2c: tegra: Changes for v5.8-rc1
Date: Tue, 19 May 2020 18:08:35 +0200	[thread overview]
Message-ID: <20200519160835.GC2113674@ulmo> (raw)
In-Reply-To: <314a292e-bcd9-bb30-4067-71dc7cc399d6@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1632 bytes --]

On Sat, May 16, 2020 at 10:45:32AM +0300, Dmitry Osipenko wrote:
> 15.05.2020 17:39, Thierry Reding пишет:
> > Hi,
> > 
> > The following changes since commit 0e698dfa282211e414076f9dc7e83c1c288314fd:
> > 
> >   Linux 5.7-rc4 (2020-05-03 14:56:04 -0700)
> > 
> > are available in the Git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/for-5.8-i2c
> > 
> > for you to fetch changes up to c73178b93754edd8449dccd3faf05baafd4d3f0e:
> > 
> >   i2c: tegra: Add support for the VI I2C on Tegra210 (2020-05-12 22:47:52 +0200)
> > 
> > Thanks,
> > Thierry
> > 
> > ----------------------------------------------------------------
> > i2c: tegra: Changes for v5.8-rc1
> > 
> > This includes a few improvements to make the Tegra I2C controller behave
> > properly on suspend/resume, does a bit of cleanup and adds support for
> > the VI-variant of the I2C controller that is used primarily for video
> > capture purposes.
> > 
> > ----------------------------------------------------------------
> > Dmitry Osipenko (2):
> >       i2c: tegra: Better handle case where CPU0 is busy for a long time
> >       i2c: tegra: Synchronize DMA before termination
> > 
> > Thierry Reding (5):
> >       Revert "i2c: tegra: Fix suspending in active runtime PM state"
> 
> >       i2c: tegra: Restore pinmux on system resume
> 
> In general this series is good to me, although I have some concerns
> about this patch. Could you please answer the review comments?

Sorry, those had been burried under too much email. I've answered your
questions now.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-05-19 16:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 14:39 [GIT PULL] i2c: tegra: Changes for v5.8-rc1 Thierry Reding
2020-05-16  7:45 ` Dmitry Osipenko
2020-05-19 16:08   ` Thierry Reding [this message]
2020-05-20  2:19     ` Dmitry Osipenko
2020-05-20 10:51       ` Thierry Reding
2020-05-21 16:02         ` Dmitry Osipenko
2020-05-20 13:40 ` 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=20200519160835.GC2113674@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=digetx@gmail.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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).