All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Staub <phils@windriver.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Phil.Staub@windriver.com, phils@windriver.com,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] MIPS: Correct FCR0 initialization
Date: Thu, 9 Aug 2012 15:23:40 -0700	[thread overview]
Message-ID: <5024386C.5070006@windriver.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1208092303180.20608@tp.orcam.me.uk>

On 08/09/2012 03:09 PM, Maciej W. Rozycki wrote:
> On Thu, 9 Aug 2012, Phil Staub 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.
>
>   Excellent, thanks, I've been just about to get back to them after a long
> distraction.  I should have something to add and to address Richard's
> comments tomorrow or early next week.  If resending patches helps, I can
> certainly do that too -- in any case no pings or such stuff from me
> usually does not mean that I am dead, but only that I've been pulled away
> to something else.

I can relate! :-)

Phil

>
>    Maciej
>
>


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

  reply	other threads:[~2012-08-09 22:23 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 [this message]
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=5024386C.5070006@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.