From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: libc-hacker@sources.redhat.com
Subject: Re: [PATCH] POSIX_FADV_{DONTNEED,NOREUSE} defines on s390-64.
Date: Thu, 14 Jul 2005 09:02:00 -0000 [thread overview]
Message-ID: <OF6DC515B8.D5B15D44-ON4225703E.00314B44-4225703E.0031A769@de.ibm.com> (raw)
In-Reply-To: <42D2A3A0.6030300@redhat.com>
> Changing glibc might be the simpler solution but it the least friendly
> to users. Can you reconsider it?
The patch to fix this problem in the kernel has hit the git repository.
The solution in the kernel doesn't comply with my sense of nice, good
looking code but I must admit it is the better solution for the customer.
blue skies,
Martin
Martin Schwidefsky
Linux for zSeries Development & Services
IBM Deutschland Entwicklung GmbH
next prev parent reply other threads:[~2005-07-14 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 11:13 Martin Schwidefsky
2005-07-11 16:55 ` Ulrich Drepper
2005-07-12 7:47 ` Martin Schwidefsky
2005-07-14 9:02 ` Martin Schwidefsky [this message]
2005-07-14 15:00 ` Ulrich Drepper
2005-07-12 11:49 Martin Schwidefsky
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=OF6DC515B8.D5B15D44-ON4225703E.00314B44-4225703E.0031A769@de.ibm.com \
--to=schwidefsky@de.ibm.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.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).