linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Marco Elver <elver@google.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Linux MM <linux-mm@kvack.org>, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm: slab.c: fix kernel-doc warning for __ksize()
Date: Wed, 9 Oct 2019 10:45:15 +0200	[thread overview]
Message-ID: <CANpmjNP3X5A=AUQfAPezGR=ODy_cUkoihjr+J5oBOsMcsL072w@mail.gmail.com> (raw)
In-Reply-To: <68c9fd7d-f09e-d376-e292-c7b2bdf1774d@infradead.org>

On Tue, 8 Oct 2019 at 22:45, Randy Dunlap <rdunlap@infradead.org> wrote:
>
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix kernel-doc warning in mm/slab.c:
>
> ../mm/slab.c:4215: warning: Function parameter or member 'objp' not described in '__ksize'
>
> Also add Return: documentation section for this function.
>
> Fixes: 10d1f8cb3965 ("mm/slab: refactor common ksize KASAN logic into slab_common.c")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Marco Elver <elver@google.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>

Thanks!

Acked-by: Marco Elver <elver@google.com>

> ---
>  mm/slab.c |    3 +++
>  1 file changed, 3 insertions(+)
>
> --- linux-next-20191008.orig/mm/slab.c
> +++ linux-next-20191008/mm/slab.c
> @@ -4207,9 +4207,12 @@ void __check_heap_object(const void *ptr
>
>  /**
>   * __ksize -- Uninstrumented ksize.
> + * @objp: pointer to the object
>   *
>   * Unlike ksize(), __ksize() is uninstrumented, and does not provide the same
>   * safety checks as ksize() with KASAN instrumentation enabled.
> + *
> + * Return: size of the actual memory used by @objp in bytes
>   */
>  size_t __ksize(const void *objp)
>  {
>


      reply	other threads:[~2019-10-09  8:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08 20:45 [PATCH] mm: slab.c: fix kernel-doc warning for __ksize() Randy Dunlap
2019-10-09  8:45 ` Marco Elver [this message]

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='CANpmjNP3X5A=AUQfAPezGR=ODy_cUkoihjr+J5oBOsMcsL072w@mail.gmail.com' \
    --to=elver@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).