From: Jeremy Bobbin <jer@jer.cx>
To: corbet@lwn.net
Cc: linux-doc@vger.kernel.org, Jeremy Bobbin <jer@jer.cx>
Subject: [PATCH] fix broken links in bpf, driver_api & filesystem documentation
Date: Mon, 4 May 2026 18:48:38 -0700 [thread overview]
Message-ID: <20260505014839.2670290-1-jer@jer.cx> (raw)
bpf/linux-notes.rst: broken link to ISA standard documentation
driver-api/thermal/intel_dptf.rst: two broken links to filesystem quota
Signed-off-by: Jeremy Bobbin <jer@jer.cx>
---
Documentation/bpf/linux-notes.rst | 2 +-
Documentation/driver-api/thermal/intel_dptf.rst | 2 +-
Documentation/filesystems/ext4/super.rst | 6 +++---
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/bpf/linux-notes.rst b/Documentation/bpf/linux-notes.rst
index 00d2693de025..9c7b703ae4e5 100644
--- a/Documentation/bpf/linux-notes.rst
+++ b/Documentation/bpf/linux-notes.rst
@@ -46,7 +46,7 @@ Legacy BPF Packet access instructions
=====================================
As mentioned in the `ISA standard documentation
-<instruction-set.html#legacy-bpf-packet-access-instructions>`_,
+<standardization/instruction-set.html#legacy-bpf-packet-access-instructions>`_,
Linux has special eBPF instructions for access to packet data that have been
carried over from classic BPF to retain the performance of legacy socket
filters running in the eBPF interpreter.
diff --git a/Documentation/driver-api/thermal/intel_dptf.rst b/Documentation/driver-api/thermal/intel_dptf.rst
index 4adfa1eb74db..1a4d7eedbb68 100644
--- a/Documentation/driver-api/thermal/intel_dptf.rst
+++ b/Documentation/driver-api/thermal/intel_dptf.rst
@@ -81,7 +81,7 @@ DPTF ACPI Drivers interface
``data_vault`` (RO)
Binary thermal table. Refer to
- https:/github.com/intel/thermal_daemon for decoding
+ https://github.com/intel/thermal_daemon for decoding
thermal table.
``production_mode`` (RO)
diff --git a/Documentation/filesystems/ext4/super.rst b/Documentation/filesystems/ext4/super.rst
index 9a59cded9bd7..d06e4ae96d16 100644
--- a/Documentation/filesystems/ext4/super.rst
+++ b/Documentation/filesystems/ext4/super.rst
@@ -408,11 +408,11 @@ The ext4 superblock is laid out as follows in
* - 0x240
- __le32
- s_usr_quota_inum
- - Inode number of user `quota <quota>`__ file.
+ - Inode number of user `quota </filesystems/quota.html>`__ file.
* - 0x244
- __le32
- s_grp_quota_inum
- - Inode number of group `quota <quota>`__ file.
+ - Inode number of group `quota </filesystems/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 </filesystems/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
--
2.53.0
next reply other threads:[~2026-05-05 1:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 1:48 Jeremy Bobbin [this message]
2026-05-05 3:43 ` [PATCH] fix broken links in bpf, driver_api & filesystem documentation Randy Dunlap
2026-05-05 3:48 ` Randy Dunlap
2026-05-05 5:23 ` Bagas Sanjaya
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=20260505014839.2670290-1-jer@jer.cx \
--to=jer@jer.cx \
--cc=corbet@lwn.net \
--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