All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
To: Melissa Wen <melissa.srw@gmail.com>
Cc: igt-dev@lists.freedesktop.org, kernel-usp@googlegroups.com,
	twoerner@gmail.com
Subject: Re: [igt-dev] [PATCH i-g-t v2 1/1] test/kms_cursor_crc: release old pipe_crc before create a new one
Date: Mon, 20 Jul 2020 18:10:26 +0300	[thread overview]
Message-ID: <20200720151026.d7wrd65vlrval3cx@ahiler-desk1.fi.intel.com> (raw)
In-Reply-To: <e2e335dbf2189ea9ece3373364520eca8eb3349b.1594897760.git.melissa.srw@gmail.com>

On Thu, Jul 16, 2020 at 08:25:21AM -0300, Melissa Wen wrote:
> When a subtest fails, it skips the cleanup, and its pipe_crc remains allocated.
> As a consequence, the following subtest also fails (timeout) when trying to
> create a new one. This patch releases any remaining pipe_crc to enable the
> creation of a new one for the next subtest.
> 
> Signed-off-by: Melissa Wen <melissa.srw@gmail.com>

Reviewed-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>

and merged, thanks!
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-07-20 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 11:24 [igt-dev] [PATCH i-g-t v2 0/1] test/kms_cursor_crc: tie some loose ends in prepare_crtc Melissa Wen
2020-07-16 11:25 ` [igt-dev] [PATCH i-g-t v2 1/1] test/kms_cursor_crc: release old pipe_crc before create a new one Melissa Wen
2020-07-20 15:10   ` Arkadiusz Hiler [this message]
2020-07-16 11:52 ` [igt-dev] ✓ Fi.CI.BAT: success for test/kms_cursor_crc: tie some loose ends in prepare_crtc (rev2) Patchwork
2020-07-16 15:10 ` [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=20200720151026.d7wrd65vlrval3cx@ahiler-desk1.fi.intel.com \
    --to=arkadiusz.hiler@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kernel-usp@googlegroups.com \
    --cc=melissa.srw@gmail.com \
    --cc=twoerner@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 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.