From: "Danilo Krummrich" <dakr@kernel.org>
To: "Gary Guo" <gary@garyguo.net>
Cc: Eliot Courtney <ecourtney@nvidia.com>,
acourbot@nvidia.com, aliceryhl@google.com,
nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel <dri-devel-bounces@lists.freedesktop.org>
Subject: Re: [PATCH] gpu: nova-core: gsp: fix UB in DmaGspMem pointer accessors
Date: Wed, 11 Mar 2026 14:04:29 +0100 [thread overview]
Message-ID: <DGZZ35ONHS0Q.N6Q05IA0T0IB@kernel.org> (raw)
In-Reply-To: <DGZYYB7XDN4N.3L7ZRCJSQH2QE@garyguo.net>
On Wed Mar 11, 2026 at 1:58 PM CET, Gary Guo wrote:
> If this patch is intended to go through -fixes, then we should really land your
> series via -fixes too, otherwise it is just causing unnecessary conflicts on
> linux-next.
It has already been merged in drm-rust-next, so we will have the conflict
temporarily. I say temporarily because I will backmerge once the changes in
-fixes hit Linus' tree anyways.
WARNING: multiple messages have this Message-ID (diff)
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Gary Guo" <gary@garyguo.net>
Cc: "Eliot Courtney" <ecourtney@nvidia.com>, <acourbot@nvidia.com>,
<aliceryhl@google.com>, <nouveau@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>,
<rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"dri-devel" <dri-devel-bounces@lists.freedesktop.org>
Subject: Re: [PATCH] gpu: nova-core: gsp: fix UB in DmaGspMem pointer accessors
Date: Wed, 11 Mar 2026 14:04:29 +0100 [thread overview]
Message-ID: <DGZZ35ONHS0Q.N6Q05IA0T0IB@kernel.org> (raw)
In-Reply-To: <DGZYYB7XDN4N.3L7ZRCJSQH2QE@garyguo.net>
On Wed Mar 11, 2026 at 1:58 PM CET, Gary Guo wrote:
> If this patch is intended to go through -fixes, then we should really land your
> series via -fixes too, otherwise it is just causing unnecessary conflicts on
> linux-next.
It has already been merged in drm-rust-next, so we will have the conflict
temporarily. I say temporarily because I will backmerge once the changes in
-fixes hit Linus' tree anyways.
next prev parent reply other threads:[~2026-03-11 13:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 22:53 [PATCH] gpu: nova-core: gsp: fix UB in DmaGspMem pointer accessors Danilo Krummrich
2026-03-10 2:01 ` Gary Guo
2026-03-10 2:01 ` Gary Guo
2026-03-10 3:56 ` Eliot Courtney
2026-03-10 3:56 ` Eliot Courtney
2026-03-10 11:02 ` Danilo Krummrich
2026-03-10 11:02 ` Danilo Krummrich
2026-03-11 12:58 ` Gary Guo
2026-03-11 12:58 ` Gary Guo
2026-03-11 13:04 ` Danilo Krummrich [this message]
2026-03-11 13:04 ` Danilo Krummrich
2026-03-10 10:58 ` Danilo Krummrich
2026-03-10 10:58 ` Danilo Krummrich
2026-03-11 12:59 ` Gary Guo
2026-03-11 12:59 ` Gary Guo
2026-03-11 13:05 ` Danilo Krummrich
2026-03-11 13:05 ` Danilo Krummrich
2026-03-11 8:01 ` Alexandre Courbot
2026-03-11 8:01 ` Alexandre Courbot
2026-03-11 19:29 ` Danilo Krummrich
2026-03-11 19:29 ` Danilo Krummrich
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=DGZZ35ONHS0Q.N6Q05IA0T0IB@kernel.org \
--to=dakr@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=dri-devel-bounces@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ecourtney@nvidia.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.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 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.