All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: BrillyWu <brillywu@gmail.com>
Cc: BrillyWu@viatech.com.cn, avi@redhat.com, mtosatti@redhat.com,
	qemu-devel@nongnu.org, mst@redhat.com, KaryJin@viatech.com.cn,
	kvm@vger.kernel.org
Subject: Re: [PATCH uq/master V2] kvm: Add CPUID support for VIA CPU
Date: Mon, 30 May 2011 09:47:37 +0200	[thread overview]
Message-ID: <4DE34B99.2000505@web.de> (raw)
In-Reply-To: <BANLkTi=A_6-3fRcd+LYcznZuNKmKHEVB-Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 553 bytes --]

On 2011-05-30 09:40, BrillyWu wrote:
> From: BrillyWu <brillywu@viatech.com.cn>
> 
> Hi, Jan
>          I'm very sorry for these bugs in the patch. Now I have made a
> new patch based on the
> newest uq/master where the patch has been applied to fix these bugs,
> is it feasible? If it is
> not acceptable, should I re-generate a patch based on previous
> uq/master, or what else?

A clean patch (which passed checkpatch...) against uq/master without the
broken version is required. We can't push a non-bisectable series upstream.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@web.de>
To: BrillyWu <brillywu@gmail.com>
Cc: kvm@vger.kernel.org, KaryJin@viatech.com.cn, mst@redhat.com,
	mtosatti@redhat.com, BrillyWu@viatech.com.cn,
	qemu-devel@nongnu.org, avi@redhat.com
Subject: Re: [Qemu-devel] [PATCH uq/master V2] kvm: Add CPUID support for VIA CPU
Date: Mon, 30 May 2011 09:47:37 +0200	[thread overview]
Message-ID: <4DE34B99.2000505@web.de> (raw)
In-Reply-To: <BANLkTi=A_6-3fRcd+LYcznZuNKmKHEVB-Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 553 bytes --]

On 2011-05-30 09:40, BrillyWu wrote:
> From: BrillyWu <brillywu@viatech.com.cn>
> 
> Hi, Jan
>          I'm very sorry for these bugs in the patch. Now I have made a
> new patch based on the
> newest uq/master where the patch has been applied to fix these bugs,
> is it feasible? If it is
> not acceptable, should I re-generate a patch based on previous
> uq/master, or what else?

A clean patch (which passed checkpatch...) against uq/master without the
broken version is required. We can't push a non-bisectable series upstream.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  reply	other threads:[~2011-05-30  7:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10  8:02 [PATCH uq/master V2] kvm: Add CPUID support for VIA CPU BrillyWu
2011-05-10  8:02 ` [Qemu-devel] " BrillyWu
2011-05-11 11:50 ` Avi Kivity
2011-05-11 11:50   ` [Qemu-devel] " Avi Kivity
2011-05-28 10:28 ` Jan Kiszka
2011-05-28 10:28   ` [Qemu-devel] " Jan Kiszka
2011-05-28 16:20 ` Jan Kiszka
2011-05-28 16:20   ` [Qemu-devel] " Jan Kiszka
2011-05-30  4:02   ` BrillyWu
2011-05-30  4:02     ` [Qemu-devel] " BrillyWu
2011-05-30  7:40     ` BrillyWu
2011-05-30  7:40       ` [Qemu-devel] " BrillyWu
2011-05-30  7:47       ` Jan Kiszka [this message]
2011-05-30  7:47         ` Jan Kiszka
2011-05-30  8:59       ` BrillyWu
2011-05-30  8:59         ` [Qemu-devel] " BrillyWu
2011-05-30 10:45         ` Jan Kiszka
2011-05-30 10:45           ` [Qemu-devel] " Jan Kiszka
2011-05-31  1:25           ` BrillyWu
2011-05-31  1:25             ` [Qemu-devel] " BrillyWu
2011-05-31  6:11             ` Jan Kiszka
2011-05-31  6:11               ` [Qemu-devel] " Jan Kiszka
2011-05-31  7:39               ` BrillyWu
2011-05-31  7:39                 ` [Qemu-devel] " BrillyWu
2011-05-31  7:50                 ` Jan Kiszka
2011-05-31  7:50                   ` [Qemu-devel] " Jan Kiszka
2011-05-31  8:22                   ` BrillyWu
2011-05-31  8:22                     ` [Qemu-devel] " 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=4DE34B99.2000505@web.de \
    --to=jan.kiszka@web.de \
    --cc=BrillyWu@viatech.com.cn \
    --cc=KaryJin@viatech.com.cn \
    --cc=avi@redhat.com \
    --cc=brillywu@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --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.