From: Hyeonggon Yoo <42.hyeyoo@gmail.com>
To: Thorsten Scherer <t.scherer@eckelmann.de>
Cc: 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>,
Yury Norov <yury.norov@gmail.com>, Ingo Molnar <mingo@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slab: Adjust comment after refactoring of gfp.h
Date: Mon, 13 Mar 2023 04:04:29 +0000 [thread overview]
Message-ID: <ZA6gzTvu6M/JQof4@localhost> (raw)
In-Reply-To: <20230312122315.3562-1-t.scherer@eckelmann.de>
On Sun, Mar 12, 2023 at 01:23:15PM +0100, Thorsten Scherer wrote:
> Reflect the change from the commit below.
>
> Fixes: cb5a065b4ea9 ("headers/deps: mm: Split <linux/gfp_types.h> out of <linux/gfp.h>")
> Signed-off-by: Thorsten Scherer <t.scherer@eckelmann.de>
> ---
> include/linux/slab.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/slab.h b/include/linux/slab.h
> index 45af70315a94..87d687c43d8c 100644
> --- a/include/linux/slab.h
> +++ b/include/linux/slab.h
> @@ -526,7 +526,7 @@ void *kmalloc_large_node(size_t size, gfp_t flags, int node) __assume_page_align
> * to be at least to the size.
> *
> * The @flags argument may be one of the GFP flags defined at
> - * include/linux/gfp.h and described at
> + * include/linux/gfp_types.h and described at
> * :ref:`Documentation/core-api/mm-api.rst <mm-api-gfp-flags>`
Acked-by: Hyeonggon Yoo <42.hyeyoo@gmail.com>
> *
> * The recommended usage of the @flags is described at
> --
> 2.38.0
>
next prev parent reply other threads:[~2023-03-13 4:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 12:23 [PATCH] slab: Adjust comment after refactoring of gfp.h Thorsten Scherer
2023-03-13 4:04 ` Hyeonggon Yoo [this message]
2023-03-13 13:52 ` Vlastimil Babka
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=ZA6gzTvu6M/JQof4@localhost \
--to=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=mingo@kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=t.scherer@eckelmann.de \
--cc=vbabka@suse.cz \
--cc=yury.norov@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.