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 0/3] Documentation/gpu: reduce verbosity in toc
Date: Mon,  7 Nov 2022 09:32:06 -0800	[thread overview]
Message-ID: <20221107173209.2219571-1-lucas.demarchi@intel.com> (raw)

Checking some issues I was having i915 doc made me look at the toc for
Documentation/gpu. I think it's too hard to read when extending the toc
all levels for each driver. Reduce it to maxdepth=2.

Also fix the usage-stats section appearing in the wrong place.

Lucas De Marchi (3):
  Documentation/gpu: Fix section in the wrong scope
  Documentation/gpu: Limit index to maxdepth=2
  Documentation/gpu: Limit drivers index to maxdepth=2

 Documentation/gpu/drivers.rst         | 1 +
 Documentation/gpu/drm-usage-stats.rst | 1 -
 Documentation/gpu/index.rst           | 1 +
 3 files changed, 2 insertions(+), 1 deletion(-)

-- 
2.38.1


             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 Lucas De Marchi [this message]
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 ` [PATCH 2/3] Documentation/gpu: Limit index to maxdepth=2 Lucas De Marchi
2022-11-15  9:48   ` [Intel-gfx] " 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-1-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