From: "Danilo Krummrich" <dakr@kernel.org>
To: "James Jones" <jajones@nvidia.com>
Cc: "Lyude Paul" <lyude@redhat.com>,
"Faith Ekstrand" <faith.ekstrand@collabora.com>,
<nouveau@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Joel Fernandes" <joelagnelf@nvidia.com>
Subject: Re: [PATCH 2/3] drm/nouveau/disp: Always accept linear modifier
Date: Fri, 22 Aug 2025 22:55:23 +0200 [thread overview]
Message-ID: <DC99870U9374.HUXNLLZ5ZYBE@kernel.org> (raw)
In-Reply-To: <20250811220017.1337-3-jajones@nvidia.com>
On Tue Aug 12, 2025 at 12:00 AM CEST, James Jones wrote:
> On some chipsets, which block-linear modifiers are
> supported is format-specific. However, linear
> modifiers are always be supported. The prior
> modifier filtering logic was not accounting for
> the linear case.
>
> Fixes: c586f30bf74c ("drm/nouveau/kms: Add format mod prop to base/ovly/nvdisp")
> Signed-off-by: James Jones <jajones@nvidia.com>
This issue seems to be present since v5.10, what's the implication of this? I
assume this has to be backported into stable releases?
Does the subsequent patch break strictly depend on this fix, or can it go
separately?
next prev parent reply other threads:[~2025-08-22 20:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 22:00 [PATCH 0/3] drm/nouveau: Advertise correct modifiers on GB20x James Jones
2025-08-11 22:00 ` [PATCH 1/3] drm: define NVIDIA DRM format modifiers for GB20x James Jones
2025-08-22 15:51 ` Faith Ekstrand
2025-08-22 16:16 ` Faith Ekstrand
2025-09-02 13:41 ` Danilo Krummrich
2025-10-15 0:10 ` James Jones
2025-08-11 22:00 ` [PATCH 2/3] drm/nouveau/disp: Always accept linear modifier James Jones
2025-08-22 16:17 ` Faith Ekstrand
2025-08-22 20:55 ` Danilo Krummrich [this message]
2025-08-22 21:11 ` James Jones
2025-08-22 21:14 ` Danilo Krummrich
2025-08-22 23:14 ` Danilo Krummrich
2025-08-11 22:00 ` [PATCH 3/3] drm/nouveau: Advertise correct modifiers on GB20x James Jones
2025-08-22 15:48 ` Faith Ekstrand
2025-08-22 17:03 ` James Jones
2025-08-22 17:10 ` Faith Ekstrand
2025-08-22 20:44 ` [PATCH 0/3] " Faith Ekstrand
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=DC99870U9374.HUXNLLZ5ZYBE@kernel.org \
--to=dakr@kernel.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=faith.ekstrand@collabora.com \
--cc=jajones@nvidia.com \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=simona@ffwll.ch \
/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.