From: Pavel Machek <pavel@ucw.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus <torvalds@transmeta.com>,
LKML <linux-kernel@vger.kernel.org>,
anton@samba.org, "David S. Miller" <davem@redhat.com>,
ak@muc.de
Subject: Re: [PATCH] Beginnings of conpat 32 code cleanups
Date: Tue, 26 Nov 2002 14:53:01 +0100 [thread overview]
Message-ID: <20021126135301.GB1268@zaurus> (raw)
In-Reply-To: <20021122162312.32ff4bd3.sfr@canb.auug.org.au>
Hi!
> There is a lot of duplicated code among the 32 compatibility layers in our
> 64 bit architectures. I am proposing to considate this as much as
> possible. To that end, I first need to tidy up the relevant header files
> and make them as common as possible. Discussions with Dave Miller, Andi
> Kleen, and Anton Blanchard has led to the creation of compat32.h to
> contain all the 32 compatibility data types.
>
> This patch merely adds include/asm-generic/compat32.h which is the header
> information that is common to all the 32 bit compatibility code across all
> the architectures (except parisc as I don't pretend to understand that
> :-)).
>
> I will follow this up with patches for each architecture that I can. I
I'll be happy to test anything you have on
x86-64...
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
prev parent reply other threads:[~2002-11-26 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 5:23 [PATCH] Beginnings of conpat 32 code cleanups Stephen Rothwell
2002-11-22 19:47 ` Linus Torvalds
2002-11-22 19:54 ` Larry McVoy
2002-11-22 20:13 ` Cort Dougan
2002-11-22 20:38 ` H. Peter Anvin
2002-11-23 0:28 ` Stephen Rothwell
2002-11-25 19:48 ` Linus Torvalds
2002-11-23 5:16 ` Anton Blanchard
2002-11-25 20:00 ` Linus Torvalds
2002-11-26 13:53 ` Pavel Machek [this message]
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=20021126135301.GB1268@zaurus \
--to=pavel@ucw.cz \
--cc=ak@muc.de \
--cc=anton@samba.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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 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.