public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: Lyude <lyude@redhat.com>
Cc: igt-dev@lists.freedesktop.org, nouveau@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v3 2/5] lib/igt_core: Add igt_require_fd()
Date: Mon, 20 Apr 2020 12:29:55 +0300	[thread overview]
Message-ID: <20200420092955.GX9497@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20200417211025.109574-3-lyude@redhat.com>

On Fri, Apr 17, 2020 at 05:10:22PM -0400, Lyude wrote:
> From: Lyude Paul <lyude@redhat.com>
> 
> Like igt_assert_fd(), but using igt_require() instead
> 
> Changes since v1:
> * Fix documentation error in igt_require_fd() - Petri Latvala
> 
> Signed-off-by: Lyude Paul <lyude@redhat.com>


Reviewed-by: Petri Latvala <petri.latvala@intel.com>



> ---
>  lib/igt_core.h | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/lib/igt_core.h b/lib/igt_core.h
> index 3f69b072..8f68b2dd 100644
> --- a/lib/igt_core.h
> +++ b/lib/igt_core.h
> @@ -1021,6 +1021,18 @@ void igt_describe_f(const char *fmt, ...);
>  	else igt_debug("Test requirement passed: %s\n", #expr); \
>  } while (0)
>  
> +/**
> + * igt_require_fd:
> + * @fd: file descriptor
> + *
> + * Skips (sub-) test if the given file descriptor is invalid.
> + *
> + * Like igt_require(), but displays the stringified identifier that was supposed
> + * to contain a valid fd on failure.
> + */
> +#define igt_require_fd(fd) \
> +	igt_require_f(fd >= 0, "file descriptor " #fd " failed\n");
> +
>  /**
>   * igt_skip_on_f:
>   * @expr: condition to test
> -- 
> 2.25.1
> 
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-04-20  9:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-17 21:10 [igt-dev] [PATCH i-g-t v3 0/5] Add nouveau-crc tests Lyude
2020-04-17 21:10 ` [igt-dev] [PATCH i-g-t v3 1/5] lib/igt_core: Fix igt_assert_fd() documentation Lyude
2020-04-20  9:29   ` Petri Latvala
2020-04-17 21:10 ` [igt-dev] [PATCH i-g-t v3 2/5] lib/igt_core: Add igt_require_fd() Lyude
2020-04-20  9:29   ` Petri Latvala [this message]
2020-04-17 21:10 ` [igt-dev] [PATCH i-g-t v3 3/5] lib/igt_debugfs: Add igt_debugfs_pipe_dir() Lyude
2020-08-18 21:01   ` [igt-dev] [i-g-t, v3, " Jeremy Cline
2020-04-17 21:10 ` [igt-dev] [PATCH i-g-t v3 4/5] lib/igt_kms: Hook up connector dithering prop Lyude
2020-08-18 21:18   ` [igt-dev] [i-g-t, v3, " Jeremy Cline
2020-04-17 21:10 ` [igt-dev] [PATCH i-g-t v3 5/5] tests: Add nouveau-crc tests Lyude
2020-08-18 21:00   ` [igt-dev] [PATCH i-g-t v4] " Lyude
2020-09-28 21:36     ` Jeremy Cline
2020-09-29 16:13       ` Lyude Paul
2020-09-29 17:42         ` Jeremy Cline
2020-04-17 23:16 ` [igt-dev] ✗ GitLab.Pipeline: warning for Add nouveau-crc tests (rev3) Patchwork
2020-04-17 23:29 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-04-19 20:33 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2020-08-18 21:57 ` [igt-dev] ✓ Fi.CI.BAT: success for Add nouveau-crc tests (rev4) Patchwork
2020-08-19  4:40 ` [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=20200420092955.GX9497@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=lyude@redhat.com \
    --cc=nouveau@lists.freedesktop.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