From: "H. Peter Anvin" <hpa@transmeta.com>
To: ultralinux@vger.kernel.org
Subject: Re: 2.1.126 still no sparc64 autofsu
Date: Mon, 16 Nov 1998 08:37:08 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-91122943501911@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-91107863319189@msgid-missing>
> >
> > I looked at this patch, and it occurs to me, why to make it an
> > unsigned long ever? For one thing this wait_queue_token seems to be
> > set by an int counter (autofs_next_wait_queue).
>
> I guess probably just for alpha compatibility. So the best would be to use a
> u32 everywhere and have a special case for alpha - u64 - to keep it binary
> compatible.
>
> Cheers,
> Jakub
Actually, there is a simpler answer (I guess): Linus changed this one
while I was on vacation; it used to be u32. :(
-hpa
next prev parent reply other threads:[~1998-11-16 8:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-14 8:17 2.1.126 still no sparc64 autofsu H. Peter Anvin
1998-11-14 15:45 ` Rich Sahlender
1998-11-14 19:53 ` Jakub Jelinek
1998-11-15 0:52 ` David S. Miller
1998-11-15 23:49 ` H. Peter Anvin
1998-11-15 23:54 ` David S. Miller
1998-11-16 6:47 ` H. Peter Anvin
1998-11-16 6:48 ` Jakub Jelinek
1998-11-16 7:57 ` Jakub Jelinek
1998-11-16 8:37 ` H. Peter Anvin [this message]
1998-11-16 20:33 ` Rich Sahlender
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=marc-linux-ultrasparc-91122943501911@msgid-missing \
--to=hpa@transmeta.com \
--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.