dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Stone <daniels@collabora.com>
To: dri-devel@lists.freedesktop.org
Subject: [PATCH igt v7 0/4] Assert tests, atomic, multi-blob
Date: Thu, 29 Oct 2015 10:31:15 +0000	[thread overview]
Message-ID: <1446114679-6844-1-git-send-email-daniels@collabora.com> (raw)

Hi,
Following on from the previous few series, most of which have been
merged ...

Add some self-tests for igt-assert_*() to make sure they do the right
thing, including for fds. This is a bit gross, but does work.

Do a Cocci run through the tree. This doesn't actually pick up a lot
of the changes for some reason, but I have not a clue why.

Add a new subtest to core_prop_blob which creates multiple blobs per
connection, exercising a kernel bug.

Resubmit the atomic tests, with only minor changes this time.

Cheers,
Daniel

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2015-10-29 10:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29 10:31 Daniel Stone [this message]
2015-10-29 10:31 ` [PATCH igt v7 1/4] lib/tests: Add igt_assert_*() self-tests Daniel Stone
2015-10-29 12:36   ` Thomas Wood
2015-10-29 10:35 ` [PATCH igt v7 2/4] tests: Run igt.cocci Daniel Stone
2015-10-29 10:35   ` [PATCH igt v7 3/4] tests/core_prop_blob: Add multiple blobs per connection Daniel Stone
2015-10-29 10:35   ` [PATCH igt v7 4/4] kms_atomic: Add basic atomic modesetting tests Daniel Stone
2015-10-29 11:33     ` Emil Velikov
2015-10-30 10:44       ` Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2015-10-29 11:01 [PATCH igt v7 0/4] Assert tests, atomic, multi-blob Daniel Stone

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=1446114679-6844-1-git-send-email-daniels@collabora.com \
    --to=daniels@collabora.com \
    --cc=dri-devel@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