From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: phils@windriver.com, Phil.Staub@windriver.com,
qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
"Maciej W. Rozycki" <macro@codesourcery.com>,
Meador Inge <meadori@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] MIPS: Correct FCR0 initialization
Date: Fri, 10 Aug 2012 11:13:43 +0200 [thread overview]
Message-ID: <5024D0C7.6080603@suse.de> (raw)
In-Reply-To: <CAFEAcA_uSdty8r69GBa3uAY7OXaSTbok-Uog_z4v2xJu0QOM4g@mail.gmail.com>
Am 10.08.2012 11:00, schrieb Peter Maydell:
> On 10 August 2012 09:48, Andreas Färber <afaerber@suse.de> wrote:
>> Actually there were better patches for the same bug by Meador, including
>> git-style rather than SVN patches and adding a helper to initialize it
>> consistently at all call sites.
>>
>> There's also DSP, Octeon, mips64 and signal handling patches around that
>> someone needs to volunteer to update, test, clean up and queue.
>> That a patch is on the list doesn't imply that it "just" needs to be
>> applied though. So please be careful which patches you ping.
>
> Yes, hence my suggestion to look for patches which got reviewed.
>
> (Although speaking as somebody who has in the past submitted patches
> which got neither reviewed nor rejected, I have some sympathy for the
> idea that if nobody among us cares enough to look at a patch at all the
> default should be to apply it.)
>From my memory Maciej himself retracted his patches in reaction to a
reply from his colleague Meador. That might not show up when looking at
just one unthreaded reply-less patch, so in general ack but needs to
look at context, too.
Doing follow-ups based on this one or, in worst case, reverting is
certainly possible but the decision-making would best be done by someone
who actually uses mips - not that there's no users, just no volunteer
for a staging tree yet.
/-F
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-08-10 9:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.186707.1339511294.854.qemu-devel@nongnu.org>
2012-08-06 18:21 ` [Qemu-devel] [PATCH] MIPS: Correct FCR0 initialization Phil Staub
2012-08-07 12:10 ` Peter Maydell
2012-08-07 14:56 ` Phil Staub
2012-08-09 19:57 ` Blue Swirl
2012-08-09 20:01 ` Phil Staub
2012-08-09 20:36 ` Peter Maydell
2012-08-09 21:17 ` Phil Staub
2012-08-09 22:09 ` Maciej W. Rozycki
2012-08-09 22:23 ` Phil Staub
2012-08-10 8:48 ` Andreas Färber
2012-08-10 9:00 ` Peter Maydell
2012-08-10 9:13 ` Andreas Färber [this message]
2012-08-10 13:15 ` Maciej W. Rozycki
2012-08-10 14:30 ` Andreas Färber
2012-08-10 21:51 ` Meador Inge
2012-08-10 23:16 ` Maciej W. Rozycki
2012-06-08 1:04 Maciej W. Rozycki
2012-06-12 14:14 ` Richard Henderson
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=5024D0C7.6080603@suse.de \
--to=afaerber@suse.de \
--cc=Phil.Staub@windriver.com \
--cc=blauwirbel@gmail.com \
--cc=macro@codesourcery.com \
--cc=meadori@codesourcery.com \
--cc=peter.maydell@linaro.org \
--cc=phils@windriver.com \
--cc=qemu-devel@nongnu.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).