public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Rob Herring <robh@kernel.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-renesas-soc@vger.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] dt-bindings: bus: renesas-bsc: allow additional properties
Date: Thu, 9 Oct 2025 08:43:15 +0200	[thread overview]
Message-ID: <aOdZgyPJLsZ5IjBS@shikoro> (raw)
In-Reply-To: <20251008224208.GA237448-robh@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 478 bytes --]

Hi Rob,

> There's always examples not to follow...

Sure. The good thing is that I could fix the bad examples, once I learnt
how to do it properly.

> The unit-address is the only part a bus schema should define. And there, 
> lowercase hex is standard unless you have distinct fields (e.g. chip 
> select and offset).

Okay, so, the proper pattern is: ""^.*@[0-9a-f]+$"" which is what most
busses are using. Will fix.

Thanks and happy hacking,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-10-09  6:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07  3:18 [PATCH] dt-bindings: bus: renesas-bsc: allow additional properties Wolfram Sang
2025-10-07  8:44 ` Geert Uytterhoeven
2025-10-07 21:30   ` Wolfram Sang
2025-10-08  9:56     ` Geert Uytterhoeven
2025-10-08 10:02       ` Wolfram Sang
2025-10-08 22:42         ` Rob Herring
2025-10-09  6:43           ` Wolfram Sang [this message]
2025-10-09 12:41             ` Rob Herring

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=aOdZgyPJLsZ5IjBS@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --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