From: Mark Brown <broonie@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>,
Gary Guo <gary@garyguo.net>, Boqun Feng <boqun@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Bert Karwatzki <spasswolf@web.de>, Harry Yoo <harry@kernel.org>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
Alice Ryhl <aliceryhl@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
rust-for-linux@vger.kernel.org, Miguel Ojeda <ojeda@kernel.org>
Subject: Re: rust compile failure in next-20260730
Date: Wed, 5 Aug 2026 17:31:23 +0100 [thread overview]
Message-ID: <49305296-b2e5-4e59-befd-50fe85bf59ff@sirena.org.uk> (raw)
In-Reply-To: <CANiq72=Y1eVO5F0j4NXbnUzVvEnDGg0evAkeiE9hd-7hkeVr7A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
On Wed, Aug 05, 2026 at 06:24:03PM +0200, Miguel Ojeda wrote:
> I don't see it in next-20260805 -- Mark, could we please get the last
> diff hunk from:
> https://lore.kernel.org/all/11a8bf75-8fc1-4d32-a350-6bf8156dd8ab@kernel.org/
> applied tomorrow in the char-misc-next merge? i.e.
> - rcu: Opaque<bindings::callback_head>,
> + rcu: Opaque<bindings::kvfree_rcu_head>,
> in `rust/kernel/sync/poll.rs`.
Could someone please send me the exact merge fixup you want applying as
a patch, together with a description of which merge you want it applying
to (or at least a description of the two trees affected so I can work it
out)? That's going to be less error prone...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-08-05 16:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 12:28 rust compile failure in next-20260730 Bert Karwatzki
2026-07-31 13:19 ` Thorsten Leemhuis
2026-07-31 13:48 ` Luna Jernberg
2026-07-31 19:25 ` Nathan Chancellor
2026-08-03 13:57 ` Gary Guo
2026-08-03 14:23 ` Boqun Feng
2026-08-03 15:10 ` Vlastimil Babka (SUSE)
2026-08-03 15:32 ` Gary Guo
2026-08-03 21:04 ` Vlastimil Babka (SUSE)
2026-08-04 10:10 ` Gary Guo
2026-08-04 10:35 ` Vlastimil Babka (SUSE)
2026-08-05 16:24 ` Miguel Ojeda
2026-08-05 16:30 ` Vlastimil Babka (SUSE)
2026-08-05 16:31 ` Mark Brown [this message]
2026-08-06 5:52 ` Harry Yoo
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=49305296-b2e5-4e59-befd-50fe85bf59ff@sirena.org.uk \
--to=broonie@kernel.org \
--cc=aliceryhl@google.com \
--cc=boqun@kernel.org \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=harry@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=spasswolf@web.de \
--cc=vbabka@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