From: Ulrich Drepper <drepper@redhat.com>
To: Andreas Schwab <schwab@redhat.com>
Cc: libc-hacker@sourceware.org
Subject: Re: [PATCH] powerpc32: add fanotify_mark syscall
Date: Thu, 19 Aug 2010 14:54:00 -0000 [thread overview]
Message-ID: <4C6D4583.2000900@redhat.com> (raw)
In-Reply-To: <m339uaac8i.fsf@hase.home>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/19/2010 07:49 AM, Andreas Schwab wrote:
> Which is exactly what it does. Count the letters.
That's not what I meant. It's the order of the two halves. Works for
little endian If I got it right and big endian needs a wrapper.
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA â–
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
iEYEARECAAYFAkxtRYMACgkQ2ijCOnn/RHSXcQCgpbaOuhD5JxaWJfh6/cJrE6+b
huEAoKr5JcAGm5Bx3uLhh1kQkLoCdub/
=SHUy
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-08-19 14:54 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
2010-08-19 14:49 ` Andreas Schwab
2010-08-19 14:54 ` Ulrich Drepper [this message]
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=4C6D4583.2000900@redhat.com \
--to=drepper@redhat.com \
--cc=libc-hacker@sourceware.org \
--cc=schwab@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).