From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org
Cc: jani.nikula@intel.com
Subject: [PATCH 0/3] Documentation/gpu: tables of contents cleanups and fixes
Date: Fri, 8 May 2026 14:12:06 +0300 [thread overview]
Message-ID: <cover.1778238671.git.jani.nikula@intel.com> (raw)
Make the GPU documentation slightly easier to navigate.
Jani Nikula (3):
Documentation/gpu: limit main toctree depth to 2
Documentation/gpu: add some tables of contents to large documents
Documentation/gpu/rfc: fix toctree
Documentation/gpu/driver-uapi.rst | 2 ++
Documentation/gpu/drm-internals.rst | 2 ++
Documentation/gpu/drm-kms-helpers.rst | 2 ++
Documentation/gpu/drm-kms.rst | 2 ++
Documentation/gpu/drm-mm.rst | 2 ++
Documentation/gpu/drm-ras.rst | 2 ++
Documentation/gpu/drm-uapi.rst | 4 +++-
Documentation/gpu/drm-usage-stats.rst | 2 ++
Documentation/gpu/index.rst | 1 +
Documentation/gpu/introduction.rst | 2 ++
Documentation/gpu/rfc/index.rst | 26 ++++++--------------------
11 files changed, 26 insertions(+), 21 deletions(-)
--
2.47.3
next reply other threads:[~2026-05-08 11:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 11:12 Jani Nikula [this message]
2026-05-08 11:12 ` [PATCH 1/3] Documentation/gpu: limit main toctree depth to 2 Jani Nikula
2026-05-08 18:37 ` Randy Dunlap
2026-05-08 11:12 ` [PATCH 2/3] Documentation/gpu: add some tables of contents to large documents Jani Nikula
2026-05-08 18:37 ` Randy Dunlap
2026-05-08 11:12 ` [PATCH 3/3] Documentation/gpu/rfc: fix toctree Jani Nikula
2026-05-08 18:36 ` Randy Dunlap
2026-05-11 8:50 ` [PATCH 0/3] Documentation/gpu: tables of contents cleanups and fixes Jani Nikula
2026-05-11 12:14 ` Jonathan Corbet
2026-05-13 8:20 ` 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=cover.1778238671.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.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 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.