From: Andreas Hindborg <a.hindborg@kernel.org>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>
Cc: <alex.gaynor@gmail.com>, <ojeda@kernel.org>,
<aliceryhl@google.com>, <bjorn3_gh@protonmail.com>,
<boqun.feng@gmail.com>, <dakr@kernel.org>, <gary@garyguo.net>,
<lossin@kernel.org>, <rust-for-linux@vger.kernel.org>,
<tmgross@umich.edu>, <tamird@gmail.com>,
"FUJITA Tomonori" <fujita.tomonori@gmail.com>
Subject: Re: [PATCH v1] rust: time: Fix compile error in impl_has_hr_timer macro
Date: Tue, 10 Jun 2025 12:43:58 +0200 [thread overview]
Message-ID: <875xh33mhd.fsf@kernel.org> (raw)
In-Reply-To: <CANiq72n-+FKrWmbtwoKn1n90Mw+wyQJKUrGUa7opsuNYbts-tQ@mail.gmail.com> (Miguel Ojeda's message of "Tue, 10 Jun 2025 11:49:40 +0200")
"Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com> writes:
> On Tue, Jun 10, 2025 at 9:36 AM Andreas Hindborg <a.hindborg@kernel.org> wrote:
>>
>> Acked-by: Andreas Hindborg <a.hindborg@kernel.org>
>
> Thanks!
>
>> You want to take it directly in the rust fixes PR?
>
> Yeah, since it is a fix, or what do you mean?
Yes, I thought we might want to get it in for v6.16-rc2.
> I guess there is no rush given there is no in-tree user, so you could
> pick it in your -next one, but perhaps someone else wants to start
> using it in another branch?
Either way is fine, just let me know.
Best regards,
Andreas Hindborg
next prev parent reply other threads:[~2025-06-10 10:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 2:05 [PATCH v1] rust: time: Fix compile error in impl_has_hr_timer macro FUJITA Tomonori
2025-06-06 15:34 ` Miguel Ojeda
2025-06-06 21:36 ` FUJITA Tomonori
2025-06-07 10:19 ` Miguel Ojeda
2025-06-08 21:26 ` Miguel Ojeda
2025-06-10 7:36 ` Andreas Hindborg
2025-06-10 9:49 ` Miguel Ojeda
2025-06-10 10:43 ` Andreas Hindborg [this message]
2025-06-06 19:34 ` Benno Lossin
2025-06-10 19:30 ` 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=875xh33mhd.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=lossin@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@gmail.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 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.