From: Arnd Bergmann <arnd@arndb.de>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: linux-arch@vger.kernel.org
Subject: Re: [patch] sys_stime needs a compat function.
Date: Thu, 18 Nov 2004 19:06:47 +0100 [thread overview]
Message-ID: <200411181906.47591.arnd@arndb.de> (raw)
In-Reply-To: <20041118173416.GA8360@mschwid3.boeblingen.de.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
On Dunnersdag 18 November 2004 18:34, Martin Schwidefsky wrote:
> ia64 doesn't support sys_stime
I'd call that a bug, too.
> and ppc64 has its own sys_stime functions.
This one is identical to the generic sys_stime function (despite the
comment above it), so it should be merged as well.
> +
> +#ifdef __ARCH_WANT_SYS_TIME
> +
> +/*
> + * sys_stime() can be implemented in user-level using
> + * sys_settimeofday(). Is this for backwards compatibility? If so,
> + * why not move it into the appropriate arch directory (for those
> + * architectures that need it).
> + */
> +
> +asmlinkage long compat_sys_stime(compat_time_t __user *tptr)
I'd prefer having an extra __ARCH_WANT_COMPAT_SYS_TIME flag. Mips, x86_64,
ia64 and s390 only need compat_sys_stime, but not sys_stime for 64 bit
kernels.
Also, the comment you copied from sys_stime is apparently superceded by
introduction of __ARCH_WANT_XYZ.
Arnd <><
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-11-18 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 17:34 [patch] sys_stime needs a compat function Martin Schwidefsky
2004-11-18 18:06 ` Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-18 18:39 Luck, Tony
2004-11-24 15:40 Martin Schwidefsky
2004-11-24 15:43 ` Andi Kleen
2004-11-24 19:00 tony.luck
2004-11-25 12:13 ` Martin Schwidefsky
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=200411181906.47591.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=schwidefsky@de.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox