From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: IGT development <igt-dev@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>,
Petri Latvala <petri.latvala@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] Add TODO.rst
Date: Thu, 11 Oct 2018 10:26:43 -0700 [thread overview]
Message-ID: <20181011172638.GC4205@intel.com> (raw)
In-Reply-To: <20181011163632.14507-1-daniel.vetter@ffwll.ch>
On Thu, Oct 11, 2018 at 06:36:32PM +0200, Daniel Vetter wrote:
> First attempt at collecting a bunch of cleanup tasks. I think using
> the kernel as an example, it's much better if we keep these here than
> in our own internal $bug_db instance.
>
> v2: Fix typo (Rodrigo).
>
> Cc: Petri Latvala <petri.latvala@intel.com>
> Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> TODO.rst | 31 +++++++++++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
> create mode 100644 TODO.rst
>
> diff --git a/TODO.rst b/TODO.rst
> new file mode 100644
> index 000000000000..eb3e50f14ed4
> --- /dev/null
> +++ b/TODO.rst
> @@ -0,0 +1,31 @@
> +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.19.1
>
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-10-11 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 16:36 [igt-dev] [PATCH i-g-t] Add TODO.rst Daniel Vetter
2018-10-11 17:05 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-10-11 17:26 ` Rodrigo Vivi [this message]
2018-10-11 22:03 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=20181011172638.GC4205@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.