Linux Documentation
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.demarchi@intel.com>
To: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	linux-doc@vger.kernel.org
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: [PATCH 2/3] Documentation/gpu: Limit index to maxdepth=2
Date: Mon,  7 Nov 2022 09:32:08 -0800	[thread overview]
Message-ID: <20221107173209.2219571-3-lucas.demarchi@intel.com> (raw)
In-Reply-To: <20221107173209.2219571-1-lucas.demarchi@intel.com>

With a lot of sub-section it's a little bit hard to find the information
needed in the main GPU index. Limit the maxdepth to 2 so it doesn't get
poluted with noise from each driver and from other sections.

Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
---
 Documentation/gpu/index.rst | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/gpu/index.rst b/Documentation/gpu/index.rst
index b99dede9a5b1..1d9402d519be 100644
--- a/Documentation/gpu/index.rst
+++ b/Documentation/gpu/index.rst
@@ -3,6 +3,7 @@ Linux GPU Driver Developer's Guide
 ==================================
 
 .. toctree::
+   :maxdepth: 2
 
    introduction
    drm-internals
-- 
2.38.1


  parent reply	other threads:[~2022-11-07 17:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 17:32 [PATCH 0/3] Documentation/gpu: reduce verbosity in toc Lucas De Marchi
2022-11-07 17:32 ` [PATCH 1/3] Documentation/gpu: Fix section in the wrong scope Lucas De Marchi
2022-11-08  9:49   ` Tvrtko Ursulin
2022-11-15  6:55     ` Lucas De Marchi
2022-11-07 17:32 ` Lucas De Marchi [this message]
2022-11-15  9:48   ` [Intel-gfx] [PATCH 2/3] Documentation/gpu: Limit index to maxdepth=2 Balasubramani Vivekanandan
2022-11-15 17:36     ` Lucas De Marchi
2022-11-07 17:32 ` [PATCH 3/3] Documentation/gpu: Limit drivers " Lucas De Marchi

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=20221107173209.2219571-3-lucas.demarchi@intel.com \
    --to=lucas.demarchi@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=tvrtko.ursulin@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox