From: "H. Peter Anvin" <hpa@zytor.com>
To: Helge Deller <deller@gmx.de>, Ley Foon Tan <lftan@altera.com>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: lftan.linux@gmail.com, cltang@codesourcery.com,
"James E.J. Bottomley" <jejb@parisc-linux.org>,
linux-parisc@vger.kernel.org
Subject: Re: [PATCH 17/25] parisc: Add 32 bit time_t and clock_t
Date: Wed, 14 May 2014 17:34:56 -0700 [thread overview]
Message-ID: <53740BB0.1050708@zytor.com> (raw)
In-Reply-To: <53727DE8.7000105@gmx.de>
On 05/13/2014 01:17 PM, Helge Deller wrote:
>
> We can't use CONFIG_64BIT for a userspace header file. Please use
> #if !defined(__LP64__)
> instead.
> But even then I'm not sure if it's all correct...
>
__u64 (or __s64) works fine in that case.
-hpa
prev parent reply other threads:[~2014-05-15 0:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1399971456-3941-1-git-send-email-lftan@altera.com>
2014-05-13 9:06 ` [PATCH 17/25] parisc: Add 32 bit time_t and clock_t Ley Foon Tan
2014-05-13 20:17 ` Helge Deller
2014-05-14 1:57 ` Ley Foon Tan
2014-05-15 0:34 ` H. Peter Anvin [this message]
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=53740BB0.1050708@zytor.com \
--to=hpa@zytor.com \
--cc=cltang@codesourcery.com \
--cc=deller@gmx.de \
--cc=jejb@parisc-linux.org \
--cc=lftan.linux@gmail.com \
--cc=lftan@altera.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@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