linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Harry Yoo <harry.yoo@oracle.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Feng Tang <feng.tang@intel.com>,
	Christoph Lameter <cl@gentwo.org>,
	David Rientjes <rientjes@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	Danilo Krummrich <dakr@kernel.org>
Subject: Re: [PATCH] mm: slub: Wrap krealloc() __GFP_ZERO semantics diagram in literal code block
Date: Tue, 10 Jun 2025 23:20:14 +0900	[thread overview]
Message-ID: <aEg_HtGuJ8Q8G_s8@hyeyoo> (raw)
In-Reply-To: <20250610092153.55093-1-bagasdotme@gmail.com>

On Tue, Jun 10, 2025 at 04:21:53PM +0700, Bagas Sanjaya wrote:
> Sphinx reports htmldocs warnings:
> 
> Documentation/core-api/mm-api:40: ./mm/slub.c:4936: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
> Documentation/core-api/mm-api:40: ./mm/slub.c:4936: ERROR: Undefined substitution referenced: "--------". [docutils]
> 
> Fix the warning by wrapping krealloc() semantics diagram for __GFP_ZERO
> in literal code block.
> 
> Fixes: 489a744e5fb1 ("mm: krealloc: clarify valid usage of __GFP_ZERO")
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---

Hmm not sure what I am missing, but neither `make htmldocs` on my machine
nor docs.kernel.org [1] list kerneldoc for *_noprof() functions properly
(which should have been listed), so no errors show up...

[1] https://docs.kernel.org/core-api/mm-api.html

>  mm/slub.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/mm/slub.c b/mm/slub.c
> index 31e11ef256f90a..45a963e363d32b 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -4930,12 +4930,12 @@ __do_krealloc(const void *p, size_t new_size, gfp_t flags)
>   * 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
> -- 
> An old man doll... just what I always wanted! - Clara
> 

-- 
Cheers,
Harry / Hyeonggon


  reply	other threads:[~2025-06-10 14:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10  9:21 Bagas Sanjaya
2025-06-10 14:20 ` Harry Yoo [this message]
2025-06-10 22:54   ` Bagas Sanjaya
2025-06-10 23:51 ` Matthew Wilcox

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=aEg_HtGuJ8Q8G_s8@hyeyoo \
    --to=harry.yoo@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=bagasdotme@gmail.com \
    --cc=cl@gentwo.org \
    --cc=dakr@kernel.org \
    --cc=feng.tang@intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.com \
    --cc=roman.gushchin@linux.dev \
    --cc=vbabka@suse.cz \
    /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