[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72=uZLZ-ddUpyhPA8Kn-4DRKDgYT00wzc+zDRLOX3kv+dA@mail.gmail.com>
Date: Tue, 10 Jun 2025 12:21:38 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Boqun Feng <boqun.feng@...il.com>, "Rafael J. Wysocki" <rafael@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>, Peter Zijlstra <peterz@...radead.org>,
Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>, Vincent Guittot <vincent.guittot@...aro.org>,
Yury Norov <yury.norov@...il.com>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2 1/2] rust: cpu: Introduce CpuId abstraction
On Tue, Jun 10, 2025 at 12:14 PM Miguel Ojeda
<miguel.ojeda.sandonis@...il.com> wrote:
>
> But if you already did it, then please post it of course. (And maybe
> you just don't want "good first issues" for files, of course).
I meant "for your files", I meant, sorry.
i.e. it takes some work to guide people and help them get their patch
setup right etc., so it can be often quite more work than just doing
it oneself. So it is understandable if a maintainer doesn't want
those.
Cheers,
Miguel
Powered by blists - more mailing lists