All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: kvm-ppc-devel@lists.sourceforge.net, kvm-devel@lists.sourceforge.net
Subject: Re: [kvm-ppc-devel] [PATCH 00 of 10] Qemu PowerPC fixes and
Date: Sun, 04 May 2008 08:17:04 +0000	[thread overview]
Message-ID: <481D7100.2030808@qumranet.com> (raw)
In-Reply-To: <patchbomb.1209589410@localhost.localdomain>

Hollis Blanchard wrote:
> Avi, please apply these patches to the kvm-userspace repository. I've submitted
> the device emulation patches (UIC and PCI) to qemu-devel, but have received no
> response.
>
>   

Applied all, thanks.

> Thinking ahead to qemu integration, many of these should be folded into a
> single "Bamboo board" patch, but e.g. the device emulation patches are
> logically separate. Do you track qemu patches for upstream integration like
> you do for the kernel? Do you want me to keep these split-out patches locally?
> Unsplitting them later would be a pain...
>   

It's better to keep the patches split.  As you point out, folding 
patches together is easy but splitting them later is hard.  I don't keep 
a qemu patch queue; whether to take patches from kvm-userspace.git or 
rediff against upstream qemu is a decision that is best taken on a 
case-by-case basis, if and when qemu upstream becomes receptive to these 
patches.

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


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel

WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@qumranet.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: kvm-ppc-devel@lists.sourceforge.net, kvm-devel@lists.sourceforge.net
Subject: Re: [PATCH 00 of 10] Qemu PowerPC fixes and enhancements
Date: Sun, 04 May 2008 11:17:04 +0300	[thread overview]
Message-ID: <481D7100.2030808@qumranet.com> (raw)
In-Reply-To: <patchbomb.1209589410@localhost.localdomain>

Hollis Blanchard wrote:
> Avi, please apply these patches to the kvm-userspace repository. I've submitted
> the device emulation patches (UIC and PCI) to qemu-devel, but have received no
> response.
>
>   

Applied all, thanks.

> Thinking ahead to qemu integration, many of these should be folded into a
> single "Bamboo board" patch, but e.g. the device emulation patches are
> logically separate. Do you track qemu patches for upstream integration like
> you do for the kernel? Do you want me to keep these split-out patches locally?
> Unsplitting them later would be a pain...
>   

It's better to keep the patches split.  As you point out, folding 
patches together is easy but splitting them later is hard.  I don't keep 
a qemu patch queue; whether to take patches from kvm-userspace.git or 
rediff against upstream qemu is a decision that is best taken on a 
case-by-case basis, if and when qemu upstream becomes receptive to these 
patches.

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


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

  reply	other threads:[~2008-05-04  8:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 21:03 [kvm-ppc-devel] [PATCH 00 of 10] Qemu PowerPC fixes and enhancements Hollis Blanchard
2008-05-04  8:17 ` Avi Kivity [this message]
2008-05-04  8:17   ` Avi Kivity

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=481D7100.2030808@qumranet.com \
    --to=avi@qumranet.com \
    --cc=hollisb@us.ibm.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=kvm-ppc-devel@lists.sourceforge.net \
    /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.