From: Ulrich Drepper <drepper@redhat.com>
To: libc-hacker@sourceware.org
Subject: Re: [PATCH] powerpc32: add fanotify_mark syscall
Date: Thu, 19 Aug 2010 14:45:00 -0000 [thread overview]
Message-ID: <4C6D4363.7070407@redhat.com> (raw)
In-Reply-To: <m3bp8yaee7.fsf@hase.home>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/19/2010 07:03 AM, Andreas Schwab wrote:
> +fanotify_mark EXTRA fanotify_mark i:iiiiis fanotify_mark
Are you sure? I didn't add anything like this because the kernel entry
for 32-bit expects the mask in two halves. These are passed correctly
for x86 but I don't think it works without a wrapper on big endian.
- --
⧠Ulrich Drepper ⧠Red Hat, Inc. ⧠444 Castro St ⧠Mountain View, CA â
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
iEYEARECAAYFAkxtQ2MACgkQ2ijCOnn/RHS5sQCfRfH/xRQHzFRIarU9XfKA1aXz
09kAn1gIfELhYWKn7HMHGahSUHOChVAa
=/uWN
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-08-19 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 14:03 Andreas Schwab
2010-08-19 14:45 ` Ulrich Drepper [this message]
2010-08-19 14:49 ` Andreas Schwab
2010-08-19 14:54 ` Ulrich Drepper
2010-08-19 14:58 ` Andreas Schwab
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=4C6D4363.7070407@redhat.com \
--to=drepper@redhat.com \
--cc=libc-hacker@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).