From: Avi Kivity <avi@redhat.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Maciej Rutecki <maciej.rutecki@gmail.com>,
Florian Mickler <florian@mickler.org>,
Jay Ren <yongjie.ren@intel.com>,
stefanha@linux.vnet.ibm.com, KVM General <kvm@vger.kernel.org>
Subject: Re: [Bug #39412] Win Vista and Win2K8 guests' network breaks down
Date: Mon, 15 Aug 2011 06:38:34 -0700 [thread overview]
Message-ID: <4E49215A.5080103@redhat.com> (raw)
In-Reply-To: <CAOJsxLEToaQe3DrhUQx5FizMnzATxwG8XGCPwZpRFpuBQpq1ug@mail.gmail.com>
On 08/15/2011 03:33 AM, Pekka Enberg wrote:
> On Sun, Aug 14, 2011 at 10:07 PM, Rafael J. Wysocki<rjw@sisk.pl> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.39 and 3.0.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.39 and 3.0. Please verify if it still should
> > be listed and let the tracking team know (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=39412
> > Subject : Win Vista and Win2K8 guests' network breaks down
> > Submitter : Jay Ren<yongjie.ren@intel.com>
> > Date : 2011-07-15 15:31 (31 days old)
>
> The bugzilla report claims that this commit fixes the regression:
>
> http://git.kernel.org/?p=virt/kvm/kvm.git;a=commitdiff;h=e72ef590a3ef3047f6ed5bcb8808a9734f6c4b32
>
> The commit, however, is not in mainline nor does it seem to be tagged
> for -stable.
That commit is completely unrelated.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2011-08-15 13:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <xuTC4jRtHbB.A.l4H.gMCSOB@chimera>
[not found] ` <bkwpSnItbJM.A.nx.VNCSOB@chimera>
2011-08-15 10:33 ` [Bug #39412] Win Vista and Win2K8 guests' network breaks down Pekka Enberg
2011-08-15 13:38 ` Avi Kivity [this message]
[not found] ` <4E49215A.5080103-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-08-15 13:50 ` Pekka Enberg
2011-08-15 14:09 ` Avi Kivity
2011-08-15 14:31 ` Florian Mickler
2011-08-15 19:07 ` Avi Kivity
[not found] ` <4E496E7C.30303-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-08-15 20:17 ` Florian Mickler
[not found] ` <20110815221705.768b56f8-mGsOIKOveelVRbCss4o9kg@public.gmane.org>
2011-08-16 2:04 ` Ren, Yongjie
2011-07-15 15:31 [Bug 39412] New: Win Vista and Win2K8 guests cann't find NIC driver bugzilla-daemon
2011-07-17 10:39 ` [Bug 39412] Win Vista and Win2K8 guests' network breaks down bugzilla-daemon
2011-07-29 11:16 ` bugzilla-daemon
2011-07-29 11:17 ` bugzilla-daemon
2011-08-14 19:13 ` bugzilla-daemon
2011-08-16 2:43 ` bugzilla-daemon
2011-08-21 2:27 ` bugzilla-daemon
2011-08-24 12:29 ` bugzilla-daemon
2011-08-29 8:48 ` bugzilla-daemon
2011-08-29 8:53 ` bugzilla-daemon
2011-08-29 16:23 ` bugzilla-daemon
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=4E49215A.5080103@redhat.com \
--to=avi@redhat.com \
--cc=florian@mickler.org \
--cc=kernel-testers@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=penberg@kernel.org \
--cc=rjw@sisk.pl \
--cc=stefanha@linux.vnet.ibm.com \
--cc=yongjie.ren@intel.com \
/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