[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dedea008d546a2a29d3b604e9f4b0c0dec3ebac1.camel@sipsolutions.net>
Date: Tue, 25 Nov 2025 08:40:15 +0100
From: Johannes Berg <johannes@...solutions.net>
To: David Gow <davidgow@...gle.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>, Richard Weinberger
<richard@....at>, Anton Ivanov <anton.ivanov@...bridgegreys.com>, Miguel
Ojeda <ojeda@...nel.org>, Paolo 'Blaisorblade' Giarrusso
<blaisorblade@...oo.it>, Alice Ryhl <aliceryhl@...gle.com>,
linux-um@...ts.infradead.org, linux-kernel@...r.kernel.org,
rust-for-linux@...r.kernel.org
Subject: Re: [PATCH] arch: um: Don't rename vmap to kernel_vmap
On Tue, 2025-11-25 at 15:36 +0800, David Gow wrote:
> >
> > Or it's not that urgent because all this came up in -next now? I didn't
> > really see (or fully understand) all the build bug reports.
> >
>
> I'm happy for this to go in via any tree. (Worst-case, we could
> possibly take it via KUnit, though I'd rather not, as it's not really
> KUnit-related at all.)
>
> The issue has actually been around since probably 6.16 (c284d3e42338
> ("rust: drm: gem: Add GEM object abstraction")), but since it only
> applies to people building Rust graphics drivers against UML, which is
> not super common, it seems like it's only come up in randconfig builds
> so far.
Oh, interesting, OK. I guess then given that it's not super important
and how late we're in the game, I'll just throw it into the (relatively
small) pile we have for UML for -next. Given that we removed the pcap
driver in 6.11 (12b8e7e69aa7a) I guess we could even ask stable to take
it, but it's not even that important until someone wants to test the
rust DRM stuff in kunit or something :)
johannes
Powered by blists - more mailing lists