From: Roland Dreier <roland@topspin.com>
To: "David S. Miller" <davem@redhat.com>
Cc: ultralinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix sparc64 build with CONFIG_COMPAT=n
Date: Wed, 21 Jul 2004 20:43:53 +0000 [thread overview]
Message-ID: <52llhd2ira.fsf@topspin.com> (raw)
In-Reply-To: <20040720200352.5c17b3f7.davem@redhat.com> (David S. Miller's message of "Tue, 20 Jul 2004 20:03:52 -0700")
David> I like the big fix, and it allowed some cleanups too. I've
David> munged your patch a bit and this is what I'm currently
David> testing.
Cool, my allnoconfig compile tests thank you.
Just out of curiousity, is there any practical use for sparc64 without
CONFIG_COMPAT? My impression was that everyone used 32-bit userspace
(except for possibly a few executables).
- R.
WARNING: multiple messages have this Message-ID (diff)
From: Roland Dreier <roland@topspin.com>
To: "David S. Miller" <davem@redhat.com>
Cc: ultralinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix sparc64 build with CONFIG_COMPAT=n
Date: Wed, 21 Jul 2004 13:43:53 -0700 [thread overview]
Message-ID: <52llhd2ira.fsf@topspin.com> (raw)
In-Reply-To: <20040720200352.5c17b3f7.davem@redhat.com> (David S. Miller's message of "Tue, 20 Jul 2004 20:03:52 -0700")
David> I like the big fix, and it allowed some cleanups too. I've
David> munged your patch a bit and this is what I'm currently
David> testing.
Cool, my allnoconfig compile tests thank you.
Just out of curiousity, is there any practical use for sparc64 without
CONFIG_COMPAT? My impression was that everyone used 32-bit userspace
(except for possibly a few executables).
- R.
next prev parent reply other threads:[~2004-07-21 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-10 3:47 [PATCH] Fix sparc64 build with CONFIG_COMPAT=n Roland Dreier
2004-07-10 3:47 ` Roland Dreier
2004-07-21 3:03 ` David S. Miller
2004-07-21 3:03 ` David S. Miller
2004-07-21 20:43 ` Roland Dreier [this message]
2004-07-21 20:43 ` Roland Dreier
2004-07-21 21:47 ` David S. Miller
2004-07-21 21:47 ` David S. Miller
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=52llhd2ira.fsf@topspin.com \
--to=roland@topspin.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ultralinux@vger.kernel.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.