public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>,
	Baolin Liu <liubaolin12138@163.com>,
	skhan@linuxfoundation.org, cyphar@cyphar.com, vbabka@kernel.org,
	surenb@google.com
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-doc@vger.kernel.org, Baolin Liu <liubaolin@kylinos.cn>
Subject: Re: [PATCH v2 v2] Documentation: proc: fix section numbering in table of contents
Date: Mon, 27 Apr 2026 03:55:20 -0600	[thread overview]
Message-ID: <87wlxspw1j.fsf@trenco.lwn.net> (raw)
In-Reply-To: <df3b6729-ed3b-42e3-9a8a-f77ebf827dd7@infradead.org>

Randy Dunlap <rdunlap@infradead.org> writes:

> On 4/24/26 2:06 AM, Baolin Liu wrote:
>> From: Baolin Liu <liubaolin@kylinos.cn>
>> 
>> Commit e24ccaaf7ec4 ("block: remove last remaining traces of IDE
>> documentation") removed the IDE section but left its table of
>> contents entry behind.
>> Fix the stale entry and renumber the following sections.
>> 
>> Fixes: e24ccaaf7ec4 ("block: remove last remaining traces of IDE documentation")
>> Signed-off-by: Baolin Liu <liubaolin@kylinos.cn>
>
> LGTM.
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
>
> I note that the html-generated TOC is already correct;
> e.g., https://docs.kernel.org/filesystems/proc.html#networking-info-in-proc-net
> is already section 1.3.

There are advantages to having a computer do a job like that :)

I do really question the value of these manually maintained TOCs; they
are always going to be out of date.  But ...

> AFAICT, this TOC is for users/readers who use an editor or pager
> to read this file, but the patch is useful in that setting.

Others seem to disagree, so we keep them.

I've applied the patch, thanks.

jon

  reply	other threads:[~2026-04-27  9:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-24  9:06 [PATCH v2 v2] Documentation: proc: fix section numbering in table of contents Baolin Liu
2026-04-24 21:12 ` Randy Dunlap
2026-04-27  9:55   ` Jonathan Corbet [this message]
2026-04-27 17:00     ` Randy Dunlap
     [not found]     ` <9455d5d6-80b7-4c0a-a569-fef3bd9f1529@163.com>
2026-04-28  8:57       ` Jonathan Corbet
2026-04-28 10:36         ` liubaolin

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=87wlxspw1j.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=cyphar@cyphar.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liubaolin12138@163.com \
    --cc=liubaolin@kylinos.cn \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=surenb@google.com \
    --cc=vbabka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox