From: Edgar Toernig <froese@gmx.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] syscalls-by-name (aka dynamic syscalls / vsyscalls)
Date: Fri, 18 Jan 2002 01:10:19 +0100 [thread overview]
Message-ID: <3C4767EB.D1911582@gmx.de> (raw)
In-Reply-To: <20020117171930.G18086@redhat.com>
Benjamin LaHaise wrote:
>
> The attached patch implements syscalls-by-name [...]
>
> If anyone has any comments [...]
Don't miss the wood for the trees.
Ciao, ET.
next prev parent reply other threads:[~2002-01-18 0:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 22:19 [RFC] syscalls-by-name (aka dynamic syscalls / vsyscalls) Benjamin LaHaise
2002-01-18 0:10 ` Edgar Toernig [this message]
2002-01-18 11:04 ` ertzog
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=3C4767EB.D1911582@gmx.de \
--to=froese@gmx.de \
--cc=linux-kernel@vger.kernel.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