From: John Levon <levon@movementarian.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Russell King <rmk@arm.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Make modules work in Linus' tree on ARM
Date: Thu, 14 Aug 2003 18:30:24 +0100 [thread overview]
Message-ID: <20030814173024.GA42066@compsoc.man.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0308141011030.8148-100000@home.osdl.org>
On Thu, Aug 14, 2003 at 10:14:37AM -0700, Linus Torvalds wrote:
> Why not just fix the oprofile interfaces to contain that information? You
> already have to export CPU type, buffer size etc..
I'll quite happily do that. I'd assumed it was also rejected for bloat
reasons based on your previous objections that it was/should be entirely
a userspace issue.
If you'll take /dev/oprofile/pointer_size now, then I'm more than happy
to drop the kcore sniffing (and I don't have the a.out problem any more)
regards
john
--
Khendon's Law:
If the same point is made twice by the same person, the thread is over.
next prev parent reply other threads:[~2003-08-14 17:31 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
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 [this message]
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=20030814173024.GA42066@compsoc.man.ac.uk \
--to=levon@movementarian.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=torvalds@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).