From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Jamie Lokier <jamie@shareable.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] use simple_strtoul for unsigned kernel parameters
Date: 18 Aug 2003 17:43:24 +0100 [thread overview]
Message-ID: <1061225003.25041.34.camel@dhcp23.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0308180817360.1672-100000@home.osdl.org>
On Llu, 2003-08-18 at 16:20, Linus Torvalds wrote:
> Well, in theory short/int/long can all be the same size and thus a
> "unsigned short" may not actually fit in a "long". I think that was the
> case on the old 64-bit cray machines, for example ("char" was a very slow
> 8-bit thing, everything else was purely 64-bit).
>
> Not likely something we want to port Linux to, admittedly.
Bear in mind we have the compiler source 8). If someone desperately
wants to run Linux (probably ucLinux) on their cray they can fix the
types too.
Things like the DEC10 (9,18,36 bit) and HLH Orion (word addressed) would
be a lot more fun but thankfully are extinct
next prev parent reply other threads:[~2003-08-18 16:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 0:46 [PATCH] use simple_strtoul for unsigned kernel parameters Jamie Lokier
2003-08-18 10:13 ` Rusty Russell
2003-08-18 12:09 ` Jamie Lokier
2003-08-18 15:32 ` Rusty Russell
2003-08-18 15:20 ` Linus Torvalds
2003-08-18 15:31 ` Jamie Lokier
2003-08-18 16:43 ` Alan Cox [this message]
2003-08-18 17:18 John Bradford
2003-08-18 17:15 ` Larry McVoy
2003-08-18 19:17 ` Alan Cox
2003-08-18 17:40 John Bradford
2003-08-18 17:39 ` Larry McVoy
2003-08-18 17:59 John Bradford
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=1061225003.25041.34.camel@dhcp23.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).