From: "Szwichtenberg, Radoslaw" <radoslaw.szwichtenberg@intel.com>
To: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>
Cc: "Vetter, Daniel" <daniel.vetter@intel.com>
Subject: Re: [PATCH i-g-t v3] tests/gem_flink_basic: Add documentation for subtests
Date: Fri, 15 Sep 2017 07:34:06 +0000 [thread overview]
Message-ID: <1505460843.21576.25.camel@intel.com> (raw)
In-Reply-To: <1505412598-35854-1-git-send-email-vinay.belgaumkar@intel.com>
On Thu, 2017-09-14 at 11:09 -0700, Vinay Belgaumkar wrote:
> Added the missing IGT_TEST_DESCRIPTION and some subtest
> descriptions.
>
> v2: Removed duplication, addressed comments, cc'd test author
>
> v3: Only comment abstract code, change some igt_info to igt_debug.
> Changed description to reflect this is a patch, not an RFC.
>
> Cc: Michał Winiarski <michal.winiarski@intel.com>
> Cc: Eric Anholt <eric@anholt.net>
> Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
> Cc: Daniel Vetter <daniel.vetter@intel.com>
>
> Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
LGTM
Reviewed-by: Radoslaw Szwichtenberg <radoslaw.szwichtenberg@intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-09-15 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 18:09 [PATCH i-g-t v3] tests/gem_flink_basic: Add documentation for subtests Vinay Belgaumkar
2017-09-14 19:15 ` ✓ Fi.CI.BAT: success for tests/gem_flink_basic: Add documentation for subtests (rev3) Patchwork
2017-09-15 3:15 ` ✗ Fi.CI.IGT: failure " Patchwork
2017-09-15 7:34 ` Szwichtenberg, Radoslaw [this message]
2017-09-15 7:36 ` [PATCH i-g-t v3] tests/gem_flink_basic: Add documentation for subtests Szwichtenberg, Radoslaw
2017-09-22 10:33 ` Arkadiusz Hiler
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=1505460843.21576.25.camel@intel.com \
--to=radoslaw.szwichtenberg@intel.com \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=vinay.belgaumkar@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