mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] TRIVIAL: rwhron@earthlink.net: remove space in cache names
Date: Mon, 03 Jun 2002 16:12:02 +1000	[thread overview]
Message-ID: <E17El4U-0007ha-00@wagner.rustcorp.com.au> (raw)

rwhron@earthlink.net: remove space in _proc_slabinfo cache_name:
  Most /proc/slabinfo cache_names are in the format:
  cache_name.  There are a couple with spaces in the
  name, which is inconsistent and requires a special case
  when scripting.
  
  Changes "fasync cache" and "file lock cache" to have
  the usual underscore.
  
  Tested on 2.5.18.  Applies to 2.4.19-pre8 with offset.
  

--- trivial-2.5.20/fs/fcntl.c.orig	Mon Jun  3 15:25:18 2002
+++ trivial-2.5.20/fs/fcntl.c	Mon Jun  3 15:25:18 2002
@@ -551,7 +551,7 @@
 
 static int __init fasync_init(void)
 {
-	fasync_cache = kmem_cache_create("fasync cache",
+	fasync_cache = kmem_cache_create("fasync_cache",
 		sizeof(struct fasync_struct), 0, 0, NULL, NULL);
 	if (!fasync_cache)
 		panic("cannot create fasync slab cache");
--- trivial-2.5.20/fs/locks.c.orig	Mon Jun  3 15:25:18 2002
+++ trivial-2.5.20/fs/locks.c	Mon Jun  3 15:25:18 2002
@@ -1940,7 +1940,7 @@
 
 static int __init filelock_init(void)
 {
-	filelock_cache = kmem_cache_create("file lock cache",
+	filelock_cache = kmem_cache_create("file_lock_cache",
 			sizeof(struct file_lock), 0, 0, init_once, NULL);
 	if (!filelock_cache)
 		panic("cannot create file lock slab cache");

--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

             reply	other threads:[~2002-06-03  6:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-03  6:12 Rusty Russell [this message]
2002-06-03  5:20 ` Martin Dalecki
2002-06-03 10:31   ` Daniel Phillips
2002-06-03  7:20 rwhron

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=E17El4U-0007ha-00@wagner.rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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 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®