From: Andreas Hindborg <a.hindborg@kernel.org>
To: "Timothy Garwood via B4 Relay"
<devnull+gtimothy-dev.protonmail.com@kernel.org>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
gtimothy-dev@protonmail.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>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] rust: HrTimerMode replacement with bitfield_options macro
Date: Wed, 29 Jan 2025 12:15:53 +0100 [thread overview]
Message-ID: <87jzadlvkm.fsf@kernel.org> (raw)
In-Reply-To: <20250128-bitfield-option-hrtimer-v1-1-31033d8e727f@protonmail.com> (Timothy Garwood via's message of "Tue, 28 Jan 2025 18:12:49 +0100")
"Timothy Garwood via B4 Relay" <devnull+gtimothy-dev.protonmail.com@kernel.org> writes:
> From: Timothy Garwood <gtimothy-dev@protonmail.com>
>
> replace the HrTimerMode enum with a bitfield wrapper built using the
> bitfield_options macro
>
> ---
> This patch provides an example of usage of the bitfield_options macro
> proposed in [1] as a replacement for the HrTimerMode enum introduced in
> [2].
> [1] is a RFC.
> This patch depends on both [1] and [2]
>
Very cool!
Since `hrtimer` is not upstream yet, if you get a non RFC version ready
before the next `hrtimer` spin, I can put a dependency on that if you
want?
Best regards,
Andreas Hindborg
next prev parent reply other threads:[~2025-01-29 11:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DS80qoWpf2_CoG8atMaPTH_9n1u1KOAzwhJfLmUVwwM9VgDvL4lsK-LCBbaJyCOUhNEZ9GicVz_x-J6Jcrm6dg==@protonmail.internalid>
2025-01-28 17:12 ` [PATCH RFC] rust: HrTimerMode replacement with bitfield_options macro Timothy Garwood via B4 Relay
2025-01-28 18:55 ` Miguel Ojeda
2025-01-28 21:23 ` Timothy Garwood
2025-01-28 22:00 ` Miguel Ojeda
2025-01-29 11:15 ` Andreas Hindborg [this message]
2025-01-29 14:17 ` Timothy Garwood
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=87jzadlvkm.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=devnull+gtimothy-dev.protonmail.com@kernel.org \
--cc=gary@garyguo.net \
--cc=gtimothy-dev@protonmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@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