From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>, dri-devel@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
stable@vger.kernel.org,
Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Subject: Re: [PATCH v2] drm: Block fb changes for async plane updates
Date: Tue, 08 Jan 2019 00:57:49 +0000 [thread overview]
Message-ID: <20190108005750.5862720827@mail.kernel.org> (raw)
In-Reply-To: <20190107174146.2947-1-nicholas.kazlauskas@amd.com>
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: fef9df8b5945 drm/atomic: initial support for asynchronous plane update.
The bot has tested the following trees: v4.20.0, v4.19.13, v4.14.91.
v4.20.0: Build OK!
v4.19.13: Build OK!
v4.14.91: Build failed! Errors:
drivers/gpu/drm/drm_atomic_helper.c:1421:6: error: ‘old_plane_state’ undeclared (first use in this function); did you mean ‘drm_plane_state’?
drivers/gpu/drm/drm_atomic_helper.c:1421:29: error: ‘new_plane_state’ undeclared (first use in this function); did you mean ‘drm_plane_state’?
How should we proceed with this patch?
--
Thanks,
Sasha
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-01-08 0:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 17:41 [PATCH v2] drm: Block fb changes for async plane updates Nicholas Kazlauskas
2019-01-07 17:41 ` Nicholas Kazlauskas
2019-01-08 0:57 ` Sasha Levin [this message]
2019-02-13 21:21 ` Helen Koike via dri-devel
2019-02-13 23:32 ` Helen Koike via dri-devel
2019-02-14 8:21 ` Daniel Vetter
2019-02-14 13:37 ` Helen Koike via dri-devel
2019-02-14 14:13 ` Wentland, Harry
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=20190108005750.5862720827@mail.kernel.org \
--to=sashal@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=nicholas.kazlauskas@amd.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 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.