From: Mike Fedyk <mfedyk@matchmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Fix for duplicate /proc entries
Date: Fri, 8 Feb 2002 09:47:30 -0800 [thread overview]
Message-ID: <20020208174730.GA343@mis-mike-wstn> (raw)
In-Reply-To: <Pine.LNX.4.33.0202072243560.26015-100000@Appserv.suse.de> <20020208094911.F7930-100000@ozma.union.utexas.edu>
In-Reply-To: <20020208094911.F7930-100000@ozma.union.utexas.edu>
On Fri, Feb 08, 2002 at 10:13:26AM -0600, Brent Cook wrote:
> Maybe, someday there will be some sort of DEBUG flag to set in the kernel,
> from which a slew of asserts and printk's will spring to life, pointing
> out inconsistencies and bad assumptions. That is where this check would
> probably work the best.
>
Actually, there are seperate debug config options for different subsystems,
and I think that is good. The real problem is finding a way to add another
debug config option for procfs without littering the code with ifdefs...
Mike
next prev parent reply other threads:[~2002-02-08 17:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 3:52 Brent Cook
2002-02-06 18:11 ` Dave Jones
2002-02-07 21:38 ` Brent Cook
2002-02-07 21:45 ` Dave Jones
2002-02-08 16:13 ` Brent Cook
2002-02-08 17:47 ` Mike Fedyk [this message]
2002-02-08 17:54 ` Alexander Viro
2002-02-08 18:12 ` Tommy Reynolds
2002-06-14 22:30 ` File permission problem with NFSv3 and 2.5.20-dj4 Brent Cook
2002-06-15 12:23 ` Dave Jones
2002-06-19 17:45 ` Brent Cook
2002-06-19 17:48 ` Dave Jones
2002-06-19 17:52 ` another sched.c error with athlon Kirk Reiser
2002-06-19 18:27 ` Adrian Bunk
2002-04-10 14:02 ` Mouse interrupts: the death knell of a VP6 Brent Cook
2002-04-10 15:23 ` Oleg Drokin
2002-04-10 16:43 ` Brent Cook
2002-04-10 16:49 ` William Park
2002-04-11 6:39 ` john slee
2002-04-10 20:55 ` Oleg Drokin
2002-04-10 17:16 ` John Adams
2002-04-10 17:52 ` Brent Cook
[not found] <Pine.LNX.4.33.0202081203020.29252-100000@coffee.psychology.mcmaster.ca>
2002-02-08 19:26 ` Fix for duplicate /proc entries Brent Cook
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=20020208174730.GA343@mis-mike-wstn \
--to=mfedyk@matchmail.com \
--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
all inboxes | Powered by JetHome®