All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andi Kleen <ak@suse.de>,
	blaisorblade@yahoo.it, torvalds@osdl.org, akpm@osdl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 2/3] x86_64: remove duplicated sys_time64
Date: Thu, 31 Mar 2005 13:36:21 +0200	[thread overview]
Message-ID: <20050331113621.GP1623@wotan.suse.de> (raw)
In-Reply-To: <20050331212516.64506156.sfr@canb.auug.org.au>

On Thu, Mar 31, 2005 at 09:25:16PM +1000, Stephen Rothwell wrote:
> On Thu, 31 Mar 2005 13:12:35 +0200 Andi Kleen <ak@suse.de> wrote:
> >
> > On Thu, Mar 31, 2005 at 09:10:59PM +1000, Stephen Rothwell wrote:
> > > On Thu, 31 Mar 2005 12:38:34 +0200 Andi Kleen <ak@suse.de> wrote:
> > > >
> > > > Nack. The generic sys_time still writes to int, not long.
> > > > That is why x86-64 has a private one. Please keep that.
> > > 
> > > It writes to a time_t which is a __kernel_time_t which is a long on
> > > x86-64, isn't it?
> > 
> > At least in 2.6.10 it writes to int.
> 
> I was looking at current bk where it looks like this:
> 
> asmlinkage long sys_time(time_t __user * tloc)

Ok with that change the patch is ok.
> {
>         time_t i;
>         struct timeval tv;
> 
>         do_gettimeofday(&tv);
>         i = tv.tv_sec;
> 
>         if (tloc) {
>                 if (put_user(i,tloc))
>                         i = -EFAULT;
>         }
>         return i;
> }
> 
> I have no idea when it changed.
I was looking at an older tree, sorry.
-Andi

      reply	other threads:[~2005-03-31 11:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30 17:32 [patch 2/3] x86_64: remove duplicated sys_time64 blaisorblade
2005-03-31 10:38 ` Andi Kleen
2005-03-31 11:10   ` Stephen Rothwell
2005-03-31 11:12     ` Andi Kleen
2005-03-31 11:25       ` Stephen Rothwell
2005-03-31 11:36         ` Andi Kleen [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=20050331113621.GP1623@wotan.suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=blaisorblade@yahoo.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@osdl.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.