From: Greg KH <gregkh@linuxfoundation.org>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: stable@vger.kernel.org, "Manasi Navare" <navaremanasi@google.com>,
"Drew Davenport" <ddavenport@chromium.org>,
"Imre Deak" <imre.deak@intel.com>,
"Jouni Högander" <jouni.hogander@intel.com>
Subject: Re: [PATCH 6.1.y 1/2] drm/i915: Add a .color_post_update() hook
Date: Sat, 15 Apr 2023 08:53:00 +0200 [thread overview]
Message-ID: <2023041519-margin-agenda-66b4@gregkh> (raw)
In-Reply-To: <20230414083140.24095-1-ville.syrjala@linux.intel.com>
On Fri, Apr 14, 2023 at 11:31:39AM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> We're going to need stuff after the color management
> register latching has happened. Add a corresponding hook.
>
> Cc: <stable@vger.kernel.org> #v5.19+
> Cc: <stable@vger.kernel.org> # 52a90349f2ed: drm/i915: Introduce intel_crtc_needs_fastset()
> Cc: <stable@vger.kernel.org> # 925ac8bc33bf: drm/i915: Remove some local 'mode_changed' bools
> Cc: <stable@vger.kernel.org> # f5e674e92e95: drm/i915: Introduce intel_crtc_needs_color_update()
> Cc: <stable@vger.kernel.org> # 4c35e5d11900: drm/i915: Activate DRRS after state readout
> Cc: <stable@vger.kernel.org> # efb2b57edf20: drm/i915: Move the DSB setup/cleaup into the color code
> Cc: Manasi Navare <navaremanasi@google.com>
> Cc: Drew Davenport <ddavenport@chromium.org>
> Cc: Imre Deak <imre.deak@intel.com>
> Cc: Jouni Högander <jouni.hogander@intel.com>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Link: https://patchwork.freedesktop.org/patch/msgid/20230320095438.17328-4-ville.syrjala@linux.intel.com
> Reviewed-by: Imre Deak <imre.deak@intel.com>
> (cherry picked from commit 3962ca4e080a525fc9eae87aa6b2286f1fae351d)
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> (cherry picked from commit c880f855d1e240a956dcfce884269bad92fc849c)
> ---
> Picked up one more dependency to ease the backport.
Can you just send all of the needed patches, as a series, so that we can
apply them at once?
Adding to the "dependency list" doesn't help much for patch series sent
to us like this, sorry.
greg k-h
next prev parent reply other threads:[~2023-04-15 6:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 8:54 FAILED: patch "[PATCH] drm/i915: Workaround ICL CSC_MODE sticky arming" failed to apply to 6.1-stable tree gregkh
2023-04-03 16:26 ` [PATCH 6.1.y 1/3] drm/i915: Split icl_color_commit_noarm() from skl_color_commit_noarm() Ville Syrjala
2023-04-03 16:26 ` [PATCH 6.1.y 2/3] drm/i915: Add a .color_post_update() hook Ville Syrjala
2023-04-12 7:57 ` [PATCH " Greg KH
2023-04-14 8:31 ` [PATCH 6.1.y 1/2] " Ville Syrjala
2023-04-14 8:31 ` [PATCH 6.1.y 2/2] drm/i915: Workaround ICL CSC_MODE sticky arming Ville Syrjala
2023-04-15 6:53 ` Greg KH [this message]
2023-04-03 16:26 ` [PATCH 6.1.y 3/3] " Ville Syrjala
2023-04-11 13:58 ` [PATCH 6.1.y 1/3] drm/i915: Split icl_color_commit_noarm() from skl_color_commit_noarm() Greg KH
2023-04-11 15:51 ` Ville Syrjälä
2023-04-12 6:17 ` Greg KH
2023-04-12 6:40 ` Ville Syrjälä
2023-04-12 6:50 ` Greg KH
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=2023041519-margin-agenda-66b4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ddavenport@chromium.org \
--cc=imre.deak@intel.com \
--cc=jouni.hogander@intel.com \
--cc=navaremanasi@google.com \
--cc=stable@vger.kernel.org \
--cc=ville.syrjala@linux.intel.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.