From: Bagas Sanjaya <bagasdotme@gmail.com>
To: 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: Tue, 5 May 2026 12:23:59 +0700 [thread overview]
Message-ID: <afl-79jS4RiGpx_c@archie.me> (raw)
In-Reply-To: <20260505014839.2670290-1-jer@jer.cx>
[-- Attachment #1: Type: text/plain, Size: 434 bytes --]
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.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-05-05 5:24 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 [this message]
2026-05-05 5:56 ` Randy Dunlap
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=afl-79jS4RiGpx_c@archie.me \
--to=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