From: "Benno Lossin" <lossin@kernel.org>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
"Gary Guo" <gary@garyguo.net>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Fiona Behrens" <me@kloenk.dev>,
"Christian Schrefl" <chrisi.schrefl@gmail.com>,
"Tamir Duberstein" <tamird@gmail.com>,
"Alban Kurti" <kurti@invicto.ai>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [GIT PULL] Rust pin-init for v7.0
Date: Wed, 28 Jan 2026 18:05:47 +0100 [thread overview]
Message-ID: <DG0DX0WOGQ4S.35RB35H32AS3N@kernel.org> (raw)
In-Reply-To: <CANiq72mb0s4_gAW2wOQ=JBcpzkLg5tHA1TQ01V9WoFUqv7Pi7A@mail.gmail.com>
On Wed Jan 28, 2026 at 4:03 PM CET, Miguel Ojeda wrote:
> On Thu, Jan 22, 2026 at 11:10 AM Benno Lossin <lossin@kernel.org> wrote:
>>
>> Hi Miguel,
>>
>> Lot's of changes in this one, mainly the `syn` rewrite, but also some
>> smaller changes such as removing the `try_` versions of the macros in
>> pin-init (the kernel still declares its own).
>>
>> All commits have been in linux-next since Monday.
>>
>> The first commit in my tree is also in the `syn` patch series from Gary
>> [1], to avoid problems it should be merged after this tag. There also is
>> a "phantom conflict" with 74e15ac34b098 ("scripts:
>> generate_rust_analyzer: Add pin_init_internal deps") in rust-fixes,
>> which you already saw in linux-next [2]. Otherwise no conflicts
>> expected.
>>
>> Please pull for v7.0 -- thanks!
>
> Merged into `rust-next` and Gary's series (without his first patch)
> right after that -- thank you!
>
> By the way, in the PR message, it would be nice if you could use the
> imperative, since that is nowadays the style maintainers should use
> for PRs.
Will do!
> I reworded it a bit to conform, please take a look.
Changes look good to me.
Cheers,
Benno
prev parent reply other threads:[~2026-01-28 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 10:10 [GIT PULL] Rust pin-init for v7.0 Benno Lossin
2026-01-28 15:03 ` Miguel Ojeda
2026-01-28 17:05 ` Benno Lossin [this message]
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=DG0DX0WOGQ4S.35RB35H32AS3N@kernel.org \
--to=lossin@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=chrisi.schrefl@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=kurti@invicto.ai \
--cc=linux-kernel@vger.kernel.org \
--cc=me@kloenk.dev \
--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.