[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72kY7oVOd+cWCQHrF=FXbgzLFyc40phMzzNZ_sJr+jYwnA@mail.gmail.com>
Date: Wed, 26 Mar 2025 00:22:46 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Andreas Hindborg <a.hindborg@...nel.org>
Cc: Miguel Ojeda <ojeda@...nel.org>, Anna-Maria Behnsen <anna-maria@...utronix.de>,
Frederic Weisbecker <frederic@...nel.org>, Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org,
"rust-for-linux@...r.kernel.org" <rust-for-linux@...r.kernel.org>
Subject: Re: [GIT PULL] Rust `hrtimer` support for v6.15
On Sat, Mar 22, 2025 at 12:16 PM Andreas Hindborg <a.hindborg@...nel.org> wrote:
>
> I'm sorry, but I have to do another update. My usual workflow missed a
> clippy warning because it depends on clippy warnings being treated as
> errors when building with `W=e`. I forgot that is not upstream yet.
No worries at all :)
All seems fine in the latest -next, which is also free from other
issues we had in the past few days.
I don't think you need to sign the message itself -- it is rare, but
it does not hurt.
Congratulations on your first PR!
Cheers,
Miguel
Powered by blists - more mailing lists