From: Johannes Berg <johannes@sipsolutions.net>
To: David Gow <davidgow@google.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Miguel Ojeda <ojeda@kernel.org>,
Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>,
Alice Ryhl <aliceryhl@google.com>,
linux-um@lists.infradead.org, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH] arch: um: Don't rename vmap to kernel_vmap
Date: Tue, 25 Nov 2025 08:40:15 +0100 [thread overview]
Message-ID: <dedea008d546a2a29d3b604e9f4b0c0dec3ebac1.camel@sipsolutions.net> (raw)
In-Reply-To: <CABVgOSmAGahEaa71_fOT4Oo9Wg91X6rN+1_KgVVvVzmd4vuMCg@mail.gmail.com> (sfid-20251125_083645_823712_C74034DC)
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
next prev parent reply other threads:[~2025-11-25 7:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-22 8:32 [PATCH] arch: um: Don't rename vmap to kernel_vmap David Gow
2025-11-23 17:07 ` Miguel Ojeda
2025-11-24 7:49 ` Johannes Berg
2025-11-25 7:36 ` David Gow
2025-11-25 7:40 ` Johannes Berg [this message]
2025-11-25 9:17 ` David Gow
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=dedea008d546a2a29d3b604e9f4b0c0dec3ebac1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=aliceryhl@google.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=blaisorblade@yahoo.it \
--cc=davidgow@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=richard@nod.at \
--cc=rust-for-linux@vger.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;
as well as URLs for NNTP newsgroup(s).