From: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
To: Kamati Srinivas <srinivasx.k@intel.com>, igt-dev@lists.freedesktop.org
Cc: tejaskumarx.surendrakumar.upadhyay@intel.com,
juha-pekka.heikkila@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t] Stripping rendercopy implementation to use Cairo for restoring test image
Date: Wed, 2 Sep 2020 15:02:58 +0300 [thread overview]
Message-ID: <a3e2c650-9fdf-eafa-706d-1612ccfc9e84@gmail.com> (raw)
In-Reply-To: <20200901153302.26667-1-srinivasx.k@intel.com>
Hi Srinivas,
I noticed your patch got stuck in CI with false positive failures, I
forwarded the issue to Lakshminarayana Vudum. Once Lakshmi see my mail
he'll mark those failures not to be about your patch and your patch will
go on to shards testing.
About the patch otherwise, on subject line you should have note you're
changing content in tests and which test. On this case subject would
begin with 'tests/kms_cursor_crc: ...'
On 1.9.2020 18.33, Kamati Srinivas wrote:
> Cc: Landwerlin, Lionel G <lionel.g.landwerlin@intel.com>
> Cc: Heikkila, Juha-pekka <juha-pekka.heikkila@intel.com>
> Cc: Tejask Upadhyay <tejaskumarx.surendrakumar.upadhyay@intel.com>
> Cc: K Srinivas <srinivasx.k@intel.com>
> Signed-off-by: Kamati Srinivas <srinivasx.k@intel.com>
> ---
> tests/kms_cursor_crc.c | 10 +---------
> 1 file changed, 1 insertion(+), 9 deletions(-)
>
> diff --git a/tests/kms_cursor_crc.c b/tests/kms_cursor_crc.c
> index e9491847..079abe88 100644
> --- a/tests/kms_cursor_crc.c
> +++ b/tests/kms_cursor_crc.c
> @@ -831,15 +831,7 @@ igt_main
>
> igt_display_require(&data.display, data.drm_fd);
>
> - if (is_i915_device(data.drm_fd)) {
> - data.bufmgr = drm_intel_bufmgr_gem_init(data.drm_fd, 4096);
> - igt_assert(data.bufmgr);
> - drm_intel_bufmgr_gem_enable_reuse(data.bufmgr);
> -
> - data.devid = intel_get_drm_devid(data.drm_fd);
> - data.rendercopy = igt_get_render_copyfunc(data.devid);
> - }
> - igt_debug("Using %s for restoring test image\n", (data.rendercopy == NULL)?"Cairo":"rendercopy");
> + igt_debug("Using Cairo for restoring test image\n");
You'll need to remove all related dead code. I'd suggest you'll take out
from data_t structure all variables which are for rendercopy and you'll
see where compilation fail and from this you'll know where you need to
go fix. Quickly looking at least those data.rendercopy, data.bufmgr
which are mentioned in above code.
> }
>
> data.cursor_max_w = cursor_width;
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-09-02 12:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 15:33 [igt-dev] [PATCH i-g-t] Stripping rendercopy implementation to use Cairo for restoring test image Kamati Srinivas
2020-09-02 9:05 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2020-09-02 12:02 ` Juha-Pekka Heikkila [this message]
2020-09-02 16:09 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-09-03 17:13 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
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=a3e2c650-9fdf-eafa-706d-1612ccfc9e84@gmail.com \
--to=juhapekka.heikkila@gmail.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=juha-pekka.heikkila@intel.com \
--cc=srinivasx.k@intel.com \
--cc=tejaskumarx.surendrakumar.upadhyay@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox