From: Frej Drejhammar <frej.drejhammar@gmail.com>
To: Kevin Hao <haokexin@gmail.com>
Cc: dri-devel@lists.freedesktop.org, "Jyri Sarha" <jyri.sarha@iki.fi>,
"Tomi Valkeinen" <tomi.valkeinen@ideasonboard.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Maíra Canal" <mcanal@igalia.com>
Subject: Re: [PATCH] drm/tilcdc: Set preferred depth
Date: Mon, 18 Mar 2024 20:21:46 +0100 [thread overview]
Message-ID: <kle6f8hx1.fsf@gmail.com> (raw)
In-Reply-To: <ZfePYNWY5_1XwS_A@pek-khao-d3> (Kevin Hao's message of "Mon, 18 Mar 2024 08:48:32 +0800")
Hi, Kevin
Kevin Hao <haokexin@gmail.com> writes:
> I had also thought about a similar modification before, but personally,
> I considered such changes a bit aggressive for a patch that needs to be
> backported to a stable kernel (especially for a LTS kernel such as v6.6
> which I am working on). That's why I opted for minimal changes to fix this
> regression, reducing the risk when we backport it to the stable kernel.
Personally I only work with the latest stable mainline kernel, so I want
to fix both the regression and enable a 24 bit color depth...
> Additionally, my patch and your patch don't conflict semantically, and
> setting a driver's preferred_depth shouldn't cause any other issues.
True, we'll see what the maintainers say.
Regards,
--Frej
next prev parent reply other threads:[~2024-03-18 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 3:39 [PATCH] drm/tilcdc: Set preferred depth Kevin Hao
2024-03-17 19:18 ` Frej Drejhammar
2024-03-18 0:48 ` Kevin Hao
2024-03-18 19:21 ` Frej Drejhammar [this message]
2024-03-19 11:05 ` sarha
2024-03-19 19:17 ` Frej Drejhammar
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=kle6f8hx1.fsf@gmail.com \
--to=frej.drejhammar@gmail.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=haokexin@gmail.com \
--cc=jyri.sarha@iki.fi \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcanal@igalia.com \
--cc=mripard@kernel.org \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tzimmermann@suse.de \
/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