From: Sanjay Chitroda <sanjayembeddedse@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@gentwo.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Harry Yoo <harry.yoo@oracle.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Sanjay Chitroda <sanjayembeddedse@gmail.com>
Subject: Re: [PATCH] mm/slub: drop duplicate kernel-doc for ksize()
Date: Mon, 23 Feb 2026 18:51:47 +0530 [thread overview]
Message-ID: <20260223132147.1582608-1-sanjayembedded@gmail.com> (raw)
In-Reply-To: <00fc801f-6a11-4510-2b77-a683e5e37c77@google.com>
> The header file kernel-doc looks equivalent without mentioning that it
> returns bytes. Might be best to make that clear in slab.h?
shall we add dedicated change in slab.h to add return bytes information?
this would keep this change as clean, what do you suggest?
next prev parent reply other threads:[~2026-02-23 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 12:42 Sanjay Chitroda
2026-02-22 3:47 ` David Rientjes
2026-02-23 13:21 ` Sanjay Chitroda [this message]
2026-02-23 15:16 ` 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=20260223132147.1582608-1-sanjayembedded@gmail.com \
--to=sanjayembeddedse@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=harry.yoo@oracle.com \
--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