From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Andi Shyti <andi.shyti@kernel.org>,
Akhil R <akhilrajeev@nvidia.com>,
conor+dt@kernel.org, devicetree@vger.kernel.org,
digetx@gmail.com, jonathanh@nvidia.com, krzk+dt@kernel.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, ldewangan@nvidia.com,
robh@kernel.org
Subject: Re: [PATCH RESEND 0/2] i2c: tegra: Add Tegra256 I2C controller support
Date: Tue, 9 Sep 2025 19:16:13 +0200 [thread overview]
Message-ID: <aMBg3Z2OHkn2xWZ6@ninjato> (raw)
In-Reply-To: <22ucj42wvcqr5trsv75hbb6uj4y5zhjigs46w7mxtckisodcr5@77pgwttvycpl>
[-- Attachment #1: Type: text/plain, Size: 218 bytes --]
> Do you want me to pick up the DT bindings patch? There's currently no DT
> files that require this, so taking both through the I2C tree is fine,
> but either way works for me.
Agreed, this should be I2C material.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-09-09 17:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 4:33 [PATCH RESEND 0/2] i2c: tegra: Add Tegra256 I2C controller support Akhil R
2025-08-18 4:33 ` [PATCH RESEND 1/2] dt-bindings: i2c: nvidia,tegra20-i2c: Add Tegra256 I2C compatible Akhil R
2025-09-12 22:33 ` Wolfram Sang
2025-08-18 4:33 ` [PATCH RESEND 2/2] i2c: tegra: Add Tegra256 support Akhil R
2025-09-12 22:33 ` Wolfram Sang
2025-10-07 14:50 ` Jon Hunter
2025-10-08 5:35 ` Akhil R
2025-10-08 9:33 ` Jon Hunter
2025-10-08 9:52 ` Jon Hunter
2025-10-08 10:17 ` Akhil R
2025-08-29 10:04 ` [PATCH RESEND 0/2] i2c: tegra: Add Tegra256 I2C controller support Akhil R
2025-09-09 15:01 ` Thierry Reding
2025-09-09 17:16 ` 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=aMBg3Z2OHkn2xWZ6@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=akhilrajeev@nvidia.com \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=ldewangan@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@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