From: Ralf Baechle <ralf@uni-koblenz.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Terje Eggestad <terje.eggestad@scali.com>,
Amber Palekar <amber_palekar@yahoo.com>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Again:syscall from modules
Date: Fri, 28 Dec 2001 14:26:14 -0200 [thread overview]
Message-ID: <20011228142614.A1915@dea.linux-mips.net> (raw)
In-Reply-To: <20011225131441.60811.qmail@web20306.mail.yahoo.com> <1009468465.15846.0.camel@eggis1> <15403.28458.153083.961800@charged.uio.no> <20011228134106.B1323@dea.linux-mips.net> <15404.37994.476173.804713@charged.uio.no>
In-Reply-To: <15404.37994.476173.804713@charged.uio.no>; from trond.myklebust@fys.uio.no on Fri, Dec 28, 2001 at 04:48:58PM +0100
On Fri, Dec 28, 2001 at 04:48:58PM +0100, Trond Myklebust wrote:
> > Many sys_*() functions may be in the generic code but that
> > still doesn't mean the ports are actually using it or that no
> > special calling sequence which normally would be done in libc
> > is required. Only people doing syscalls themselfes and not
> > through libc wrappers is worse ...
>
> Please read the beginning of the thread. The question was about
> calling from within kernel space. No libc is or can be involved...
I was just comparing ...
Ralf
prev parent reply other threads:[~2001-12-28 19:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-25 11:31 syscall from modules Amber Palekar
2001-12-25 13:09 ` Trond Myklebust
2001-12-25 13:14 ` Again:syscall " Amber Palekar
2001-12-25 18:37 ` Trond Myklebust
2001-12-27 15:54 ` Terje Eggestad
2001-12-27 16:04 ` Terje Eggestad
2001-12-27 18:57 ` Trond Myklebust
2001-12-28 15:41 ` Ralf Baechle
2001-12-28 15:48 ` Trond Myklebust
2001-12-28 16:26 ` Ralf Baechle [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=20011228142614.A1915@dea.linux-mips.net \
--to=ralf@uni-koblenz.de \
--cc=amber_palekar@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=terje.eggestad@scali.com \
--cc=trond.myklebust@fys.uio.no \
/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