From: lyude@redhat.com
To: Aaron Kling <webgeek1234@gmail.com>, Danilo Krummrich <dakr@kernel.org>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Faith Ekstrand <faith.ekstrand@collabora.com>
Subject: Re: [PATCH v2] drm/nouveau: Use write-combined maps for coherent
Date: Tue, 01 Sep 2026 15:55:11 -0400 [thread overview]
Message-ID: <27200b7e13ecc99d57c41da4e25fad690fca68d7.camel@redhat.com> (raw)
In-Reply-To: <CALHNRZ-JmYx-PhruhDZ3L8aPVu51cJrqP_FeNtGTyMHCH_esgg@mail.gmail.com>
On Tue, 2026-09-01 at 13:03 -0500, Aaron Kling wrote:
>
> Looks like the tag is:
>
> Fixes: 1b4ea4c5980f ("drm/ttm: set the tt caching state at creation
> time")
>
> Should I send another revision just to add this, or can the subsystem
> maintainer add it when picking the change up? For stable, I would
> like
> to see this picked to 6.18 at least, since I primarily work with LTS
> forks.
>
> Aaron
I would send out a respin with the tag
WARNING: multiple messages have this Message-ID (diff)
From: lyude@redhat.com
To: Aaron Kling <webgeek1234@gmail.com>, Danilo Krummrich <dakr@kernel.org>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Faith Ekstrand <faith.ekstrand@collabora.com>
Subject: Re: [PATCH v2] drm/nouveau: Use write-combined maps for coherent
Date: Tue, 01 Sep 2026 15:55:11 -0400 [thread overview]
Message-ID: <27200b7e13ecc99d57c41da4e25fad690fca68d7.camel@redhat.com> (raw)
In-Reply-To: <CALHNRZ-JmYx-PhruhDZ3L8aPVu51cJrqP_FeNtGTyMHCH_esgg@mail.gmail.com>
On Tue, 2026-09-01 at 13:03 -0500, Aaron Kling wrote:
>
> Looks like the tag is:
>
> Fixes: 1b4ea4c5980f ("drm/ttm: set the tt caching state at creation
> time")
>
> Should I send another revision just to add this, or can the subsystem
> maintainer add it when picking the change up? For stable, I would
> like
> to see this picked to 6.18 at least, since I primarily work with LTS
> forks.
>
> Aaron
I would send out a respin with the tag
next prev parent reply other threads:[~2026-09-01 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 4:42 [PATCH v2] drm/nouveau: Use write-combined maps for coherent Aaron Kling via B4 Relay
2026-08-22 4:42 ` Aaron Kling
2026-08-22 4:42 ` Aaron Kling via B4 Relay
2026-09-01 14:07 ` Danilo Krummrich
2026-09-01 14:07 ` Danilo Krummrich
2026-09-01 18:03 ` Aaron Kling
2026-09-01 18:03 ` Aaron Kling
2026-09-01 19:55 ` lyude [this message]
2026-09-01 19:55 ` lyude
2026-09-01 20:29 ` Danilo Krummrich
2026-09-01 20: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=27200b7e13ecc99d57c41da4e25fad690fca68d7.camel@redhat.com \
--to=lyude@redhat.com \
--cc=airlied@gmail.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=faith.ekstrand@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=webgeek1234@gmail.com \
/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.