From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andi Shyti <andi.shyti@kernel•org>,
Colin Cross <ccross@android•com>, Olof Johansson <olof@lixom•net>,
Thierry Reding <treding@nvidia•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patches in the i2c-host tree
Date: Thu, 29 Aug 2024 10:05:04 +1000 [thread overview]
Message-ID: <20240829100504.091160a4@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 724 bytes --]
Hi all,
The following commits are also in the tegra tree as different commits
(but the same patches):
6302d41b3f7a ("dt-bindings: i2c: nvidia,tegra20-i2c: define power-domains top-level")
20b9b216daf8 ("dt-bindings: i2c: nvidia,tegra20-i2c: restrict also clocks in if:then:")
cd07e699cea9 ("dt-bindings: i2c: nvidia,tegra20-i2c: combine same if:then: clauses")
These are commits
fd16970c9d67 ("dt-bindings: i2c: nvidia,tegra20-i2c: Define power-domains top-level")
e0c7b7fcaf77 ("dt-bindings: i2c: nvidia,tegra20-i2c: Restrict also clocks in if:then:")
69a87db435a7 ("dt-bindings: i2c: nvidia,tegra20-i2c: Combine same if:then: clauses")
in the tegra tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-08-29 0:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 0:05 Stephen Rothwell [this message]
2024-09-06 21:47 ` linux-next: duplicate patches in the i2c-host tree Andi Shyti
-- strict thread matches above, loose matches on Subject: below --
2025-05-26 1:43 Stephen Rothwell
2025-06-10 23:03 ` Stephen Rothwell
2025-03-28 1:59 Stephen Rothwell
2025-04-02 5:19 ` Stephen Rothwell
2024-07-17 1:05 Stephen Rothwell
2024-06-04 1:20 Stephen Rothwell
2024-06-05 22:01 ` Stephen Rothwell
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=20240829100504.091160a4@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=andi.shyti@kernel$(echo .)org \
--cc=ccross@android$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=olof@lixom$(echo .)net \
--cc=treding@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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