public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: liubaolin <liubaolin12138@163.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	corbet@lwn.net, skhan@linuxfoundation.org, surenb@google.com,
	cyphar@cyphar.com, witcher@wiredspace.de
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-doc@vger.kernel.org, wangguanyu@vivo.com,
	Baolin Liu <liubaolin@kylinos.cn>
Subject: Re: [PATCH v1 v1] Documentation: proc: fix ext4 section numbering in table of contents
Date: Fri, 24 Apr 2026 14:53:54 +0800	[thread overview]
Message-ID: <255bdd69-e0f0-4300-864a-15fd077ea748@163.com> (raw)
In-Reply-To: <8668e0f3-49c1-4748-97ab-00ee2befde10@infradead.org>



在 2026/4/24 10:54, Randy Dunlap 写道:
> 
> 
> On 4/23/26 7:44 PM, liubaolin wrote:
>>
>>
>> 在 2026/4/23 23:55, Randy Dunlap 写道:
>>> Hi--
>>>
>>> Why is "ext4" in the Subject?
>>> Probably just drop that word?

Dear Randy Dunlap,
    I apologize for missing the first part of your email. You're right, 
the commit message title should remove the word"ext4". I will submit a 
v2 patch to fix this error later. Thank you for your review.

Thanks,
Baolin

>>>
>>>
>>> On 4/22/26 11:56 PM, 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>
>>>> ---
>>>>    Documentation/filesystems/proc.rst | 14 +++++++-------
>>>>    1 file changed, 7 insertions(+), 7 deletions(-)
>>>>
>>>> diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
>>>> index 7ce02573a3d9..70db35987ee1 100644
>>>> --- a/Documentation/filesystems/proc.rst
>>>> +++ b/Documentation/filesystems/proc.rst
>>>> @@ -23,13 +23,13 @@ fixes/update part 1.1  Stefani Seibold <stefani@seibold.net>    June 9 2009
>>>>      1    Collecting System Information
>>>>      1.1    Process-Specific Subdirectories
>>>>      1.2    Kernel data
>>>> -  1.3    IDE devices in /proc/ide
>>>> -  1.4    Networking info in /proc/net
>>>> -  1.5    SCSI info
>>>> -  1.6    Parallel port info in /proc/parport
>>>> -  1.7    TTY info in /proc/tty
>>>> -  1.8    Miscellaneous kernel statistics in /proc/stat
>>>> -  1.9    Ext4 file system parameters
>>>> +  1.3    Networking info in /proc/net
>>>> +  1.4    SCSI info
>>>> +  1.5    Parallel port info in /proc/parport
>>>> +  1.6    TTY info in /proc/tty
>>>> +  1.7    Miscellaneous kernel statistics in /proc/stat
>>>> +  1.8    Ext4 file system parameters
>>>> +  1.9    /proc/consoles - Shows registered system consoles
>>>>        2    Modifying System Parameters
>>>>    
>>>
>>> Where/how is this Table of Contents used?
>>>
>>> But yes, the intent of the patch is good.
>>> Thanks.
>>>
>> Hello, this directory contains the subsequent content of the file proc.rst.
>>
>> My modification is due to a previous commit e24ccaaf7ec4 ("block: remove last remaining traces of IDE documentation")
>> which removed "1.3 IDE devices in /proc/ide" from the subsequent content and modified the labels of the various items.
>> However, this previous commit forgot to remove "1.3 IDE devices in /proc/ide" from the directory itself.
>> This caused a misalignment between the directory entry and the actual subsequent content items.
>>
>> My modification is to remove the "1.3 IDE devices in /proc/ide" that was forgotten in the previous commit and correct the labels of the other subsequent items.
> 
> Yes, I understood all of that, but I had questions (which you ignored).
> 



      reply	other threads:[~2026-04-24  6:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23  6:56 [PATCH v1 v1] Documentation: proc: fix ext4 section numbering in table of contents Baolin Liu
2026-04-23 15:55 ` Randy Dunlap
2026-04-24  2:44   ` liubaolin
2026-04-24  2:54     ` Randy Dunlap
2026-04-24  6:53       ` liubaolin [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=255bdd69-e0f0-4300-864a-15fd077ea748@163.com \
    --to=liubaolin12138@163.com \
    --cc=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=liubaolin@kylinos.cn \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=surenb@google.com \
    --cc=wangguanyu@vivo.com \
    --cc=witcher@wiredspace.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