From: Matt Roper <matthew.d.roper@intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] NEWS: Updates
Date: Thu, 24 Jul 2014 17:49:29 -0700 [thread overview]
Message-ID: <20140725004929.GF1618@intel.com> (raw)
In-Reply-To: <1406147563-21526-1-git-send-email-daniel.vetter@ffwll.ch>
On Wed, Jul 23, 2014 at 10:32:43PM +0200, Daniel Vetter wrote:
> ---
> NEWS | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/NEWS b/NEWS
> index 1b5ee83ec849..4866d59b5619 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -10,6 +10,12 @@ Release 1.8 (xxxx-xx-xx)
>
> - As usual piles of new tests.
>
> +- Improved plane/pipe handling in the igt_kms library (Damien).
> +
> +- Unified option parsing between simple tests and tests with subtests (Thomas).
> + This will allow us to merge the different Makefile targets once test runners
> + are converted.
> +
Might be worth adding a bullet for the new "commit style" support in
igt_kms (igt_display_commit2 / igt_display_try_commit2). That allows us
to expose the universal plane interfaces today and also provides a
natural way to expose atomic interfaces in the future.
Matt
> Release 1.7 (2014-06-09)
> ------------------------
>
> --
> 2.0.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Matt Roper
Graphics Software Engineer
IoTG Platform Enabling & Development
Intel Corporation
(916) 356-2795
next prev parent reply other threads:[~2014-07-25 0:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 20:32 [PATCH] NEWS: Updates Daniel Vetter
2014-07-25 0:49 ` Matt Roper [this message]
2014-07-25 7:28 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2014-07-10 18:20 Daniel Vetter
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=20140725004929.GF1618@intel.com \
--to=matthew.d.roper@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@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