summaryrefslogtreecommitdiff
path: root/mm
diff options
context:
space:
mode:
authorJonathan Corbet <corbet@lwn.net>2025-06-11 16:59:08 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-08-15 16:38:38 +0200
commit0f22ddce67d405f9280ff5339841877b6373a615 (patch)
treeab309450568ae5d371a219b6e71b0f0d267745e1 /mm
parentedba98f39b49d79f93232745b0a631a737f60e91 (diff)
downloadlinux-0f22ddce67d405f9280ff5339841877b6373a615.tar.gz
linux-0f22ddce67d405f9280ff5339841877b6373a615.tar.bz2
linux-0f22ddce67d405f9280ff5339841877b6373a615.zip
slub: Fix a documentation build error for krealloc()
[ Upstream commit e8a45f198e3ae2434108f815bc28f37f6fe6742b ] The kerneldoc comment for krealloc() contains an unmarked literal block, leading to these warnings in the docs build: ./mm/slub.c:4936: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils] ./mm/slub.c:4936: ERROR: Undefined substitution referenced: "--------". [docutils] Mark up and indent the block properly to bring a bit of peace to our build logs. Fixes: 489a744e5fb1 (mm: krealloc: clarify valid usage of __GFP_ZERO) Signed-off-by: Jonathan Corbet <corbet@lwn.net> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org> Link: https://patch.msgid.link/20250611155916.2579160-6-willy@infradead.org Signed-off-by: Vlastimil Babka <vbabka@suse.cz> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'mm')
-rw-r--r--mm/slub.c10
1 files changed, 5 insertions, 5 deletions
diff --git a/mm/slub.c b/mm/slub.c
index 31e11ef256f9..45a963e363d3 100644
--- a/mm/slub.c
+++ b/mm/slub.c
@@ -4930,12 +4930,12 @@ alloc_new:
* When slub_debug_orig_size() is off, krealloc() only knows about the bucket
* size of an allocation (but not the exact size it was allocated with) and
* hence implements the following semantics for shrinking and growing buffers
- * with __GFP_ZERO.
+ * with __GFP_ZERO::
*
- * new bucket
- * 0 size size
- * |--------|----------------|
- * | keep | zero |
+ * new bucket
+ * 0 size size
+ * |--------|----------------|
+ * | keep | zero |
*
* Otherwise, the original allocation size 'orig_size' could be used to
* precisely clear the requested size, and the new size will also be stored