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 1/6] Documentation: rhashtable: undo _noprof additions in the documentation
Date: Tue, 26 Mar 2024 16:14:47 -0700 [thread overview]
Message-ID: <20240326231453.1206227-2-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: 11c91be0e244 ("rhashtable: plumb through alloc tag")
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>
---
lib/rhashtable.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lib/rhashtable.c b/lib/rhashtable.c
index 35d841cf2b43..dbbed19f8fff 100644
--- a/lib/rhashtable.c
+++ b/lib/rhashtable.c
@@ -979,7 +979,7 @@ static u32 rhashtable_jhash2(const void *key, u32 length, u32 seed)
}
/**
- * rhashtable_init_noprof - initialize a new hash table
+ * rhashtable_init - initialize a new hash table
* @ht: hash table to be initialized
* @params: configuration parameters
*
@@ -1085,13 +1085,13 @@ int rhashtable_init_noprof(struct rhashtable *ht,
EXPORT_SYMBOL_GPL(rhashtable_init_noprof);
/**
- * rhltable_init_noprof - initialize a new hash list table
+ * rhltable_init - initialize a new hash list table
* @hlt: hash list table to be initialized
* @params: configuration parameters
*
* Initializes a new hash list table.
*
- * See documentation for rhashtable_init_noprof.
+ * See documentation for rhashtable_init.
*/
int rhltable_init_noprof(struct rhltable *hlt, const struct rhashtable_params *params)
{
--
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 ` Suren Baghdasaryan [this message]
2024-03-26 23:14 ` [PATCH 2/6] Documentation: mm: undo _noprof additions in the documentation 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 ` [PATCH 6/6] Documentation: mm/slab: " Suren Baghdasaryan
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-2-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