intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Paul Kocialkowski <paul.kocialkowski@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH IGT v2] Replace mentions of Intel GPU Tools by	IGT GPU Tools
Date: Thu, 15 Jun 2017 22:53:38 +0300	[thread overview]
Message-ID: <87bmppxc1p.fsf@intel.com> (raw)
In-Reply-To: <20170612113340.7750-1-paul.kocialkowski@linux.intel.com>

On Mon, 12 Jun 2017, Paul Kocialkowski <paul.kocialkowski@linux.intel.com> wrote:
> Since IGT supports much more that testing for the Intel DRM driver, it
> was renamed to IGT GPU Tools instead of Intel GPU Tools.
>
> This replaces the remaining mentions of Intel GPU Tools in favor of
> IGT GPU tools.

There's still a bunch of "intel-gpu-tools" references left after this,
though not all of them need to be updated right now.

BR,
Jani.

>
> Signed-off-by: Paul Kocialkowski <paul.kocialkowski@linux.intel.com>
> ---
>  README       | 14 +++++++-------
>  configure.ac |  2 +-
>  2 files changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/README b/README
> index 26171a17..b860ca91 100644
> --- a/README
> +++ b/README
> @@ -1,18 +1,18 @@
> -Intel GPU Tools
> -===============
> +IGT GPU Tools
> +=============
>  
>  Description
>  -----------
>  
> -Intel GPU Tools is a collection of tools for development and testing of the
> -Intel DRM driver. There are many macro-level test suites that get used against
> +IGT GPU Tools is a collection of tools for development and testing of DRM
> +drivers. There are many macro-level test suites that get used against
>  the driver, including xtest, rendercheck, piglit, and oglconform, but failures
>  from those can be difficult to track down to kernel changes, and many require
>  complicated build procedures or specific testing environments to get useful
> -results. Therefore, Intel GPU Tools includes low-level tools and tests
> -specifically for development and testing of the Intel DRM Driver.
> +results. Therefore, IGT GPU Tools includes low-level tools and tests
> +specifically for development and testing of DRM drivers.
>  
> -Intel GPU Tools is split into several sections:
> +IGT GPU Tools is split into several sections:
>  
>  benchmarks/
>  	This is a collection of useful microbenchmarks that can be used to tune
> diff --git a/configure.ac b/configure.ac
> index 0418e605..efc81acb 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -379,7 +379,7 @@ AC_OUTPUT
>  
>  # Print a summary of the compilation
>  echo ""
> -echo "Intel GPU tools"
> +echo "IGT GPU Tools"
>  
>  echo ""
>  echo " • Tests:"

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-06-15 19:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12 11:33 [PATCH IGT v2] Replace mentions of Intel GPU Tools by IGT GPU Tools Paul Kocialkowski
2017-06-15 19:53 ` Jani Nikula [this message]
2017-06-15 20:59   ` Rodrigo Vivi
2017-06-15 21:15     ` Jani Nikula

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=87bmppxc1p.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=paul.kocialkowski@linux.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;
as well as URLs for NNTP newsgroup(s).