From: John Levon <levon@movementarian.org>
To: trivial@rustcorp.com.au
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: [PATCH] tiny kmem_cache_destroy doc tweak
Date: Wed, 18 Sep 2002 22:31:39 +0100 [thread overview]
Message-ID: <20020918213139.GA21178@compsoc.man.ac.uk> (raw)
Make it clear that _destroy() won't do the kmem_cache_free()s for you (it seems).
Against 2.5.36
thanks
john
--- linux-linus/mm/slab.c Wed Sep 18 19:48:54 2002
+++ linux/mm/slab.c Wed Sep 18 22:27:32 2002
@@ -1018,6 +1018,8 @@
* cache being allocated each time a module is loaded and unloaded, if the
* module doesn't have persistent in-kernel storage across loads and unloads.
*
+ * The cache must be empty before calling this function.
+ *
* The caller must guarantee that noone will allocate memory from the cache
* during the kmem_cache_destroy().
*/
reply other threads:[~2002-09-18 21:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020918213139.GA21178@compsoc.man.ac.uk \
--to=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=trivial@rustcorp.com.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
all inboxes | Powered by JetHome®