From: Russell King <rmk@arm.linux.org.uk>
To: John Levon <levon@movementarian.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linus Torvalds <torvalds@osdl.org>,
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:24:04 +0100 [thread overview]
Message-ID: <20030814182403.E332@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030814165512.GA36329@compsoc.man.ac.uk>; from levon@movementarian.org on Thu, Aug 14, 2003 at 05:55:12PM +0100
On Thu, Aug 14, 2003 at 05:55:12PM +0100, John Levon wrote:
> On Thu, Aug 14, 2003 at 05:47:03PM +0100, Alan Cox wrote:
>
> > I see no problem with it either going or becoming an arch specific
> > module someone can go write if they care about it and insmod if they
> > actually use.
>
> And then I'm stuck with no sensible way to figure out the kernel pointer
> size again... all user-space suggestions having the problems listed
> in this thread :
>
> http://marc.theaimsgroup.com/?t=104205635900001&r=1&w=2
You could say "oprofile requires /proc/kcore support".
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-08-14 17:24 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
2003-08-14 19:18 ` [PATCH] Export pointer size in oprofilefs John Levon
2003-08-14 17:24 ` Russell King [this message]
2003-08-14 20:12 ` [PATCH] Make modules work in Linus' tree on ARM Eli Carter
2003-08-14 20:42 ` Russell King
2003-08-18 19:27 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
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=20030814182403.E332@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.