From: "John 'Warthog9' Hawley" <warthog9@kernel.org>
To: Avi Kivity <avi@redhat.com>
Cc: Konstantin Ryabitsev <mricon@kernel.org>,
"Ren, Yongjie" <yongjie.ren@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
ftpadmin <ftpadmin@kernel.org>
Subject: Re: where should I report kvm kernel bug?
Date: Thu, 05 Jan 2012 19:33:33 -0700 [thread overview]
Message-ID: <4F065D7D.4080206@kernel.org> (raw)
In-Reply-To: <4F0335FA.4080600@redhat.com>
On 01/03/2012 10:08 AM, Avi Kivity wrote:
> On 01/03/2012 06:28 PM, Konstantin Ryabitsev wrote:
>> On Tue, 2012-01-03 at 12:10 +0200, Avi Kivity wrote:
>>> I'm surprised bugzilla.kernel.org isn't responding. Copying
>>> ftpadmin@kernel.org for ETA (though that address isn't responding, either).
>>
>> Hi, Avi and Ren:
>>
>> Unfortunately, we don't currently have an ETA for bringing up
>> bugzilla.kernel.org. We are still awaiting some hardware deliveries
>> before we can recover that service.
>
> The KVM developers suggest a virtual machine in the meantime?
>
>> I suggest you ask KVM developers
>> where they would prefer to have the bug reported.
>
> Ren, please use the qemu bug tracker temporarily, just make sure to mark
> it as a kernel bug.
>
>> Sorry for lack of responses -- the holidays always make it more
>> difficult to respond in time.
>>
>
> Thanks.
>
Ok, I've quietly turned bugzilla back on don't beat it too hard or
you'll start affecting other services but it's alive.
- John
next prev parent reply other threads:[~2012-01-06 2:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 3:02 where should I report kvm kernel bug? Ren, Yongjie
2012-01-03 10:10 ` Avi Kivity
2012-01-03 16:28 ` Konstantin Ryabitsev
2012-01-03 17:08 ` Avi Kivity
2012-01-04 0:54 ` Ren, Yongjie
2012-01-06 2:33 ` John 'Warthog9' Hawley [this message]
2012-01-06 3:27 ` Ren, Yongjie
2012-01-13 7:05 ` Ren, Yongjie
2012-01-13 23:42 ` John 'Warthog9' Hawley
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=4F065D7D.4080206@kernel.org \
--to=warthog9@kernel.org \
--cc=avi@redhat.com \
--cc=ftpadmin@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mricon@kernel.org \
--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 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.