From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Rob Herring <robh@kernel.org>
Cc: devicetree-spec@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH dt-schema] schemas: i2c: Allow '-' in 'i2c-.*' node names
Date: Wed, 21 May 2025 11:35:26 +0200 [thread overview]
Message-ID: <aC2eXoAyATuusWX4@shikoro> (raw)
In-Reply-To: <CAL_JsqL6CdmrCTbvbFEUjhbd+yDtd9Jf9r+OcV0imcoB117iAg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 330 bytes --]
> The hardest part is doing a dtb->dts pass and comparing those before
> and after to make sure you haven't combined or split nodes.
I'll pass. I'll fix the boards I have actually access to, but the above
task sounds no fun to me.
That being said: is my original patch here rejected? We allow only one
'-' for i2c node names?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-05-21 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 18:43 [PATCH dt-schema] schemas: i2c: Allow '-' in 'i2c-.*' node names Wolfram Sang
2025-05-20 1:18 ` Rob Herring
2025-05-20 9:25 ` Wolfram Sang
2025-05-20 12:29 ` Rob Herring
2025-05-21 9:35 ` 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=aC2eXoAyATuusWX4@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=devicetree-spec@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=robh@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