From: Arnd Bergmann <arnd@arndb.de>
To: Ulrich Drepper <drepper@redhat.com>
Cc: John Williams <john.williams@petalogix.com>,
monstr@seznam.cz, Matthew Wilcox <matthew@wil.cx>,
Will Newton <will.newton@gmail.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-arch@vger.kernel.org, git@xilinx.com,
Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>,
John Linn <John.Linn@xilinx.com>
Subject: Re: microblaze syscall list
Date: Sat, 3 May 2008 23:14:23 +0200 [thread overview]
Message-ID: <200805032314.24669.arnd@arndb.de> (raw)
In-Reply-To: <481C8B48.5020306@redhat.com>
On Saturday 03 May 2008, Ulrich Drepper wrote:
> Yes, this is how it should be. It's not done because no architecture
> glibc officially supports arrived after these and similar syscalls
> arrived. There is no need to implement the not-*at interface, no need
> to implement the creat syscall, etc etc.
Ah, good! So where should the glibc implementation for these calls go?
In the microblaze (and any future architecture) specific source directories,
to be consolidated when you get more of them, or in the common places like
sysdeps/unix/sysv/linux/*.c, with the appropriate #ifndef?
Arnd <><
next prev parent reply other threads:[~2008-05-03 21:15 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 12:13 [RFC] Introduce __ARCH_WANT_SYS_SYSFS Will Newton
2008-04-22 13:15 ` Arnd Bergmann
2008-04-23 21:16 ` Michal Simek
2008-04-23 21:38 ` Mike Frysinger
2008-04-24 11:11 ` microblaze syscall list Arnd Bergmann
2008-04-24 18:42 ` Michal Simek
2008-04-24 21:21 ` Arnd Bergmann
2008-04-25 9:36 ` [microblaze-uclinux] " John Williams
2008-04-25 10:06 ` Matthew Wilcox
2008-04-25 11:32 ` Geert Uytterhoeven
2008-04-27 2:04 ` John Williams
2008-04-27 15:52 ` Michal Simek
2008-04-27 16:50 ` Alan Cox
2008-04-27 20:15 ` Arnd Bergmann
2008-04-28 0:15 ` John Williams
2008-04-28 12:31 ` Arnd Bergmann
2008-05-01 19:17 ` Arnd Bergmann
2008-05-02 5:38 ` John Williams
2008-05-02 8:18 ` Michal Simek
2008-05-03 3:49 ` John Williams
2008-05-03 9:16 ` Arnd Bergmann
2008-05-03 15:56 ` Ulrich Drepper
2008-05-03 21:14 ` Arnd Bergmann [this message]
2008-05-05 1:09 ` John Williams
2008-05-05 14:08 ` Arnd Bergmann
2008-05-03 21:57 ` Arnd Bergmann
2008-05-04 9:12 ` Michal Simek
2008-05-04 19:37 ` Arnd Bergmann
2008-05-05 6:18 ` Michal Simek
2008-05-04 22:09 ` H. Peter Anvin
2008-05-04 22:54 ` Arnd Bergmann
2008-05-04 22:53 ` H. Peter Anvin
2008-05-06 8:33 ` Michal Simek
2008-04-24 20:51 ` Michal Simek
2008-04-24 21:37 ` Arnd Bergmann
2008-04-22 15:12 ` [RFC] Introduce __ARCH_WANT_SYS_SYSFS Randy Dunlap
2008-04-22 15:16 ` Will Newton
2008-04-22 15:24 ` Kyle McMartin
2008-04-22 15:34 ` Will Newton
2008-04-22 15:38 ` Kyle McMartin
2008-04-23 14:36 ` Will Newton
2008-04-23 14:59 ` Arnd Bergmann
2008-04-23 15:40 ` Kyle McMartin
2008-04-23 15:50 ` Will Newton
2008-04-23 16:05 ` Mike Frysinger
2008-04-23 17:59 ` Mike Frysinger
2008-04-24 9:18 ` Will Newton
2008-04-23 18:44 ` Sam Ravnborg
2008-04-24 14:51 ` Adrian Bunk
2008-04-22 15:21 ` Kyle McMartin
2008-04-22 15:38 ` Arnd Bergmann
2008-04-22 15:42 ` Kyle McMartin
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=200805032314.24669.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=John.Linn@xilinx.com \
--cc=drepper@redhat.com \
--cc=git@xilinx.com \
--cc=john.williams@petalogix.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=monstr@seznam.cz \
--cc=stephen.neuendorffer@xilinx.com \
--cc=will.newton@gmail.com \
/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