From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: bus: renesas-bsc: allow additional properties
Date: Thu, 9 Oct 2025 20:34:29 +0200 [thread overview]
Message-ID: <aOgANZnOtkKTy4sO@shikoro> (raw)
In-Reply-To: <20251009071033.5378-2-wsa+renesas@sang-engineering.com>
[-- Attachment #1: Type: text/plain, Size: 177 bytes --]
> +patternProperties:
> + # All other properties should be child nodes with unit-address and 'reg'
> + "^.*@[0-9a-f]+$":
Per Rob's comment in another thread, '^.*' can go.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-10-09 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 7:08 [PATCH v2] dt-bindings: bus: renesas-bsc: allow additional properties Wolfram Sang
2025-10-09 7:19 ` Geert Uytterhoeven
2025-10-09 18:34 ` 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=aOgANZnOtkKTy4sO@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--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