From: Ulrich Drepper <drepper@redhat.com>
To: Steven Munroe <munroesj@us.ibm.com>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>,
Jakub Jelinek <jakub@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH] PPC fenv fixes 4th update
Date: Wed, 02 May 2007 08:22:00 -0000 [thread overview]
Message-ID: <46384A0D.4070405@redhat.com> (raw)
In-Reply-To: <4637BE8E.9020107@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 478 bytes --]
Steven Munroe wrote:
> +/* This is presently a stub, until it's decided how the kernels should
> + support this. */
> +
> +const fenv_t *
> +__fe_mask_env(void)
> +{
> + __set_errno (ENOSYS);
> + return FE_DFL_ENV;
> +}
Why are you sending a patch if it's incomplete? Fix the kernel and then
send a patch. Who knows, maybe a completely different solution is needed.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next prev parent reply other threads:[~2007-05-02 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 22:08 Steven Munroe
2007-05-02 8:22 ` Ulrich Drepper [this message]
2007-05-02 14:06 ` Steven Munroe
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=46384A0D.4070405@redhat.com \
--to=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=munroesj@us.ibm.com \
--cc=rth@twiddle.net \
/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).