From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>,
Dave Airlie <airlied@redhat.com>
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/doc: Add RFC section
Date: Tue, 23 Mar 2021 08:37:07 -0400 [thread overview]
Message-ID: <YFng89ujYxcyJQmN@intel.com> (raw)
In-Reply-To: <20210323084453.366863-2-daniel.vetter@ffwll.ch>
On Tue, Mar 23, 2021 at 09:44:53AM +0100, Daniel Vetter wrote:
> Motivated by the pre-review process for i915 gem/gt features, but
> probably useful in general for complex stuff.
>
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Jason Ekstrand <jason@jlekstrand.net>
> Cc: Dave Airlie <airlied@redhat.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
> Documentation/gpu/index.rst | 1 +
> Documentation/gpu/rfc.rst | 16 ++++++++++++++++
> 2 files changed, 17 insertions(+)
> create mode 100644 Documentation/gpu/rfc.rst
>
> diff --git a/Documentation/gpu/index.rst b/Documentation/gpu/index.rst
> index c9a51e3bfb5a..df58cb826d68 100644
> --- a/Documentation/gpu/index.rst
> +++ b/Documentation/gpu/index.rst
> @@ -16,6 +16,7 @@ Linux GPU Driver Developer's Guide
> vga-switcheroo
> vgaarbiter
> todo
> + rfc
I understand the motivation here so I didn't commented earlier, but looking now,
I'm wondering that this section will polute the official doc...
>
> .. only:: subproject and html
>
> diff --git a/Documentation/gpu/rfc.rst b/Documentation/gpu/rfc.rst
> new file mode 100644
> index 000000000000..9d0ff2921af8
> --- /dev/null
> +++ b/Documentation/gpu/rfc.rst
> @@ -0,0 +1,16 @@
> +===============
> +GPU RFC Section
> +===============
> +
> +For complex work, especially new uapi, it is often good to nail the high level
> +design issues before getting lost in the code details. This section is meant to
> +host such documentation:
> +
> +* Each RFC should be a section in this file, explaining the goal and main design
> + considerations.
> +
> +* For uapi structures add a file to this directory with and then pull the
> + kerneldoc in like with real uapi headers.
> +
> +* Once the code has landed move all the documentation to the right places in
> + the main core, helper or driver sections.
> --
> 2.31.0
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-03-23 12:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 8:44 [Intel-gfx] [PATCH 1/2] drm/i915: add gem/gt TODO Daniel Vetter
2021-03-23 8:44 ` [Intel-gfx] [PATCH 2/2] drm/doc: Add RFC section Daniel Vetter
2021-03-23 12:37 ` Rodrigo Vivi [this message]
2021-03-23 13:10 ` Daniel Vetter
2021-03-23 13:38 ` Rodrigo Vivi
2021-03-23 17:01 ` Simon Ser
2021-03-23 17:55 ` Jason Ekstrand
2021-03-23 18:31 ` Daniel Vetter
2021-03-24 6:32 ` Dave Airlie
2021-03-23 9:05 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915: add gem/gt TODO Patchwork
2021-03-23 9:35 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-03-23 10:13 ` [Intel-gfx] [PATCH 1/2] " Jani Nikula
2021-03-23 11:57 ` Daniel Vetter
2021-03-23 12:34 ` Rodrigo Vivi
2021-03-23 13:18 ` Daniel Vetter
2021-03-23 18:07 ` Jason Ekstrand
2021-03-23 13:17 ` Daniel Vetter
2021-03-24 6:34 ` Dave Airlie
2021-03-24 2:29 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/2] " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2021-03-24 21:10 [Intel-gfx] [PATCH 1/2] " Daniel Vetter
2021-03-24 21:10 ` [Intel-gfx] [PATCH 2/2] drm/doc: Add RFC section Daniel Vetter
2021-03-25 2:37 ` Jason Ekstrand
2021-03-25 9:41 ` Simon Ser
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=YFng89ujYxcyJQmN@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--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