From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Thierry Reding <treding@nvidia.com>
Cc: Mark Brown <broonie@kernel.org>, Wolfram Sang <wsa@kernel.org>,
Akhil R <akhilrajeev@nvidia.com>,
Kartik Rajput <kkartik@nvidia.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the i2c tree with the arm-soc tree
Date: Wed, 17 Sep 2025 23:14:45 +0200 [thread overview]
Message-ID: <aMskxYrDxyzXPsBy@shikoro> (raw)
In-Reply-To: <ofp27qiwsw7jj5ne3y7kp2lpycwg37bvhswidwe6jfazs2czzp@76gzsofmliyc>
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
Hi Thierry,
> Note also that I only applied the DT bindings patch from the v6 series
> because it was already acked by device tree maintainers and there have
> not been any objections to the DT bits, nor are they relevant to the
> driver changes still being reviewed.
May I suggest then to send the DT bindings patch seperately next time?
We can apply it earlier then, so you can continue your work. I prefer to
take binding patches via the I2C tree so I can chime in if necessary and
also to keep the merge conflicts low.
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-09-17 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 17:50 linux-next: manual merge of the i2c tree with the arm-soc tree Mark Brown
2025-09-15 21:04 ` Wolfram Sang
2025-09-15 22:13 ` Mark Brown
2025-09-16 21:46 ` Thierry Reding
2025-09-17 21:14 ` Wolfram Sang [this message]
2025-09-22 12:03 ` Thierry Reding
-- strict thread matches above, loose matches on Subject: below --
2021-08-18 0:08 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=aMskxYrDxyzXPsBy@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=akhilrajeev@nvidia.com \
--cc=broonie@kernel.org \
--cc=kkartik@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=treding@nvidia.com \
--cc=wsa@kernel.org \
/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