From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: <libc-ports@sourceware.org>
Subject: Re: [PATCH] MIPS: Correct the handling of reserved FCSR bits
Date: Thu, 22 Aug 2013 17:12:00 -0000 [thread overview]
Message-ID: <alpine.DEB.1.10.1308221812220.8514@tp.orcam.me.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.1308212152270.21983@digraph.polyomino.org.uk>
On Wed, 21 Aug 2013, Joseph S. Myers wrote:
> > * sysdeps/mips/fpu_control.h: Document bits reserved for
> > architecture implementers.
> > (_FPU_RESERVED): Clear bit #21.
> > * sysdeps/mips/fpu/fedisblxcpt.c (fedisableexcept): Don't clear
> > reserved bits.
> > * sysdeps/mips/fpu/feenablxcpt.c (feenableexcept): Likewise.
>
> OK.
Applied, thanks.
Maciej
prev parent reply other threads:[~2013-08-22 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 21:42 Maciej W. Rozycki
2013-08-21 21:52 ` Joseph S. Myers
2013-08-22 17:12 ` Maciej W. Rozycki [this message]
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=alpine.DEB.1.10.1308221812220.8514@tp.orcam.me.uk \
--to=macro@codesourcery.com \
--cc=joseph@codesourcery.com \
--cc=libc-ports@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).