From: "Danilo Krummrich" <dakr@kernel.org>
To: "John Hubbard" <jhubbard@nvidia.com>
Cc: "rust-for-linux@vger.kernel.org" <rust-for-linux@vger.kernel.org>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Eliot Courtney" <ecourtney@nvidia.com>,
"Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
"Jason Gunthorpe" <jgg@nvidia.com>
Subject: Re: Nova developers: avoid nouveau mailing list until it is fixed
Date: Mon, 16 Mar 2026 23:36:01 +0100 [thread overview]
Message-ID: <DH4KDGXZF3XU.R94ADYNQ8RUW@kernel.org> (raw)
In-Reply-To: <bc2517c2-6772-4cbd-8fd7-6dbdcdd13eab@nvidia.com>
On Mon Mar 16, 2026 at 11:24 PM CET, John Hubbard wrote:
> And if "someone" wants to fire up a new "nova" list, that uses vger
> like the other kernel lists, I wouldn't complain. :)
I considered this already for other reasons, so let's just do it.
(We can't get a vger.kernel.org list anymore, but a lists.linux.dev one should
be no problem.)
I can send a request for nova-gpu@lists.linux.dev later today.
next prev parent reply other threads:[~2026-03-16 22:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 20:36 [PATCH v12 0/1] rust: interop: Add list module for C linked list interface Joel Fernandes
2026-03-06 20:36 ` [PATCH v12 1/1] " Joel Fernandes
2026-03-12 17:42 ` Danilo Krummrich
2026-03-12 19:15 ` Miguel Ojeda
2026-03-12 19:16 ` Miguel Ojeda
2026-03-16 18:47 ` Joel Fernandes
2026-03-12 19:20 ` Miguel Ojeda
2026-03-12 19:50 ` Danilo Krummrich
2026-03-16 17:57 ` Joel Fernandes
2026-03-16 22:24 ` Nova developers: avoid nouveau mailing list until it is fixed John Hubbard
2026-03-16 22:25 ` John Hubbard
2026-03-16 22:36 ` Danilo Krummrich [this message]
2026-03-16 22:37 ` John Hubbard
2026-03-16 18:54 ` [PATCH v12 1/1] rust: interop: Add list module for C linked list interface Joel Fernandes
2026-03-16 4:34 ` Alexandre Courbot
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=DH4KDGXZF3XU.R94ADYNQ8RUW@kernel.org \
--to=dakr@kernel.org \
--cc=acourbot@nvidia.com \
--cc=ecourtney@nvidia.com \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=konstantin@linuxfoundation.org \
--cc=nouveau@lists.freedesktop.org \
--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