From: Peter Maydell <peter.maydell@linaro.org>
To: Fabien Chouteau <chouteau@adacore.com>
Cc: "Blue Swirl" <blauwirbel@gmail.com>,
"Sebastian Huber" <sebastian.huber@embedded-brains.de>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Andreas Färber" <afaerber@suse.de>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v4] target-sparc: Add and use CPU_FEATURE_CASA
Date: Wed, 26 Feb 2014 17:25:22 +0000 [thread overview]
Message-ID: <CAFEAcA9Du_wRLMyLiFKOeRDpgr4xnSBFKFbhSx8bFtwARwSnQA@mail.gmail.com> (raw)
In-Reply-To: <530E1D81.2000108@adacore.com>
On 26 February 2014 16:59, Fabien Chouteau <chouteau@adacore.com> wrote:
> On 02/26/2014 08:56 AM, Sebastian Huber wrote:
>> Hello,
>>
>> exists there someone who is able to commit this?
>>
>
> I'm sorry Sebastian, as you probably understood the SPARC maintainer is
> missing which makes commit process more difficult that it used to be...
>
> Peter, as discussed in a previous mail, do you agree to apply SPARC
> patches that have been reviewed?
My preference is for one of the people who does care about SPARC
to take on the job of assembling these patches into pull requests,
testing them, checking they're not obviously broken or lunatic, etc.
Mark Cave-Ayland has been doing this recently, so I would prefer
this patch to go via his tree if he is happy with it and willing to take it.
thanks
-- PMM
next prev parent reply other threads:[~2014-02-26 17:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 16:06 [Qemu-devel] [PATCH v4] target-sparc: Add and use CPU_FEATURE_CASA Sebastian Huber
2014-02-14 16:22 ` Andreas Färber
2014-02-26 7:56 ` Sebastian Huber
2014-02-26 16:59 ` Fabien Chouteau
2014-02-26 17:25 ` Peter Maydell [this message]
2014-02-28 9:33 ` Mark Cave-Ayland
2014-02-28 11:25 ` Fabien Chouteau
2014-03-08 20:16 ` Mark Cave-Ayland
2014-03-08 20:35 ` Peter Maydell
2014-03-09 10:19 ` Sebastian Huber
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=CAFEAcA9Du_wRLMyLiFKOeRDpgr4xnSBFKFbhSx8bFtwARwSnQA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=afaerber@suse.de \
--cc=blauwirbel@gmail.com \
--cc=chouteau@adacore.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=sebastian.huber@embedded-brains.de \
/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).