From: Mark Brown <broonie@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Miguel Ojeda <ojeda@kernel.org>,
Danilo Krummrich <dakr@kernel.org>, Gary Guo <gary@garyguo.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the rust tree with the origin tree
Date: Mon, 6 Apr 2026 14:14:58 +0100 [thread overview]
Message-ID: <85d22f65-aeb7-4152-9d19-3e68f291372d@sirena.org.uk> (raw)
In-Reply-To: <CANiq72n-FHNbRK2-N0dJ4DiYvKZ2oifuhOn-e7zvHAJjwQykKg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 447 bytes --]
On Mon, Apr 06, 2026 at 03:11:57PM +0200, Miguel Ojeda wrote:
> On Mon, Apr 6, 2026 at 3:02 PM Mark Brown <broonie@kernel.org> wrote:
> >
> > +// Stable since Rust 1.84.0.
> > +#![feature(strict_provenance)]
> > +//
>
> This one can (should) be removed, since it is < 1.85.0 which is the
> new minimum (i.e. already by the time that commits happens) -- please
> see my resolution at:
I'll update that if I get another conflict.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-04-06 13:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 13:02 Mark Brown
2026-04-06 13:11 ` Miguel Ojeda
2026-04-06 13:14 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-06 13:13 Mark Brown
2026-04-06 13:16 ` Miguel Ojeda
2026-04-06 13:12 Mark Brown
2026-04-06 13:15 ` Miguel Ojeda
2026-04-03 12:35 Mark Brown
2026-04-03 12:53 ` Miguel Ojeda
2026-03-30 13:17 Mark Brown
2026-03-30 13:26 ` Gary Guo
2026-03-30 13:30 ` Miguel Ojeda
2026-03-30 13:32 ` Miguel Ojeda
2021-12-13 22:33 broonie
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=85d22f65-aeb7-4152-9d19-3e68f291372d@sirena.org.uk \
--to=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.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
all inboxes | Powered by JetHome®