From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Avi Kivity <avi@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL][v2] Memory API conversions, batch 5
Date: Mon, 29 Aug 2011 14:14:47 -0500 [thread overview]
Message-ID: <4E5BE527.2010601@codemonkey.ws> (raw)
In-Reply-To: <4E5BBCCB.2020508@siemens.com>
On 08/29/2011 11:22 AM, Jan Kiszka wrote:
> On 2011-08-29 18:17, Jan Kiszka wrote:
>> On 2011-08-29 17:34, Avi Kivity wrote:
>>> Please pull from
>>>
>>> git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git memory/batch
>>>
>>> to receive a fixed version of the latest memory API conversion batch.
>>> The pflash_cfi patch has been reworked extensively, but otherwise there
>>> are no changes.
>>
>> There might be some issues remaining. I've just quickly tested my
>> musicpal image with a firmware update cycle. The version I built from
>> memory/batch failed to start the update while current qemu git
>> succeeded. Need to look closer/bisect the queue later.
>
> OK, that was simple: It's still "pflash_cfi01/pflash_cfi02: convert to
> memory API".
Hrm, okay. Avi, maybe drop that patch and submit a v3?
Regards,
Anthony Liguori
>
> The firmware complains "flash_binary: Can't erase mtd device
> LINUX_ROOT_FS. Error: -5." I guess I need to enable some debug switches,
> but that really has to wait.
>
> Jan
>
next prev parent reply other threads:[~2011-08-29 19:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 15:34 [Qemu-devel] [PULL][v2] Memory API conversions, batch 5 Avi Kivity
2011-08-29 15:42 ` Anthony Liguori
2011-08-29 15:44 ` Avi Kivity
2011-08-29 16:17 ` Jan Kiszka
2011-08-29 16:22 ` Jan Kiszka
2011-08-29 19:14 ` Anthony Liguori
2011-08-29 19:14 ` Anthony Liguori [this message]
2011-08-29 21:15 ` Avi Kivity
2011-08-29 22:38 ` [Qemu-devel] [PATCH] memory: Fix memory_region_get_ram_ptr for ROM devices Jan Kiszka
2011-08-30 8:21 ` Avi Kivity
2011-08-30 11:26 ` Jan Kiszka
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=4E5BE527.2010601@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.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 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).