From: Linus Torvalds <torvalds@osdl.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Make modules work in Linus' tree on ARM
Date: Thu, 14 Aug 2003 09:19:17 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0308140917350.8148-100000@home.osdl.org> (raw)
In-Reply-To: <20030814130810.A332@flint.arm.linux.org.uk>
On Thu, 14 Aug 2003, Russell King wrote:
>
> After reviewing the /proc/kcore and kclist issues, I've decided that I'm
> no longer prepared to even _think_ about supporting /proc/kcore on ARM -
I suspect we should just remove it altogether.
Does anybody actually _use_ /proc/kcore? It was one of those "cool
feature" things, but I certainly haven't ever used it myself except for
testing, and it's historically often been broken after various kernel
infrastructure updates, and people haven't complained..
Comments?
Linus
next prev parent reply other threads:[~2003-08-14 16:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 12:08 [PATCH] Make modules work in Linus' tree on ARM Russell King
2003-08-14 16:19 ` Linus Torvalds [this message]
2003-08-14 16:32 ` Russell King
2003-09-17 9:23 ` Russell King
2003-08-14 16:47 ` Alan Cox
2003-08-14 16:55 ` John Levon
2003-08-14 17:06 ` Alan Cox
2003-08-14 17:19 ` Linus Torvalds
2003-08-14 17:14 ` Linus Torvalds
2003-08-14 17:30 ` John Levon
2003-08-14 19:18 ` [PATCH] Export pointer size in oprofilefs John Levon
2003-08-14 17:24 ` [PATCH] Make modules work in Linus' tree on ARM Russell King
2003-08-14 20:12 ` Eli Carter
2003-08-14 20:42 ` Russell King
2003-08-18 19:27 ` Daniel Jacobowitz
2003-08-14 17:16 John Bradford
2003-08-14 17:42 Luck, Tony
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=Pine.LNX.4.44.0308140917350.8148-100000@home.osdl.org \
--to=torvalds@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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).