From: Jan Kiszka <jan.kiszka@siemens.com>
To: "BrillyWu@viatech.com.cn" <BrillyWu@viatech.com.cn>
Cc: "KaryJin@viatech.com.cn" <KaryJin@viatech.com.cn>,
"avi@redhat.com" <avi@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] qemu-kvm: Add CPUID support for VIA CPU
Date: Fri, 06 May 2011 12:25:46 +0200 [thread overview]
Message-ID: <4DC3CCAA.5020100@siemens.com> (raw)
In-Reply-To: <C4F7CD9A92DBFF48AD8779355CD4D78912142A@exchsg04.s3graphics.com>
On 2011-05-06 11:37, BrillyWu@viatech.com.cn wrote:
>
>>>
>>> If I want to submit a patch for the qemu-kvm-git, should I
>> use "[QEMU-DEVEL][Patch]..." as the subject? Or there are other rules
>> for qemu-kvm upstream? If yes, would you like to tell me?. Thanks!
>>
>> If you really have to target qemu-kvm only, then you tagging is fine.
>> But this patch does not qualify for such exclusiveness.
>> Rather, your feature should go into upstream's KVM first and will then
>> be merged back into qemu-kvm on next update.
>
> I have submit a patch into upstream's KVM for supporting these features before, and the patch has been applied in kvm-git.
As far as I can see, nothing has been applied to any tree, neither
qemu.git nor qemu-kvm.git.
> Do you mean that I should not submit this patch until the KVM's patch is merged back?
You still need to submit a fixed version of this patch against
qemu-kvm.git, uq/master branch (which is qemu.git effectively). Then
Marcelo or Avi can pick it up and push it to upstream. Once it's merged
there, qemu-kvm.git will update from upstream, and you will have your
patch applied to both trees.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-05-06 10:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 3:03 [Qemu-devel] [PATCH] qemu-kvm: Add CPUID support for VIA CPU BrillyWu
2011-05-05 7:45 ` Jan Kiszka
2011-05-06 1:06 ` BrillyWu
2011-05-06 7:50 ` Jan Kiszka
2011-05-06 9:37 ` BrillyWu
2011-05-06 10:25 ` Jan Kiszka [this message]
2011-05-09 5:28 ` BrillyWu
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=4DC3CCAA.5020100@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=BrillyWu@viatech.com.cn \
--cc=KaryJin@viatech.com.cn \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.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).