From: Anthony Liguori <aliguori@us.ibm.com>
To: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, avi@qumranet.com, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH] qemu: report issues causing the kvm probe to fail v3
Date: Thu, 15 Jan 2009 15:57:48 -0600 [thread overview]
Message-ID: <496FB15C.3090806@us.ibm.com> (raw)
In-Reply-To: <4966FDC1.7070705@linux.vnet.ibm.com>
>>
> This applies to qemu upstream already when not specifying -p or -p 2
> (as I already tested yesterday before submission).
> Well I removed the leading qemu dir manually and updated the -51 lines
> offset (attached), should I change more than that (add the leading
> trunk maybe, atm I'm just not sure what changes you want) ?
Applied. Thanks.
Regards,
Anthony Liguori
prev parent reply other threads:[~2009-01-15 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 13:54 [Qemu-devel] [PATCH] qemu: report issues causing the kvm probe to fail v3 ehrhardt
2009-01-08 15:28 ` [Qemu-devel] " Avi Kivity
2009-01-08 20:34 ` Anthony Liguori
2009-01-09 7:33 ` Christian Ehrhardt
2009-01-15 21:57 ` Anthony Liguori [this message]
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=496FB15C.3090806@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=avi@qumranet.com \
--cc=ehrhardt@linux.vnet.ibm.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).