public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Andrew Morton <akpm@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] dynamic proc fallout
Date: Wed, 21 Apr 2004 13:09:18 -0500	[thread overview]
Message-ID: <20040421180917.GI28459@waste.org> (raw)

Delete obsolete comment and kill test of obsolete define.

Index: tiny/include/linux/proc_fs.h
===================================================================
--- tiny.orig/include/linux/proc_fs.h	2004-04-21 12:49:22.000000000 -0500
+++ tiny/include/linux/proc_fs.h	2004-04-21 13:06:06.000000000 -0500
@@ -24,8 +24,6 @@
 	PROC_ROOT_INO = 1,
 };
 
-/* Finally, the dynamically allocatable proc entries are reserved: */
-
 #define PROC_SUPER_MAGIC 0x9fa0
 
 /*
Index: tiny/arch/alpha/kernel/irq.c
===================================================================
--- tiny.orig/arch/alpha/kernel/irq.c	2004-03-25 13:36:07.000000000 -0600
+++ tiny/arch/alpha/kernel/irq.c	2004-04-21 13:06:06.000000000 -0500
@@ -415,16 +415,12 @@
 #endif
 
 	/*
-	 * Create entries for all existing IRQs. If the number of IRQs
-	 * is greater the 1/4 the total dynamic inode space for /proc,
-	 * don't pollute the inode space
+	 * Create entries for all existing IRQs.
 	 */
-	if (ACTUAL_NR_IRQS < (PROC_NDYNAMIC / 4)) {
-		for (i = 0; i < ACTUAL_NR_IRQS; i++) {
-			if (irq_desc[i].handler == &no_irq_type)
-				continue;
-			register_irq_proc(i);
-		}
+	for (i = 0; i < ACTUAL_NR_IRQS; i++) {
+		if (irq_desc[i].handler == &no_irq_type)
+			continue;
+		register_irq_proc(i);
 	}
 }
 



-- 
Matt Mackall : http://www.selenic.com : Linux development and consulting

                 reply	other threads:[~2004-04-21 18:09 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=20040421180917.GI28459@waste.org \
    --to=mpm@selenic.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /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