linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Jon Hunter <jonathanh@nvidia.com>,
	linux-i2c@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 0/4] i2c: tegra: Add support for the VI I2C on Tegra210
Date: Tue, 12 May 2020 15:14:51 +0200	[thread overview]
Message-ID: <20200512131451.GD13516@ninjato> (raw)
In-Reply-To: <20200506191511.2791107-1-thierry.reding@gmail.com>

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

Hi Thierry,

> That said, I could also put this set of patches (except the DTS change)
> into the same branch I already have for Dmitry's patches (plus the fixes
> that we had discussed) and take it into linux-next and let it brew for a
> couple of days to get more testing and then send everything to you with
> a PR, say, sometime next week? How does that sound?

Well, it is already next week when you get my answer... Yes, sure this
is fine with me. Makes dependency handling and testing easier.

Kind regards,

   Wolfram


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

      parent reply	other threads:[~2020-05-12 13:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 19:15 [PATCH 0/4] i2c: tegra: Add support for the VI I2C on Tegra210 Thierry Reding
2020-05-06 19:15 ` [PATCH 1/4] dt-bindings: i2c: tegra: Document Tegra210 VI I2C Thierry Reding
2020-05-06 19:15 ` [PATCH 2/4] i2c: tegra: Use FIELD_PREP/FIELD_GET macros Thierry Reding
2020-05-06 19:15 ` [PATCH 3/4] i2c: tegra: Add support for the VI I2C on Tegra210 Thierry Reding
2020-05-06 19:15 ` [PATCH 4/4] arm64: tegra: Enable VI I2C on Jetson Nano Thierry Reding
2020-05-12 13:14 ` Wolfram Sang [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=20200512131451.GD13516@ninjato \
    --to=wsa@the-dreams.de \
    --cc=jonathanh@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.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).