LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Dong Feng" <middle.fengdong@gmail.com>
To: "Davide Libenzi" <davidel@xmailserver.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Why __syscallN macros are removed?
Date: Fri, 23 Feb 2007 11:10:33 +0800	[thread overview]
Message-ID: <a2ebde260702221910q1da29a21r947bf7999f51d6c6@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702221903490.1356@alien.or.mcafeemobile.com>

Thank you very much.


2007/2/23, Davide Libenzi <davidel@xmailserver.org>:
> On Fri, 23 Feb 2007, Dong Feng wrote:
>
> > The __syscallN series macros have disappeared in
> > include/asm-i386/unistd.h. Why? I occasionally what to add and use
> > some new system calls, mainly for debug use. Now I can not access the
> > system call I added from user space.
>
> You can use glibc's syscall(2) instead of macros.
>
>
>
> - Davide
>
>
>

      reply	other threads:[~2007-02-23  3:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23  2:47 Dong Feng
2007-02-23  3:04 ` Davide Libenzi
2007-02-23  3:10   ` Dong Feng [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=a2ebde260702221910q1da29a21r947bf7999f51d6c6@mail.gmail.com \
    --to=middle.fengdong@gmail.com \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Why __syscallN macros are removed?' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).