From: Randy Dunlap <rdunlap@infradead.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>, Jeremy Bobbin <jer@jer.cx>,
corbet@lwn.net
Cc: linux-doc@vger.kernel.org
Subject: Re: [PATCH] fix broken links in bpf, driver_api & filesystem documentation
Date: Mon, 4 May 2026 22:56:45 -0700 [thread overview]
Message-ID: <f7950aaa-8b0b-499d-a421-134593ffaec0@infradead.org> (raw)
In-Reply-To: <afl-79jS4RiGpx_c@archie.me>
On 5/4/26 10:23 PM, Bagas Sanjaya wrote:
> On Mon, May 04, 2026 at 06:48:38PM -0700, Jeremy Bobbin wrote:
>> @@ -712,7 +712,7 @@ the following:
>> * - 0x80
>> - This filesystem has a snapshot (RO_COMPAT_HAS_SNAPSHOT).
>> * - 0x100
>> - - `Quota <Quota>`__ (RO_COMPAT_QUOTA).
>> + - `Quota </filesystems/quota.html>`__ (RO_COMPAT_QUOTA).
>
> Maybe :doc:`Quota </filesystems/quota>`?
>
> Thanks.
I just tried that - unsuccessfully. (Maybe because this is in
a table?)
What works for me is this: (FWIW)
--- linux-next-20260504.orig/Documentation/filesystems/ext4/super.rst
+++ linux-next-20260504/Documentation/filesystems/ext4/super.rst
@@ -408,11 +408,11 @@ The ext4 superblock is laid out as follo
* - 0x240
- __le32
- s_usr_quota_inum
- - Inode number of user `quota <quota>`__ file.
+ - Inode number of user `quota <../quota.html>`__ file.
* - 0x244
- __le32
- s_grp_quota_inum
- - Inode number of group `quota <quota>`__ file.
+ - Inode number of group `quota <../quota.html>`__ file.
* - 0x248
- __le32
- s_overhead_blocks
@@ -712,7 +712,7 @@ the following:
* - 0x80
- This filesystem has a snapshot (RO_COMPAT_HAS_SNAPSHOT).
* - 0x100
- - `Quota <Quota>`__ (RO_COMPAT_QUOTA).
+ - `Quota <../quota.html>`__ (RO_COMPAT_QUOTA).
* - 0x200
- This filesystem supports “bigalloc”, which means that file extents are
tracked in units of clusters (of blocks) instead of blocks
--
~Randy
prev parent reply other threads:[~2026-05-05 5:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 1:48 [PATCH] fix broken links in bpf, driver_api & filesystem documentation Jeremy Bobbin
2026-05-05 3:43 ` Randy Dunlap
2026-05-05 3:48 ` Randy Dunlap
2026-05-05 5:23 ` Bagas Sanjaya
2026-05-05 5:56 ` Randy Dunlap [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=f7950aaa-8b0b-499d-a421-134593ffaec0@infradead.org \
--to=rdunlap@infradead.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=jer@jer.cx \
--cc=linux-doc@vger.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