All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: torvalds@osdl.org, akpm@osdl.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH] Revert [i386/x86_64]: Remove __KERNEL__ ifdef around _syscall*()
Date: Mon, 4 Sep 2006 22:30:13 +0200	[thread overview]
Message-ID: <200609042230.13455.ak@suse.de> (raw)
In-Reply-To: <1157398050.2473.137.camel@shinybook.infradead.org>


> 1. C libraries have their own syscall(); there's no _need_ for these
>    macros to be exported by the kernel.

I like having them there. I find it it useful for my test programs.
It's also useful for numactl for once.

> 3. We should be consistent about what we provide in kernel headers.
>    Since we don't provide these macros on other architectures, we should
>    not do so on i386 and x86_64 -- especially as the reason for doing so
>    seems to be just that the arch maintainer doesn't want to use the
>    proper glibc function in his test hacks.

We've always provided them and continuing to do so is consistent.

-Andi

  parent reply	other threads:[~2006-09-04 20:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200608302359.k7UNxIZW027536@hera.kernel.org>
2006-09-04 19:27 ` [PATCH] Revert [i386/x86_64]: Remove __KERNEL__ ifdef around _syscall*() David Woodhouse
2006-09-04 19:38   ` Andrew Morton
2006-09-04 19:56     ` Arnd Bergmann
2006-09-04 20:50       ` David Woodhouse
2006-09-04 19:56     ` David Woodhouse
2006-09-10  9:48     ` David Woodhouse
2006-09-10  8:33       ` Andi Kleen
2006-09-10 10:30         ` David Woodhouse
2006-09-04 20:07   ` Arnd Bergmann
2006-09-04 20:30   ` Andi Kleen [this message]
2006-09-04 21:16     ` David Woodhouse

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=200609042230.13455.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-arch@vger.kernel.org \
    --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.