From: Ulrich Drepper <drepper@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] libc umount and umount2 can't both be right
Date: Thu, 15 May 2003 00:26:45 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705813@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705762@msgid-missing>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andreas Schwab wrote:
> [ SYS_umount is actually umount2 on ia64 ]
Indeed. This is the right patch, I've applied it. Thanks,
- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+wt7F2ijCOnn/RHQRAk3CAKCtCGqcjD3nhWuJenbeKKfWRWnHFACfdT/D
XdI87pwOvJw8IdGtnhQ0mhY=M4/U
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2003-05-15 0:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 20:06 [Linux-ia64] libc umount and umount2 can't both be right MONTGOMERY,BOB (HP-FtCollins,ex1)
2003-05-13 23:24 ` Ian Wienand
2003-05-14 8:31 ` Andreas Schwab
2003-05-14 11:37 ` Ian Wienand
2003-05-14 14:43 ` Andreas Schwab
2003-05-14 15:47 ` MONTGOMERY,BOB (HP-FtCollins,ex1)
2003-05-15 0:26 ` Ulrich Drepper [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=marc-linux-ia64-105590723705813@msgid-missing \
--to=drepper@redhat.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