From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: 1064094935@qq.com
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
"Danilo Krummrich" <dakr@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"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>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
pengfuyuan <pengfuyuan@kylinos.cn>
Subject: Re: [PATCH] rust: device: add platdata accessors
Date: Thu, 8 Jan 2026 08:57:23 +0100 [thread overview]
Message-ID: <2026010858-yonder-seventeen-361f@gregkh> (raw)
In-Reply-To: <tencent_C135881D822B4C6C12E841516893C774A805@qq.com>
On Thu, Jan 08, 2026 at 03:42:51PM +0800, 1064094935@qq.com wrote:
> From: pengfuyuan <pengfuyuan@kylinos.cn>
Please use your "real" name (you can use native character sets if
wanted.)
> Implement generic accessors for the platform data of a device.
>
> Platform data is typically set by platform code when creating the device
> and points to platform-specific data structures. The accessor provides
> type-safe access to this data without requiring unsafe code at the call
> site.
>
> The accessor is implemented for Device<Bound>, allowing drivers to access
> platform data during probe() and other device lifecycle callbacks. Unlike
> drvdata, platform data is managed by platform code and has a lifetime
> tied to the device itself.
Do you have a user for this? That would be good to see at the same time
here, we can't just add apis with no real users.
thanks,
greg k-h
next prev parent reply other threads:[~2026-01-08 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 7:42 [PATCH] rust: device: add platdata accessors 1064094935
2026-01-08 7:57 ` Greg Kroah-Hartman [this message]
[not found] ` <tencent_7AC5B74D51D3BA562D760B2E583115A06B07@qq.com>
2026-01-08 9:09 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2026-01-08 8:55 pengfuyuan
2026-01-08 9:09 ` Greg Kroah-Hartman
2026-01-08 10:46 ` Miguel Ojeda
2026-01-08 10:55 ` Miguel Ojeda
2026-01-08 10:55 ` Danilo Krummrich
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=2026010858-yonder-seventeen-361f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=1064094935@qq.com \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=pengfuyuan@kylinos.cn \
--cc=rafael@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox