From: Randolph Chung <randolph@tausq.org>
To: Joel Soete <joel.soete@freebel.net>
Cc: jsoe0708@tiscali.be, Stefan Pfetzing <dreamind@dreamind.de>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: mkfs.xfs (xfsprogs-2.3.5) failled
Date: Sat, 26 Oct 2002 14:18:22 -0700 [thread overview]
Message-ID: <20021026211822.GJ22052@tausq.org> (raw)
In-Reply-To: <3DBAD364.9060301@freebel.net>
In reference to a message from Joel Soete, dated Oct 26:
> i386 declare: "extern void __get_user_bad(void);"
> ...
> but not define elsewhere? (is it there so that the build of the kernel
> failed if that case was requested to run properly?)
yes.
> PS: afaik on i386 only put_user_u64 is define why not pending get_user?
on first glance i haven't found any code that uses get_user with 64-bit
quantities. if you have a specific need for this, please let me know.
in the mean time, i've checked in support for put_user with 64-bit
values. This is in 2.4.19-pa24
Let me know if this works for you. i've tested it only lightly.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2002-10-26 21:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 7:30 [parisc-linux] mkfs.xfs (xfsprogs-2.3.5) failled jsoe0708
2002-10-24 17:58 ` [parisc-linux] " Stefan Pfetzing
2002-10-24 18:15 ` Randolph Chung
2002-10-24 18:17 ` Stefan Pfetzing
2002-10-24 19:00 ` Randolph Chung
2002-10-24 23:08 ` Stefan Pfetzing
2002-10-25 6:04 ` jsoe0708
2002-10-25 12:58 ` jsoe0708
2002-10-25 15:09 ` jsoe0708
2002-10-26 17:39 ` Joel Soete
2002-10-26 21:18 ` Randolph Chung [this message]
[not found] ` <3DBB30C0.6060000@freebel.net>
2002-10-27 0:32 ` Joel Soete
2002-10-26 23:40 ` Joel Soete
2002-10-25 15:26 ` Randolph Chung
2002-10-25 5:57 ` jsoe0708
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=20021026211822.GJ22052@tausq.org \
--to=randolph@tausq.org \
--cc=dreamind@dreamind.de \
--cc=joel.soete@freebel.net \
--cc=jsoe0708@tiscali.be \
--cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.