public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] Remove TODO.rst
Date: Thu, 28 Nov 2019 15:40:34 +0200	[thread overview]
Message-ID: <20191128134034.GW25209@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20191128133646.39183-1-arkadiusz.hiler@intel.com>

On Thu, Nov 28, 2019 at 03:36:46PM +0200, Arkadiusz Hiler wrote:
> All tasks are now captured as GitLab issues:
> 
>  * https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/47
>  * https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/48
>  * https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/49
>  * https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/50
> 
> Cc: Petri Latvala <petri.latvala@intel.com>
> Signed-off-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>

Reviewed-by: Petri Latvala <petri.latvala@intel.com>


> ---
>  TODO.rst | 31 -------------------------------
>  1 file changed, 31 deletions(-)
>  delete mode 100644 TODO.rst
> 
> diff --git a/TODO.rst b/TODO.rst
> deleted file mode 100644
> index eb3e50f1..00000000
> --- a/TODO.rst
> +++ /dev/null
> @@ -1,31 +0,0 @@
> -TODO
> -====
> -
> -This contains a list of refactoring, cleanup and getting-started tasks around
> -the IGT library.
> -
> -Split up igt_kms.c/igt_kms.h
> -----------------------------
> -
> -igt_kms contains both a low-level modeset library, with thin convenience
> -wrappers around core kernel code and libdrm. These functions usually have a
> -drmtest_ prefix (but not all of them).
> -
> -The other part is a higher-level library around the igt_display and related
> -structures. Those usually come with an igt_ prefix.
> -
> -The task would be to split this up, and where necessary, fix up the prefixes to
> -match the level a function operates at.
> -
> -Remove property enums from igt_kms
> -----------------------------------
> -
> -These are just needless indirection for writing tests. We can keep the #defines
> -(since those strings are defacto uapi), but everything else is best handled by
> -runtime-sizing all the arrays.
> -
> -Documentation
> --------------
> -
> -igt documentation is full of warnings and fairly incomplete. Pick a library, and
> -work together with its authors to fix things up.
> -- 
> 2.23.0
> 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

      reply	other threads:[~2019-11-28 13:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28 13:36 [igt-dev] [PATCH i-g-t] Remove TODO.rst Arkadiusz Hiler
2019-11-28 13:40 ` Petri Latvala [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=20191128134034.GW25209@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@intel.com \
    --cc=arkadiusz.hiler@intel.com \
    --cc=igt-dev@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