qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Phil Staub <phils@windriver.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Phil.Staub@windriver.com,
	"Maciej W. Rozycki" <macro@codesourcery.com>,
	qemu-devel@nongnu.org, phils@windriver.com
Subject: Re: [Qemu-devel] [PATCH] MIPS: Correct FCR0 initialization
Date: Thu, 9 Aug 2012 13:01:06 -0700	[thread overview]
Message-ID: <50241702.9010301@windriver.com> (raw)
In-Reply-To: <CAAu8pHt3dSxvqxXAHRuXofEpaJcv=C3dKbb_=5t83x2B1pAyRg@mail.gmail.com>

On 08/09/2012 12:57 PM, Blue Swirl wrote:
> On Tue, Aug 7, 2012 at 12:10 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
>> On 6 August 2012 19:21, Phil Staub <phil.staub@windriver.com> wrote:
>>> On Tue, Jun 12, 2012 at 10:28:14AM -0400, qemu-devel-request@nongnu.org wrote:
>>>> From: Richard Henderson <rth@twiddle.net>
>>>> On 2012-06-07 18:04, Maciej W. Rozycki wrote:
>>>>>   I have verified this change with system emulation running the GDB test
>>>>> suite for the mips-sde-elf target (o32, big endian, 24Kf CPU emulated),
>>>>> there were 55 progressions and no regressions.
>>>>>
>>>>> Signed-off-by: Maciej W. Rozycki <macro@codesourcery.com>
>>>>> ---
>>>>>
>>>>>   Sent on behalf of Nathan, who's since left the company.  Please apply.
>>>>>
>>>>>    Maciej
>>>>>
>>>>> qemu-mips-fcr0.diff
>>>>> Index: qemu-git-trunk/target-mips/translate.c
>>>>> ===================================================================
>>>>> --- qemu-git-trunk.orig/target-mips/translate.c     2012-06-04 05:35:53.245610241 +0100
>>>>> +++ qemu-git-trunk/target-mips/translate.c  2012-06-04 05:39:26.245563823 +0100
>>>>> @@ -12776,6 +12776,7 @@ void cpu_state_reset(CPUMIPSState *env)
>>>>>       env->CP0_SRSConf3 = env->cpu_model->CP0_SRSConf3;
>>>>>       env->CP0_SRSConf4_rw_bitmask = env->cpu_model->CP0_SRSConf4_rw_bitmask;
>>>>>       env->CP0_SRSConf4 = env->cpu_model->CP0_SRSConf4;
>>>>> +    env->active_fpu.fcr0 = env->cpu_model->CP1_fcr0;
>>>>
>>>> Reviewed-by: Richard Henderson <rth@twiddle.net>
>>
>>> What are the plans for this patch? It doesn't appear to have been
>>> applied in any of the repository branches.
>>
>> Basically MIPS is currently without an active maintainer, so
>> people submitting patches need to keep pinging them until
>> one of the core maintainers (usually Blue Swirl) applies them.
>> 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.
>>
>> -- PMM
>
> Thanks, applied.
>
>

Thank you!

Phil


-- 
Phil Staub, Senior Member of Technical Staff, Wind River
Direct: 702.290.0470 Fax: 702.982.0085

  reply	other threads:[~2012-08-09 20:01 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 [this message]
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
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=50241702.9010301@windriver.com \
    --to=phils@windriver.com \
    --cc=Phil.Staub@windriver.com \
    --cc=blauwirbel@gmail.com \
    --cc=macro@codesourcery.com \
    --cc=peter.maydell@linaro.org \
    --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).