From: Jes Sorensen <jes@linuxcare.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Linuxconf patch
Date: Sun, 15 Apr 2001 05:05:28 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005402@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005401@msgid-missing>
>>>>> "Gustavo" = Gustavo Niemeyer <niemeyer@conectiva.com> writes:
Gustavo> I'd also like to introduce myself, since I haven't had time
Gustavo> to do so before. I've been working in the last two weeks to
Gustavo> port Conectiva Linux to ia64. If you know about any way I can
Gustavo> help you, or just want to exchange ideas (well, maybe this
Gustavo> list is the best place to do this), please, let me know.
Very nice
However, I noticed the following:
diff -u -r linuxconf-1.25/fstab/quota.cc linuxconf-1.25.ia64/fstab/quota.cc
--- linuxconf-1.25/fstab/quota.cc Thu Nov 2 02:32:58 2000
+++ linuxconf-1.25.ia64/fstab/quota.cc Thu Apr 12 12:03:21 2001
@@ -366,6 +366,18 @@
{
return syscall(__NR_quotactl, cmd, special, id, addr);
}
+#elif defined(__ia64__)
+ #include <asm/unistd.h>
+ int quotactl(int cmd, const char * special, int id, caddr_t addr)
+ {
+ register long r8 asm ("r8");
+ asm volatile ("mov r15=%1\n\t"
+ "break %2"
+ : "=r"(r8)
+ : "g"(__NR_quotactl), "g"(__BREAK_SYSCALL),
+ "r"(cmd), "r"(special), "r"(id), "r"(addr));
+ return r8;
+ }
Please don't inline the syscall like that. We do support syscall() in
glibc and it would be nicer (and future compatible) if you use that
instead.
Cheers
Jes
next prev parent reply other threads:[~2001-04-15 5:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-15 3:47 [Linux-ia64] Linuxconf patch Gustavo Niemeyer
2001-04-15 5:05 ` Jes Sorensen [this message]
2001-04-15 16:46 ` Gustavo Niemeyer
2001-04-15 20:37 ` David Mosberger
2001-04-17 4:02 ` Jacques Gelinas
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=marc-linux-ia64-105590693005402@msgid-missing \
--to=jes@linuxcare.com \
--cc=linux-ia64@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