From: "Danilo Krummrich" <dakr@kernel.org>
To: "FUJITA Tomonori" <fujita.tomonori@gmail.com>
Cc: <boqun.feng@gmail.com>, <gregkh@linuxfoundation.org>,
<ojeda@kernel.org>, <rafael@kernel.org>, <a.hindborg@kernel.org>,
<aliceryhl@google.com>, <bjorn3_gh@protonmail.com>,
<gary@garyguo.net>, <lossin@kernel.org>,
<rust-for-linux@vger.kernel.org>, <tmgross@umich.edu>
Subject: Re: [PATCH v1] rust: debugfs: Use kernel Atomic type in docs example
Date: Mon, 19 Jan 2026 14:51:11 +0100 [thread overview]
Message-ID: <DFSM54IDHL4O.235Q8YSZDU2N3@kernel.org> (raw)
In-Reply-To: <20260119.224942.2031351100749299829.fujita.tomonori@gmail.com>
On Mon Jan 19, 2026 at 2:49 PM CET, FUJITA Tomonori wrote:
> On Tue, 2 Dec 2025 17:36:44 -0800
> Boqun Feng <boqun.feng@gmail.com> wrote:
>
>> On Wed, Dec 03, 2025 at 09:04:11AM +0900, FUJITA Tomonori wrote:
>>> Switch the read_callback_file() documentation example from
>>> core::sync::atomic::AtomicU32 to the kernel's Atomic because Rust
>>> native atomics are not allowed to use in kernel.
>>>
>>> Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
>>
>> Reviewed-by: Boqun Feng <boqun.feng@gmail.com>
>
> Can this patch be merged via the driver-core tree, or should it go
> through a different tree?
Thanks for the ping, I will pick it up soon.
- Danilo
next prev parent reply other threads:[~2026-01-19 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 0:04 [PATCH v1] rust: debugfs: Use kernel Atomic type in docs example FUJITA Tomonori
2025-12-03 1:36 ` Boqun Feng
2026-01-19 13:49 ` FUJITA Tomonori
2026-01-19 13:51 ` Danilo Krummrich [this message]
2026-01-19 14:07 ` 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=DFSM54IDHL4O.235Q8YSZDU2N3@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--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