From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kdevt-diff
Date: 16 Apr 2003 09:43:04 -0700 [thread overview]
Message-ID: <b7k16o$6r2$1@cesium.transmeta.com> (raw)
In-Reply-To: Pine.LNX.4.44.0304141056450.19302-100000@home.transmeta.com
Followup to: <Pine.LNX.4.44.0304141056450.19302-100000@home.transmeta.com>
By author: Linus Torvalds <torvalds@transmeta.com>
In newsgroup: linux.dev.kernel
>
> (My prefernce for the 32-bit version would be 12+20 bits, but it's not a
> very strong one, and it doesn't really matter for the kernel proper, so I
> think Andries who has been tirelessly working on this for five years or
> more gets the final say on it).
>
I think 12+20 is a good choice for the 32-bit version (NFSv2 and those
guys.)
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-04-16 16:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-13 22:45 [PATCH] kdevt-diff Andries.Brouwer
2003-04-14 17:51 ` Joel Becker
2003-04-14 18:00 ` Linus Torvalds
2003-04-14 19:15 ` Joel Becker
2003-04-14 19:34 ` Roman Zippel
2003-04-16 16:43 ` H. Peter Anvin [this message]
2003-04-14 18:12 ` Roman Zippel
2003-04-14 18:18 ` Linus Torvalds
2003-04-14 18:31 ` Roman Zippel
2003-04-14 18:40 ` Linus Torvalds
2003-04-14 19:28 ` Roman Zippel
2003-04-14 19:51 ` Linus Torvalds
2003-04-14 20:02 ` Roman Zippel
2003-04-15 13:37 ` Roman Zippel
2003-04-23 15:19 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-04-14 22:01 Andries.Brouwer
2003-04-14 22:11 ` Joel Becker
2003-04-14 22:18 ` Valdis.Kletnieks
2003-04-14 22:28 ` Joel Becker
2003-04-16 16:48 ` H. Peter Anvin
2003-04-16 20:19 ` Andries Brouwer
2003-04-16 20:27 ` H. Peter Anvin
2003-04-15 14:04 Andries.Brouwer
2003-04-15 14:53 ` Roman Zippel
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='b7k16o$6r2$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@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.