qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] MIPS: Correct FCR0 initialization


From: Andreas Färber
Subject: Re: [Qemu-devel] [PATCH] MIPS: Correct FCR0 initialization
Date: Fri, 10 Aug 2012 10:48:43 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120713 Thunderbird/14.0

Am 09.08.2012 22:36, schrieb Peter Maydell:
> On 9 August 2012 21:01, Phil Staub <address@hidden> wrote:
>> On 08/09/2012 12:57 PM, Blue Swirl wrote:
>>> On Tue, Aug 7, 2012 at 12:10 PM, Peter Maydell <address@hidden>
>>> wrote:
>>>> For this purpose the usual approach is to follow up to the patch
>>>> mail saying "Ping" and giving a url to the patch in patchwork,
>>>> like this one:
>>>> http://patchwork.ozlabs.org/patch/163705/
>>>>
>>>> Eventually somebody will take pity on it and apply it, but
>>>> it does require a bit more persistence than for more actively
>>>> maintained areas of the codebase.
>>>
>>> Thanks, applied.
> 
>> Thank you!
> 
> Maciej submitted some other MIPS patches at about the same time:
> http://patchwork.ozlabs.org/project/qemu-devel/list/?submitter=4977
> at least some of which got reviewed by Richard Henderson and are
> therefore good candidates to get committed, if you can fish them out
> of the list and ping them...

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.

Regards,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg



reply via email to

[Prev in Thread] Current Thread [Next in Thread]