Linux Documentation
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jani Nikula <jani.nikula@intel.com>,
	dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: Re: [PATCH 0/3] Documentation/gpu: tables of contents cleanups and fixes
Date: Mon, 11 May 2026 06:14:35 -0600	[thread overview]
Message-ID: <875x4uw3bo.fsf@trenco.lwn.net> (raw)
In-Reply-To: <ad1be55a146a3680ad920588a7cfdbc154b8a4fc@intel.com>

Jani Nikula <jani.nikula@intel.com> writes:

> On Fri, 08 May 2026, Jani Nikula <jani.nikula@intel.com> wrote:
>> Make the GPU documentation slightly easier to navigate.
>
> Maxime, Thomas, Maarten, Jon -
>
> Any preferences which tree to merge this through? I'm thinking either
> drm-misc-next or docs-next.

Usually I stand back from DRM docs, expecting them to go through the DRM
tree.  I can certainly pick up this set if that's best, but I wasn't
expecting to.

Thanks,

jon

      reply	other threads:[~2026-05-11 12:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08 11:12 [PATCH 0/3] Documentation/gpu: tables of contents cleanups and fixes Jani Nikula
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 [this message]

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=875x4uw3bo.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=tzimmermann@suse.de \
    /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