Devicetree
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Markus Probst" <markus.probst@posteo.de>
Cc: devicetree@vger.kernel.org, rust-for-linux@vger.kernel.org,
	"Rob Herring" <robh@kernel.org>,
	"Saravana Kannan" <saravanak@google.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>
Subject: Re: [PATCH v2] rust: of: Add basic DeviceNode abstractions,
Date: Mon, 29 Sep 2025 16:31:49 +0200	[thread overview]
Message-ID: <DD5CV7ZXZDTA.26QKFT8OJO6SN@kernel.org> (raw)
In-Reply-To: <09c855b24873ba71b1c1e968d0b6d0c010843699.camel@posteo.de>

On Mon Sep 29, 2025 at 4:00 PM CEST, Markus Probst wrote:
> Add a safe wrapper arround `struct device_node`, which is capable of:
>
> * reading string, u32 and bool properties
>
> * iterating over children
>
> Signed-off-by: Markus Probst <markus.probst@posteo.de>

Can you please expand on the commit message a bit? What's the motivation? Why
can't you use device/fwnode properties instead?

Also, the patch seems mangled by your mail client, the corresponding MTA, etc.
Please have a look into fixing this up. You can also try to send a patch to
yourself first and see if it still applies for this purpose.

Thanks,
Danilo

  reply	other threads:[~2025-09-29 14:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-29 14:00 [PATCH v2] rust: of: Add basic DeviceNode abstractions, Markus Probst
2025-09-29 14:31 ` Danilo Krummrich [this message]
2025-09-29 14:57   ` Markus Probst

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=DD5CV7ZXZDTA.26QKFT8OJO6SN@kernel.org \
    --to=dakr@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gary@garyguo.net \
    --cc=lossin@kernel.org \
    --cc=markus.probst@posteo.de \
    --cc=ojeda@kernel.org \
    --cc=robh@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=saravanak@google.com \
    --cc=tmgross@umich.edu \
    /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