From: Danilo Krummrich <dakr@kernel.org>
To: Ayush Singh <ayush@beagleboard.org>
Cc: "Jason Kridner" <jkridner@beagleboard.org>,
"Deepak Khatri" <lorforlinux@beagleboard.org>,
"Robert Nelson" <robertcnelson@beagleboard.org>,
"Dhruva Gole" <d-gole@ti.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" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] rust: kernel: device: Add devm_of_platform_populate/depopulate
Date: Tue, 29 Apr 2025 16:31:52 +0200 [thread overview]
Message-ID: <aBDi2LE3O1rIsGqn@pollux> (raw)
In-Reply-To: <20250429-rust-of-populate-v2-1-0ad329d121c5@beagleboard.org>
On Tue, Apr 29, 2025 at 05:09:26PM +0530, Ayush Singh wrote:
> + /// Remove devices populated from device tree
> + pub fn devm_of_platform_depopulate(&self) {
> + // SAFETY: self is valid bound Device reference
> + unsafe { bindings::devm_of_platform_depopulate(self.as_raw()) }
> + }
> +}
One additional question regarding devm_of_platform_depopulate(). This function
is only used once throughout the whole kernel (in [1]), and at a first glance
the usage there seems unnecessary.
In your upcoming driver you call devm_of_platform_depopulate() from a fallible
path [2].
So, I think we should change devm_of_platform_depopulate() to return an error
instead of WARN(ret).
If [1] needs it for some subtle reason I don't see, then I think we can still
call it from there as
WARN(devm_of_platform_depopulate())
[1] https://elixir.bootlin.com/linux/v6.15-rc4/source/drivers/soc/ti/pruss.c#L558
[2] https://github.com/Ayush1325/linux/commit/cdb1322b7166532445c54b601ad0a252866e574d#diff-7b9e3179e36732d5f3a681034d70c2fda4ff57745c79ad4a656f328c91e54b77R71
next prev parent reply other threads:[~2025-04-29 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 11:39 [PATCH v2] rust: kernel: device: Add devm_of_platform_populate/depopulate Ayush Singh
2025-04-29 12:10 ` Miguel Ojeda
2025-04-29 13:53 ` Danilo Krummrich
2025-04-29 14:31 ` Danilo Krummrich [this message]
2025-04-29 14:37 ` Greg Kroah-Hartman
2025-04-29 14:44 ` Danilo Krummrich
2025-04-29 14:57 ` Greg Kroah-Hartman
2025-04-29 16:07 ` Ayush Singh
2025-04-29 16:39 ` Greg Kroah-Hartman
2025-04-29 16:56 ` Ayush Singh
2025-04-29 20:55 ` Miguel Ojeda
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=aBDi2LE3O1rIsGqn@pollux \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=ayush@beagleboard.org \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=d-gole@ti.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=jkridner@beagleboard.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorforlinux@beagleboard.org \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=robertcnelson@beagleboard.org \
--cc=rust-for-linux@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.