public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: dan@debian.org
Cc: torvalds@transmeta.com, levon@movementarian.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] /proc/sys/kernel/pointer_size
Date: Wed, 08 Jan 2003 20:31:34 -0800 (PST)	[thread overview]
Message-ID: <20030108.203134.64542534.davem@redhat.com> (raw)
In-Reply-To: <20030109040025.GA11596@nevyn.them.org>

   From: Daniel Jacobowitz <dan@debian.org>
   Date: Wed, 8 Jan 2003 23:00:25 -0500
   
   Just to clarify something that I saw getting lost in this discussion:
   Oprofile doesn't need to become built as a 64-bit binary, just
   configured to accept 64-bit kernels.  So this doesn't rule out using a
   32-bit oprofile (i.e. not needing a 64-bit libc) on a 64-bit kernel. 
   It just means that we need to specify it somehow.

That's right, indeed.  And furthermore, I'm willing to eat the 64-bit
overhead for all sparc builds. :)

  reply	other threads:[~2003-01-09  4:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 19:59 [PATCH] /proc/sys/kernel/pointer_size John Levon
2003-01-08 20:28 ` Linus Torvalds
2003-01-08 20:52   ` John Levon
2003-01-08 21:03     ` Linus Torvalds
2003-01-08 22:37       ` David S. Miller
2003-01-08 22:40       ` John Levon
2003-01-11  9:18       ` Kai Henningsen
2003-01-08 22:34   ` David S. Miller
2003-01-08 23:04     ` Linus Torvalds
2003-01-08 23:03       ` David S. Miller
2003-01-09  0:02         ` Linus Torvalds
2003-01-09  0:03           ` David S. Miller
2003-01-09  4:00             ` Daniel Jacobowitz
2003-01-09  4:31               ` David S. Miller [this message]
2003-01-09  5:23               ` William Lee Irwin III
2003-01-09 23:09       ` Bill Davidsen

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=20030108.203134.64542534.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=dan@debian.org \
    --cc=levon@movementarian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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