dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Leandro Ribeiro <leandrohr@riseup.net>
Cc: airlied@linux.ie, lkcamp@lists.libreplanetbr.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/doc: Update IGT documentation
Date: Mon, 4 Nov 2019 19:06:28 +0100	[thread overview]
Message-ID: <20191104180628.GO10326@phenom.ffwll.local> (raw)
In-Reply-To: <20191030011211.47942-1-leandrohr@riseup.net>

On Tue, Oct 29, 2019 at 10:12:11PM -0300, Leandro Ribeiro wrote:
> The IGT documentation in this page is telling us to build it using
> make. According to commit 67993c1 ("automake: Point builders at
> meson") from the IGT project, this is deprecated and IGT should be
> built with meson. Instead of having a documentation for IGT in this
> page, point to their GitLab README, which should always be up to
> date.
> 
> Signed-off-by: Leandro Ribeiro <leandrohr@riseup.net>

Uh, docs just don't age well :-(

Thanks for your patch, applied.
-Daniel

> ---
>  Documentation/gpu/drm-uapi.rst | 32 ++------------------------------
>  1 file changed, 2 insertions(+), 30 deletions(-)
> 
> diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst
> index 94f90521f58c..996f7354e05c 100644
> --- a/Documentation/gpu/drm-uapi.rst
> +++ b/Documentation/gpu/drm-uapi.rst
> @@ -254,36 +254,8 @@ Validating changes with IGT
>  There's a collection of tests that aims to cover the whole functionality of
>  DRM drivers and that can be used to check that changes to DRM drivers or the
>  core don't regress existing functionality. This test suite is called IGT and
> -its code can be found in https://cgit.freedesktop.org/drm/igt-gpu-tools/.
> -
> -To build IGT, start by installing its build dependencies. In Debian-based
> -systems::
> -
> -	# apt-get build-dep intel-gpu-tools
> -
> -And in Fedora-based systems::
> -
> -	# dnf builddep intel-gpu-tools
> -
> -Then clone the repository::
> -
> -	$ git clone git://anongit.freedesktop.org/drm/igt-gpu-tools
> -
> -Configure the build system and start the build::
> -
> -	$ cd igt-gpu-tools && ./autogen.sh && make -j6
> -
> -Download the piglit dependency::
> -
> -	$ ./scripts/run-tests.sh -d
> -
> -And run the tests::
> -
> -	$ ./scripts/run-tests.sh -t kms -t core -s
> -
> -run-tests.sh is a wrapper around piglit that will execute the tests matching
> -the -t options. A report in HTML format will be available in
> -./results/html/index.html. Results can be compared with piglit.
> +its code and instructions to build and run can be found in
> +https://gitlab.freedesktop.org/drm/igt-gpu-tools/.
>  
>  Display CRC Support
>  -------------------
> -- 
> 2.23.0
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2019-11-04 18:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30  1:12 [PATCH] drm/doc: Update IGT documentation Leandro Ribeiro
2019-11-04 18:06 ` Daniel Vetter [this message]

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=20191104180628.GO10326@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=leandrohr@riseup.net \
    --cc=lkcamp@lists.libreplanetbr.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