From: Kyle Moffett <mrmacman_g4@mac.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Sparc Linux Mailing List <sparclinux@vger.kernel.org>,
William Lee Irwin <wli@holomorphy.com>
Subject: [BUG?] Signedness of __kernel_nlink_t on Sparc?
Date: Mon, 14 Mar 2005 00:21:09 +0000 [thread overview]
Message-ID: <bbcd3873d9324ce185dc9eaf146ef741@mac.com> (raw)
In include/asm-sparc/types.h, __kernel_nlink_t is signed, whereas on
all the
other architectures it is unsigned. Is this intentional, or a bug?
Cheers,
Kyle Moffett
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a18 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$
L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r
!y?(-)
------END GEEK CODE BLOCK------
WARNING: multiple messages have this Message-ID (diff)
From: Kyle Moffett <mrmacman_g4@mac.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Sparc Linux Mailing List <sparclinux@vger.kernel.org>,
William Lee Irwin <wli@holomorphy.com>
Subject: [BUG?] Signedness of __kernel_nlink_t on Sparc?
Date: Sun, 13 Mar 2005 19:21:09 -0500 [thread overview]
Message-ID: <bbcd3873d9324ce185dc9eaf146ef741@mac.com> (raw)
In include/asm-sparc/types.h, __kernel_nlink_t is signed, whereas on
all the
other architectures it is unsigned. Is this intentional, or a bug?
Cheers,
Kyle Moffett
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a18 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$
L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r
!y?(-)
------END GEEK CODE BLOCK------
next reply other threads:[~2005-03-14 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 0:21 Kyle Moffett [this message]
2005-03-14 0:21 ` [BUG?] Signedness of __kernel_nlink_t on Sparc? Kyle Moffett
2005-03-14 1:56 ` David S. Miller
2005-03-14 1:56 ` David S. Miller
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=bbcd3873d9324ce185dc9eaf146ef741@mac.com \
--to=mrmacman_g4@mac.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=wli@holomorphy.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.