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

On 08/09/2012 01:36 PM, Peter Maydell wrote:
> On 9 August 2012 21:01, Phil Staub <phils@windriver.com> wrote:
>> 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:
>>>> 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...

Sounds like a plan. I'll give it a go. May not be today, but soon.

Thanks,
Phil

>
> -- PMM
>
>


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

  reply	other threads:[~2012-08-09 21:17 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 [this message]
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=502428E6.4010703@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).