From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: rdunlap@infradead.org, sfr@canb.auug.org.au,
kent.overstreet@linux.dev, surenb@google.com,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 6/6] Documentation: mm/slab: undo _noprof additions in the documentation
Date: Tue, 26 Mar 2024 16:14:52 -0700 [thread overview]
Message-ID: <20240326231453.1206227-7-surenb@google.com> (raw)
In-Reply-To: <20240326231453.1206227-1-surenb@google.com>
With kernel-doc script change to handle xyz_noprof() names, the previous
documentation changes and not needed anymore.
Fixes: bc7b83f5e4bf ("mm/slab: enable slab allocation tagging for kmalloc and friends")
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Cc: linux-doc@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>
Cc: Kent Overstreet <kent.overstreet@linux.dev>
---
mm/slub.c | 2 +-
mm/util.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/mm/slub.c b/mm/slub.c
index 7b68a3451eb9..be047279c9e9 100644
--- a/mm/slub.c
+++ b/mm/slub.c
@@ -4091,7 +4091,7 @@ void *kmem_cache_alloc_lru_noprof(struct kmem_cache *s, struct list_lru *lru,
EXPORT_SYMBOL(kmem_cache_alloc_lru_noprof);
/**
- * kmem_cache_alloc_node_noprof - Allocate an object on the specified node
+ * kmem_cache_alloc_node - Allocate an object on the specified node
* @s: The cache to allocate from.
* @gfpflags: See kmalloc().
* @node: node number of the target node.
diff --git a/mm/util.c b/mm/util.c
index 73703d6cd3dc..a9e911b22b99 100644
--- a/mm/util.c
+++ b/mm/util.c
@@ -115,7 +115,7 @@ char *kstrndup(const char *s, size_t max, gfp_t gfp)
EXPORT_SYMBOL(kstrndup);
/**
- * kmemdup_noprof - duplicate region of memory
+ * kmemdup - duplicate region of memory
*
* @src: memory region to duplicate
* @len: memory region length
@@ -594,7 +594,7 @@ unsigned long vm_mmap(struct file *file, unsigned long addr,
EXPORT_SYMBOL(vm_mmap);
/**
- * kvmalloc_node_noprof - attempt to allocate physically contiguous memory, but upon
+ * kvmalloc_node - attempt to allocate physically contiguous memory, but upon
* failure, fall back to non-contiguous (vmalloc) allocation.
* @size: size of the request.
* @flags: gfp mask for the allocation - must be compatible (superset) with GFP_KERNEL.
--
2.44.0.396.g6e790dbe36-goog
next prev parent reply other threads:[~2024-03-26 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 23:14 [PATCH 0/6] Documentation fixes for memory allocation profiling Suren Baghdasaryan
2024-03-26 23:14 ` [PATCH 1/6] Documentation: rhashtable: undo _noprof additions in the documentation Suren Baghdasaryan
2024-03-26 23:14 ` [PATCH 2/6] Documentation: mm: " Suren Baghdasaryan
2024-03-26 23:14 ` [PATCH 3/6] Documentation: mempool: " Suren Baghdasaryan
2024-03-26 23:14 ` [PATCH 4/6] Documentation: mm: vmalloc: " Suren Baghdasaryan
2024-03-26 23:14 ` [PATCH 5/6] Documentation: mm: percpu: " Suren Baghdasaryan
2024-03-26 23:14 ` Suren Baghdasaryan [this message]
2024-03-27 4:30 ` [PATCH 0/6] Documentation fixes for memory allocation profiling Randy Dunlap
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=20240326231453.1206227-7-surenb@google.com \
--to=surenb@google.com \
--cc=akpm@linux-foundation.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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