From: R Sundar <prosunofficial@gmail.com>
To: Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Roman Gushchin <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Removed @freeptr_offset to prevent doc warning
Date: Sun, 1 Sep 2024 11:48:14 +0530 [thread overview]
Message-ID: <7d4d860e-6d0a-4144-acbc-45a328df48fe@gmail.com> (raw)
In-Reply-To: <20240901055311.20905-1-prosunofficial@gmail.com>
On 01/09/24 11:23, R Sundar wrote:
> ./mm/slab_common.c:385: warning: Excess function parameter 'freeptr_offset' description in 'kmem_cache_create_usercopy'
> Removed @freeptr_offset to fix above doc warning.
>
> Signed-off-by: R Sundar <prosunofficial@gmail.com>
> ---
> mm/slab_common.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/mm/slab_common.c b/mm/slab_common.c
> index d48ef4fe1ea8..ad438ba62485 100644
> --- a/mm/slab_common.c
> +++ b/mm/slab_common.c
> @@ -353,7 +353,6 @@ do_kmem_cache_create_usercopy(const char *name,
> * for copying to userspace
> * @name: A string which is used in /proc/slabinfo to identify this cache.
> * @size: The size of objects to be created in this cache.
> - * @freeptr_offset: Custom offset for the free pointer in RCU caches
> * @align: The required alignment for the objects.
> * @flags: SLAB flags
> * @useroffset: Usercopy region offset
Sorry , Forget to mention.
This patch is for linux-next repository.
Thanks,
Sundar
next prev parent reply other threads:[~2024-09-01 6:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-01 5:53 R Sundar
2024-09-01 6:18 ` R Sundar [this message]
2024-09-01 19:26 ` Vlastimil Babka
2024-09-02 2:12 ` R Sundar
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=7d4d860e-6d0a-4144-acbc-45a328df48fe@gmail.com \
--to=prosunofficial@gmail.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.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