From: "José Expósito" <jose.exposito89@gmail.com>
To: Melissa Wen <mwen@igalia.com>
Cc: melissa.srw@gmail.com, rodrigosiqueiramelo@gmail.com,
hamohammed.sa@gmail.com, daniel@ffwll.ch, airlied@linux.ie,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v2 2/3] drm/vkms: add support for multiple overlay planes
Date: Sun, 9 Jan 2022 18:59:31 +0100 [thread overview]
Message-ID: <20220109175931.GA11065@elementary> (raw)
In-Reply-To: <20220109165933.sa6kpgrzdzj5r3ho@mail.igalia.com>
Hi Melissa,
Thanks for reviewing and applying the series :)
Now [1] should apply cleanly on drm-misc-next. Do you want me to resend
it with the appropriate prefix?
On Sun, Jan 09, 2022 at 03:59:55PM -0100, Melissa Wen wrote:
> I checked that several testcases from kms_cursor_crc are failing after
> recent changes in the test. However, this regression is not caused by
> these changes and need futher investigation for fixing.
I didn't include the results for kms_cursor_crc because some of the
tests cause issues on my PC. However, if you want to share the list of
regressions, I'll have a look into the test as well.
Thanks again,
José Expósito
[1] https://lore.kernel.org/all/20211226111219.27616-2-jose.exposito89@gmail.com/
next prev parent reply other threads:[~2022-01-09 17:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 18:28 [PATCH RESEND v2 1/3] drm/vkms: refactor overlay plane creation José Expósito
2022-01-07 18:28 ` [PATCH RESEND v2 2/3] drm/vkms: add support for multiple overlay planes José Expósito
2022-01-09 16:59 ` Melissa Wen
2022-01-09 17:59 ` José Expósito [this message]
2022-01-07 18:28 ` [PATCH RESEND v2 3/3] drm/vkms: drop "Multiple overlay planes" TODO José Expósito
2022-01-09 17:03 ` Melissa Wen
2022-01-09 16:50 ` [PATCH RESEND v2 1/3] drm/vkms: refactor overlay plane creation Melissa Wen
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=20220109175931.GA11065@elementary \
--to=jose.exposito89@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=melissa.srw@gmail.com \
--cc=mwen@igalia.com \
--cc=rodrigosiqueiramelo@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox