From: "David S. Miller" <davem@redhat.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: patches for PROC_FS=n (2.6.0-test7)
Date: Sat, 11 Oct 2003 12:08:52 -0700 [thread overview]
Message-ID: <20031011120852.13fa8ec4.davem@redhat.com> (raw)
In-Reply-To: <20031010141646.779f10bb.rddunlap@osdl.org>
On Fri, 10 Oct 2003 14:16:46 -0700
"Randy.Dunlap" <rddunlap@osdl.org> wrote:
> http://developer.osdl.org/rddunlap/patches/atmprocfs_260t7.patch
How can this be needed? When procfs is disabled then
remove_proc_entry() is defined as "do { } while (0)", ie. a nop.
next prev parent reply other threads:[~2003-10-11 19:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 21:16 patches for PROC_FS=n (2.6.0-test7) Randy.Dunlap
2003-10-11 19:08 ` David S. Miller [this message]
2003-10-11 19:40 ` Sam Ravnborg
2003-10-11 19:40 ` David S. Miller
2003-10-12 3:24 ` Randy.Dunlap
[not found] <Pine.GSO.4.58.0310101519330.9806@inky>
2003-10-13 2:17 ` Randy.Dunlap
2003-10-14 5:17 ` Noah J. Misch
2003-10-13 3:13 ` Randy.Dunlap
2003-10-13 11:31 ` Elmer
2003-10-13 14:49 ` Randy.Dunlap
2003-10-14 5:52 ` Noah J. Misch
2003-10-14 6:12 ` Randy.Dunlap
2003-10-14 8:39 ` Elmer
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=20031011120852.13fa8ec4.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=rddunlap@osdl.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;
as well as URLs for NNTP newsgroup(s).