public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
* kvm-ppc while I'm on vacation
@ 2012-03-18 22:10 Alexander Graf
  2012-03-19 11:56 ` Paul Mackerras
  0 siblings, 1 reply; 3+ messages in thread
From: Alexander Graf @ 2012-03-18 22:10 UTC (permalink / raw)
  To: kvm-ppc
  Cc: KVM devel mailing list, Scott Wood, Paul Mackerras,
	Benjamin Herrenschmidt, Avi Kivity, Marcelo Tosatti, David Gibson

Howdy,

While everyone of you will probably be working on really cool PowerPC stuff, I'll be stuck at the beach with colorful and mysterious diving experiences. Oh well - I guess you can't have everything at once :).

So while I'll try to not kill myself while breathing underwater, we still need to keep the patch flow to Avi going, so the poor PPC KVM target doesn't suffer from it.

Hence I asked Paul to take on temporary maintainership of the kvm-ppc tree for the next 3 weeks. During that time, he'll be allowed to send pull requests to Avi and Marcelo and is obliged to fix the build whenever it breaks :).

However, I'm strongly suggesting that every patch gets at least ACKed by another person knowledgable in that field - especially for Paul's own patches. Ben knows book3s, booke and kernel stuff; I'm sure Avi is happy to help out on any interface questions and Scott knows ... simply everything.

So with that crowd, I don't think it'd be an issue to find someone to ack patches and it'd make things a lot more consistent in the tree. Nothing is more frustrating than a new ABI that you have to revert because nobody looked at it seriously before ;). Don't try that at home kids.


With that said, I'm sure things will work out just fine. Please just make sure I recognize some of the code when I'm back ;).

Alex

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: kvm-ppc while I'm on vacation
  2012-03-18 22:10 kvm-ppc while I'm on vacation Alexander Graf
@ 2012-03-19 11:56 ` Paul Mackerras
  2012-03-19 12:01   ` Avi Kivity
  0 siblings, 1 reply; 3+ messages in thread
From: Paul Mackerras @ 2012-03-19 11:56 UTC (permalink / raw)
  To: Alexander Graf
  Cc: kvm-ppc, KVM devel mailing list, Scott Wood,
	Benjamin Herrenschmidt, Avi Kivity, Marcelo Tosatti, David Gibson

On Sun, Mar 18, 2012 at 11:10:43PM +0100, Alexander Graf wrote:

> Hence I asked Paul to take on temporary maintainership of the
> kvm-ppc tree for the next 3 weeks. During that time, he'll be
> allowed to send pull requests to Avi and Marcelo and is obliged to
> fix the build whenever it breaks :).

Thanks, Alex.

Avi, Marcelo, what do you plan to do with Alex's existing pull
request?  Are you about to do that pull?

Thanks,
Paul.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: kvm-ppc while I'm on vacation
  2012-03-19 11:56 ` Paul Mackerras
@ 2012-03-19 12:01   ` Avi Kivity
  0 siblings, 0 replies; 3+ messages in thread
From: Avi Kivity @ 2012-03-19 12:01 UTC (permalink / raw)
  To: Paul Mackerras
  Cc: Alexander Graf, kvm-ppc, KVM devel mailing list, Scott Wood,
	Benjamin Herrenschmidt, Marcelo Tosatti, David Gibson

On 03/19/2012 01:56 PM, Paul Mackerras wrote:
> On Sun, Mar 18, 2012 at 11:10:43PM +0100, Alexander Graf wrote:
>
> > Hence I asked Paul to take on temporary maintainership of the
> > kvm-ppc tree for the next 3 weeks. During that time, he'll be
> > allowed to send pull requests to Avi and Marcelo and is obliged to
> > fix the build whenever it breaks :).
>
> Thanks, Alex.
>
> Avi, Marcelo, what do you plan to do with Alex's existing pull
> request?  Are you about to do that pull?
>

It looks good to me, I'll pull it if Marcelo doesn't beat me to it.

-- 
error compiling committee.c: too many arguments to function


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2012-03-19 12:02 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-03-18 22:10 kvm-ppc while I'm on vacation Alexander Graf
2012-03-19 11:56 ` Paul Mackerras
2012-03-19 12:01   ` Avi Kivity

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox