All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Boqun Feng <boqun@kernel.org>, Gary Guo <gary@garyguo.net>
Cc: 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
Subject: Re: rust compile failure in next-20260730
Date: Mon, 3 Aug 2026 17:10:17 +0200	[thread overview]
Message-ID: <7c39e6cb-0ccf-4a50-a853-0f6012b05044@kernel.org> (raw)
In-Reply-To: <anCkbMyUIscmAheK@tardis.local>

On 8/3/26 16:23, Boqun Feng wrote:
> On Mon, Aug 03, 2026 at 02:57:49PM +0100, Gary Guo wrote:
>> 
>> We could also unconditionally use `kvfree_rcu_head` here, and
>> add
>> 
>>     #[cfg(not(CONFIG_KVFREE_RCU_BATCHED))]
>>     pub type kvfree_rcu_head = callback_head;
>> 
>> to bindings.rs?
>> 
> 
> This option is currently not maintainable unless it becomes a
> maintainer-aware way to handle things like this.
> 
>> (Or even better, changing `#define` to `typedef` so bindgen takes care of
>> everything).
>> 
> 
> Yes, this is better IMO, but it's up to slab maintainers. :-)

Can you elaborate a bit please, how would that look like?

> Regards,
> Boqun
> 
>> Best,
>> Gary
>> 


  reply	other threads:[~2026-08-03 15:10 UTC|newest]

Thread overview: 11+ 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) [this message]
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)

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=7c39e6cb-0ccf-4a50-a853-0f6012b05044@kernel.org \
    --to=vbabka@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=nathan@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=spasswolf@web.de \
    /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.