From: Herve Codina <herve.codina@bootlin.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree-spec@vger.kernel.org,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Herve Codina <herve.codina@bootlin.com>
Subject: [PATCH 1/2] schemas: i2c: Avoid extra characters in i2c nodename pattern
Date: Tue, 1 Apr 2025 10:10:39 +0200 [thread overview]
Message-ID: <20250401081041.114333-2-herve.codina@bootlin.com> (raw)
In-Reply-To: <20250401081041.114333-1-herve.codina@bootlin.com>
Current nodename pattern doesn't limit the end of name for an i2c node.
It can match 'i2c@10-foo'.
In order to avoid matching to an incorrect name, avoid any extra
characters in nodename pattern.
Signed-off-by: Herve Codina <herve.codina@bootlin.com>
---
dtschema/schemas/i2c/i2c-controller.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dtschema/schemas/i2c/i2c-controller.yaml b/dtschema/schemas/i2c/i2c-controller.yaml
index 487e669..018d266 100644
--- a/dtschema/schemas/i2c/i2c-controller.yaml
+++ b/dtschema/schemas/i2c/i2c-controller.yaml
@@ -14,7 +14,7 @@ maintainers:
properties:
$nodename:
- pattern: "^i2c(@.*)?"
+ pattern: "^i2c(@.*)?$"
i2c-bus:
type: object
--
2.49.0
next prev parent reply other threads:[~2025-04-01 8:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 8:10 [PATCH 0/2] i2c: Introduce I2C bus extensions Herve Codina
2025-04-01 8:10 ` Herve Codina [this message]
2025-04-01 14:10 ` [PATCH 1/2] schemas: i2c: Avoid extra characters in i2c nodename pattern Rob Herring
2025-04-01 8:10 ` [PATCH 2/2] schemas: i2c: Introduce I2C bus extensions Herve Codina
2025-04-01 14:03 ` Rob Herring
2025-04-02 8:21 ` Herve Codina
2025-04-17 15:38 ` Herve Codina
2025-04-29 18:04 ` Ayush Singh
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=20250401081041.114333-2-herve.codina@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree-spec@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wsa+renesas@sang-engineering.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