From: Eric Engestrom <eric.engestrom@intel.com>
To: Karsten Hohmeier <karsten@hohmatik.de>
Cc: dri-devel@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Madhur Verma <madhur.verma@samsung.com>,
stable@vger.kernel.org,
Hemanshu Srivastava <hemanshu.s@samsung.com>,
Sean Paul <seanpaul@chromium.org>,
Satendra Singh Thakur <satendra.t@samsung.com>
Subject: Re: [PATCH] Fixes: fc2a69f3903d ("drm/atomic: Handling the case when, setting old crtc for plane")
Date: Wed, 5 Sep 2018 10:37:39 +0100 [thread overview]
Message-ID: <20180905093739.mtakpyog63tfmgff@intel.com> (raw)
In-Reply-To: <279cbe23-ed68-2729-bba9-61953a65a1cb@hohmatik.de>
Hey Karsten, thanks for the patch! I don't know if it's correct or not,
but I'll comment on a few other things.
The title of the commit should be a description of what your commit does;
in this case you should probably keep the title that git gave you when
you did `git revert`, as well as the first line:
Revert "drm/atomic: Handling the case when setting old crtc for plane"
This reverts commit fc2a69f3903dfd97cd47f593e642b47918c949df.
After that comes your explanation of why this commit should be reverted,
which you've done here:
On Wednesday, 2018-09-05 00:26:27 +0200, Karsten Hohmeier wrote:
> Original commit causes "plane A assertion failure" on lid close/lid open
> with older HP Compaq 6720s laptops (Intel Mobile GME965/GLE960).
The "Fixes" line that Chris gave you should got at the end of the commit
message, after the explanation.
> Full bug report at "https://bugs.freedesktop.org/show_bug.cgi?id=107827".
The format for bug report references is (on its own line):
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107827
> ---
> drivers/gpu/drm/drm_atomic.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_atomic.c b/drivers/gpu/drm/drm_atomic.c
> index 895741e9cd7d..a59ded403657 100644
> --- a/drivers/gpu/drm/drm_atomic.c
> +++ b/drivers/gpu/drm/drm_atomic.c
> @@ -1433,9 +1433,7 @@ drm_atomic_set_crtc_for_plane(struct
> drm_plane_state *plane_state,
It looks like thunderbird mangled the patch when sending the email; it's
recommended to use `git send-email` instead, as it does the right thing:
https://git-scm.com/docs/git-send-email
> {
> struct drm_plane *plane = plane_state->plane;
> struct drm_crtc_state *crtc_state;
> - /* Nothing to do for same crtc*/
> - if (plane_state->crtc == crtc)
> - return 0;
> +
> if (plane_state->crtc) {
> crtc_state = drm_atomic_get_crtc_state(plane_state->state,
> plane_state->crtc);
> --
> 2.11.0
>
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-09-05 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 22:26 [PATCH] Fixes: fc2a69f3903d ("drm/atomic: Handling the case when, setting old crtc for plane") Karsten Hohmeier
2018-09-05 9:23 ` Jani Nikula
2018-09-05 9:34 ` Daniel Vetter
2018-09-05 9:36 ` Maarten Lankhorst
2018-09-05 9:37 ` Eric Engestrom [this message]
2018-09-06 4:39 ` Satendra Singh Thakur
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=20180905093739.mtakpyog63tfmgff@intel.com \
--to=eric.engestrom@intel.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hemanshu.s@samsung.com \
--cc=karsten@hohmatik.de \
--cc=madhur.verma@samsung.com \
--cc=satendra.t@samsung.com \
--cc=seanpaul@chromium.org \
--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;
as well as URLs for NNTP newsgroup(s).