From: Ulrich Drepper <drepper@redhat.com>
To: 7eggert@gmx.de
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, torvalds@osdl.org
Subject: Re: [PATCH 3/3] updated *at function patch
Date: Fri, 06 Jan 2006 13:49:44 -0800 [thread overview]
Message-ID: <43BEE5F8.5040109@redhat.com> (raw)
In-Reply-To: <E1EuzOT-0000jw-1g@be1.lrz>
[-- Attachment #1: Type: text/plain, Size: 364 bytes --]
Bodo Eggert wrote:
>> +#define __NR_fchownat 259
>> +__SYSCALL(__NR_fchownat, sys_fchownat)
>
> s/fchown/chown/ ?
No, fchownat is the name commonly used. I don't like it much either but
it's the name commonly used (i.e., what is used in Solaris).
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next prev parent reply other threads:[~2006-01-06 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5s5sB-p4-181@gated-at.bofh.it>
2006-01-06 21:45 ` [PATCH 3/3] updated *at function patch Bodo Eggert
2006-01-06 21:49 ` Ulrich Drepper [this message]
2006-01-06 19:04 Ulrich Drepper
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=43BEE5F8.5040109@redhat.com \
--to=drepper@redhat.com \
--cc=7eggert@gmx.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox