From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
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/3] drm/i915: Split icl_color_commit_noarm() from skl_color_commit_noarm()
Date: Tue, 11 Apr 2023 18:51:52 +0300 [thread overview]
Message-ID: <ZDWCGGgxGvcsFXhi@intel.com> (raw)
In-Reply-To: <2023041117-cannot-sensuous-6f62@gregkh>
On Tue, Apr 11, 2023 at 03:58:49PM +0200, Greg KH wrote:
> On Mon, Apr 03, 2023 at 07:26:16PM +0300, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > We're going to want different behavior for skl/glk vs. icl
> > in .color_commit_noarm(), so split the hook into two. Arguably
> > we already had slightly different behaviour since
> > csc_enable/gamma_enable are never set on icl+, so the old
> > code was perhaps a bit confusing as well.
> >
> > Cc: <stable@vger.kernel.org> #v5.19+
> > Cc: <stable@vger.kernel.org> # 05ca98523481: drm/i915: Use _MMIO_PIPE() for SKL_BOTTOM_COLOR
> > 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-2-ville.syrjala@linux.intel.com
> > Reviewed-by: Imre Deak <imre.deak@intel.com>
> > (cherry picked from commit f161eb01f50ab31f2084975b43bce54b7b671e17)
> > Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> > (cherry picked from commit 76b767d4d1cd052e455cf18e06929e8b2b70101d)
> > ---
> > drivers/gpu/drm/i915/display/intel_color.c | 21 ++++++++++++++++++++-
> > 1 file changed, 20 insertions(+), 1 deletion(-)
>
> This commit breaks the build.
You did cherry pick all the dependencies I listed?
>
> Always test-build the stuff you send out. please.
I did.
>
> Whole series dropped from my review queue.
>
> greg k-h
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2023-04-11 15:52 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 ` [PATCH 6.1.y 1/2] drm/i915: Add a .color_post_update() hook Greg KH
2023-04-03 16:26 ` [PATCH 6.1.y 3/3] drm/i915: Workaround ICL CSC_MODE sticky arming 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ä [this message]
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=ZDWCGGgxGvcsFXhi@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=ddavenport@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=imre.deak@intel.com \
--cc=jouni.hogander@intel.com \
--cc=navaremanasi@google.com \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox