From: Jaswinder Singh <jaswinder@infradead.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
kernelnewbies <kernelnewbies@nl.linux.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] x86: Introducing asm-x86/syscalls.h
Date: Tue, 15 Jul 2008 21:29:38 +0530 [thread overview]
Message-ID: <1216137578.2747.16.camel@jaswinder.satnam> (raw)
In-Reply-To: <1216133883.27455.252.camel@shinybook.infradead.org>
Hello David,
On Tue, 2008-07-15 at 07:58 -0700, David Woodhouse wrote:
> I don't like this bit though:
>
> > --- a/include/linux/syscalls.h
> > +++ b/include/linux/syscalls.h
> > @@ -65,6 +65,10 @@ struct getcpu_cache;
> > #include <linux/quota.h>
> > #include <linux/key.h>
> >
> > +#ifdef CONFIG_X86
> > +#include <asm/syscalls.h>
> > +#endif
> > +
> > asmlinkage long sys_time(time_t __user *tloc);
> > asmlinkage long sys_stime(time_t __user *tptr);
> > asmlinkage long sys_gettimeofday(struct timeval __user *tv,
>
> We're going to want to do this for all architectures, aren't we? Perhaps
> it's better to provide <asm/syscalls.h> for all architectures from the
> beginning, and not bother with the ifdef? Or if you must have an ifdef,
> perhaps make it on something like ARCH_HAS_ASM_SYSCALLS_H rather than
> having to change it every time an architecture adds its own
> <asm/syscalls.h> file?
>
OK, I will also create asm/syscalls.h for all the architectures.
Thank you,
Jaswinder Singh.
prev parent reply other threads:[~2008-07-15 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 9:27 Jaswinder Singh
2008-07-15 13:06 ` Jaswinder Singh
2008-07-15 14:58 ` David Woodhouse
2008-07-15 15:59 ` Jaswinder Singh [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=1216137578.2747.16.camel@jaswinder.satnam \
--to=jaswinder@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®