From: Mark Brown <broonie@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Miguel Ojeda <ojeda@kernel.org>,
a.hindborg@kernel.org, aliceryhl@google.com,
bjorn3_gh@protonmail.com, boqun@kernel.org, dakr@kernel.org,
gary@garyguo.net, jhubbard@nvidia.com,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
lossin@kernel.org, rafael@kernel.org,
rust-for-linux@vger.kernel.org, tmgross@umich.edu,
viresh.kumar@linaro.org
Subject: Re: [RFC PATCH] rust: kbuild: support global per-version flags
Date: Mon, 16 Mar 2026 00:04:35 +0000 [thread overview]
Message-ID: <abdJE4BsrzGDTVZT@sirena.co.uk> (raw)
In-Reply-To: <CANiq72=drAtf3y_DZ-2o4jb6Az9J3Yj4QYwWnbRui4sm4AJD3Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 457 bytes --]
On Sun, Mar 15, 2026 at 10:21:04PM +0100, Miguel Ojeda wrote:
> (We will see how hard it is to keep all these versions clean in the
> medium-term future when more Rust is in the kernel: we have the MSRV
> bump cadence now with Debian Stable, so it may be doable, but worst
> case we could consider relaxing the policy to just the latest stable
> release and whatever linux-next runs).
At the minute whatever linux-next runs is whatever Debian stable has!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-03-16 0:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 19:53 [PATCH] rust: cpufreq: fix clippy::double_parens warning in Policy doctest John Hubbard
2026-03-04 20:06 ` Gary Guo
2026-03-04 20:07 ` John Hubbard
2026-03-04 20:28 ` Gary Guo
2026-03-04 20:32 ` John Hubbard
2026-03-04 20:39 ` Gary Guo
2026-03-04 21:13 ` John Hubbard
2026-03-05 12:31 ` Gary Guo
2026-03-06 12:36 ` Miguel Ojeda
2026-03-07 17:09 ` [RFC PATCH] rust: kbuild: support global per-version flags Miguel Ojeda
2026-03-15 21:21 ` Miguel Ojeda
2026-03-15 21:22 ` Miguel Ojeda
2026-03-16 0:04 ` Mark Brown [this message]
2026-03-16 4:49 ` Miguel Ojeda
2026-03-16 12:50 ` Mark Brown
2026-03-16 12:31 ` Danilo Krummrich
2026-03-16 13:42 ` Miguel Ojeda
2026-03-04 20:30 ` [PATCH] rust: cpufreq: fix clippy::double_parens warning in Policy doctest Gary Guo
2026-03-04 20:34 ` John Hubbard
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=abdJE4BsrzGDTVZT@sirena.co.uk \
--to=broonie@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=viresh.kumar@linaro.org \
/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