linux-parisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@systemhalted.org>
To: John David Anglin <dave.anglin@bell.net>
Cc: Rolf Eike Beer <eike-kernel@sf-tec.de>,
	linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] parisc: futex: Use same lock set as lws calls
Date: Sun, 30 Oct 2011 20:21:31 -0400	[thread overview]
Message-ID: <CADZpyizsC-eSgCSyK52-Ns12z+mWUpFB8JH2dC2C7J_3EnGR5Q@mail.gmail.com> (raw)
In-Reply-To: <BLU0-SMTP8183F951B80BB9F5455EB297D10@phx.gbl>

On Sun, Oct 30, 2011 at 12:13 PM, John David Anglin
<dave.anglin@bell.net> wrote:
> On 30-Oct-11, at 11:31 AM, Rolf Eike Beer wrote:
>
>> John David Anglin wrote:
>>
>>> This problem is fixed in the GCC trunk and 4.4, 4.5 and 4.6 branche=
s.
>>> libmpfr4-3.1.0 now passes all tests.
>>
>> Can we get a link to a bug or a commit so we could easily put this i=
nto
>> the
>> gentoo patchset for local usage until a new version is released?
>
>
> The trunk patch is on the gcc-patches list:
> http://gcc.gnu.org/ml/gcc-patches/2011-10/msg02758.html
>
> There are two variants of the patch:
> http://gcc.gnu.org/viewcvs?view=3Drevision&revision=3D180655
> http://gcc.gnu.org/viewcvs?view=3Drevision&revision=3D180662
>
> The first is for 4.7. =A0The latter applies to 4.4, 4.5 and 4.6.

Awesome! Great work Dave! :-)

Cheers,
Carlos.
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc"=
 in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-10-31  0:21 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09 20:40 [PATCH] parisc: futex: Use same lock set as lws calls John David Anglin
2011-10-10 14:30 ` Rolf Eike Beer
2011-10-10 20:27   ` John David Anglin
2011-10-10 20:30     ` James Bottomley
2011-10-17 15:23 ` Domenico Andreoli
2011-10-17 15:47   ` Carlos O'Donell
2011-10-17 18:10     ` John David Anglin
2011-10-17 20:55       ` Carlos O'Donell
2011-10-17 21:09         ` John David Anglin
2011-10-17 21:57           ` Domenico Andreoli
2011-10-17 22:28             ` John David Anglin
2011-10-18  9:31               ` Domenico Andreoli
2011-10-18  9:33               ` Domenico Andreoli
2011-10-18 14:20                 ` John David Anglin
2011-10-18  3:01           ` Carlos O'Donell
2011-10-18  3:21             ` Carlos O'Donell
2011-10-18 21:22               ` Carlos O'Donell
2011-10-20 15:35           ` Carlos O'Donell
2011-10-20 17:57             ` Matt Turner
2011-10-20 18:11               ` Carlos O'Donell
2011-10-20 18:16                 ` Matt Turner
2011-10-20  1:47       ` John David Anglin
2011-10-21 14:49         ` Carlos O'Donell
2011-10-21 17:42           ` John David Anglin
2011-10-21 18:11             ` John David Anglin
2011-10-21 18:15               ` Carlos O'Donell
2011-10-30 15:04                 ` John David Anglin
2011-10-30 15:31                   ` Rolf Eike Beer
2011-10-30 16:13                     ` John David Anglin
2011-10-31  0:21                       ` Carlos O'Donell [this message]
2011-10-31  1:36                         ` John David Anglin
2011-10-31  9:41                           ` Domenico Andreoli
2011-10-31 12:28                             ` John David Anglin
2011-10-31 23:26                             ` John David Anglin
2011-11-01  9:15                               ` Domenico Andreoli
2011-11-01  2:15                           ` Carlos O'Donell
2011-11-01  9:19                             ` Domenico Andreoli
2011-11-01 19:56                               ` John David Anglin

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=CADZpyizsC-eSgCSyK52-Ns12z+mWUpFB8JH2dC2C7J_3EnGR5Q@mail.gmail.com \
    --to=carlos@systemhalted.org \
    --cc=dave.anglin@bell.net \
    --cc=eike-kernel@sf-tec.de \
    --cc=linux-parisc@vger.kernel.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 NNTP newsgroup(s).