All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jamie Lokier <jamie@shareable.org>, linux-kernel@vger.kernel.org
Subject: Re: Minor header bug? MIPS (32-bit) nlink_t sign
Date: Tue, 21 Jan 2003 10:00:20 +0100	[thread overview]
Message-ID: <20030121100020.A15008@linux-mips.org> (raw)
In-Reply-To: <20030121160959.6e392885.sfr@canb.auug.org.au>; from sfr@canb.auug.org.au on Tue, Jan 21, 2003 at 04:09:59PM +1100

On Tue, Jan 21, 2003 at 04:09:59PM +1100, Stephen Rothwell wrote:

> > Stephen, I guess you have already figured this out with your recent
> > 32-bit compatibility cleanup?
> 
> I mainly did direct substitutions, but will have a look shortly and see
> what I think.
> 
> I assume we are being compatable with Irix? Ralf?

Dunno where the signed int for nlink_t did come from.  The original idea
was to avoid pointless creativity and choose data types to match IRIX
rsp. the MIPS psABI.  As using a signed type didn't create any visible
problems so far this never got noticed until Jamie Lokier mailed me last
week.  I now changed the definition to unsigned long for the 32-bit
kernel and unsigned int for the 64-bit kernel.

  Ralf

  parent reply	other threads:[~2003-01-21  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-18  3:34 Minor header bug? MIPS (32-bit) nlink_t sign Jamie Lokier
2003-01-21  5:09 ` Stephen Rothwell
2003-01-21  6:18   ` David S. Miller
2003-01-21  9:00   ` Ralf Baechle [this message]
2003-01-21 11:53     ` Jamie Lokier

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=20030121100020.A15008@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.