From: Jan Glauber <glauber@gmx.de>
To: linux-s390@vger.kernel.org
Subject: Re: __kernel_ino_t == 32bit
Date: Tue, 12 Aug 2008 11:33:09 +0000 [thread overview]
Message-ID: <1218540789.8269.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20080809141428.GA7813@wavehammer.waldi.eu.org>
Hi Bastian,
On Sat, 2008-08-09 at 16:14 +0200, Bastian Blank wrote:
> Hi folks
>
> Is there a reason why both 32 and 64Bit kernel have __kernel_ino_t 32bit
> wide? Any other arches have it matching the word size.
I don't think there is a reason and my machine does not complain if I
change it the 64Bit __kernel_ino_t to "unsigned long". But what about
the comment in the header file that the types are used by userspace?
Can we easily change that without breaking things?
Jan
> Bastian
>
parent reply other threads:[~2008-08-12 11:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20080809141428.GA7813@wavehammer.waldi.eu.org>]
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=1218540789.8269.3.camel@localhost.localdomain \
--to=glauber@gmx.de \
--cc=linux-s390@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox