From: Peter Maydell <peter.maydell@linaro.org>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: qemu list <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] KVM call agenda for 2014-05-13
Date: Mon, 12 May 2014 12:09:16 +0100 [thread overview]
Message-ID: <CAFEAcA9zMYTd5noO68ofbLe70sMGxcMgAC8jvyw0WFByrkJASA@mail.gmail.com> (raw)
In-Reply-To: <CAEgOgz49P-3Ru_+-BD3Mo8Y_ftnhZBUpMa9OE+5vEqFUW2ohjA@mail.gmail.com>
On 12 May 2014 11:30, Peter Crosthwaite <peter.crosthwaite@xilinx.com> wrote:
> On Mon, May 12, 2014 at 7:44 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
>> On 12 May 2014 10:10, Juan Quintela <quintela@redhat.com> wrote:
>>> Please, send any topic that you are interested in covering.
>>>
>>> - QOMifying both Memory regions and GPIOs and attaching them via QOM
>>> links (Peter Crosthwaite)
>>
>> Is there some further useful material on-list on this subject, or
>> are we just going to have a rerun of the discussions on the
>> last two calls?
> I have any ugly work-in-progress series. TBH I was going to wait for
> discussion outcomes. Want me to RFC it?
I don't think you necessarily need to post code, but maybe a writeup
of current status/options would be useful to try to make the on-call
discussion productive?
thanks
-- PMM
next prev parent reply other threads:[~2014-05-12 11:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 9:10 [Qemu-devel] KVM call agenda for 2014-05-13 Juan Quintela
2014-05-12 9:44 ` Peter Maydell
2014-05-12 10:30 ` Peter Crosthwaite
2014-05-12 11:09 ` Peter Maydell [this message]
2014-05-12 23:27 ` Peter Crosthwaite
2014-05-13 10:44 ` Peter Maydell
2014-05-13 11:07 ` Peter Crosthwaite
2014-05-13 11:31 ` Peter Maydell
2014-05-13 10:21 ` Andreas Färber
2014-05-13 10:33 ` Peter Crosthwaite
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=CAFEAcA9zMYTd5noO68ofbLe70sMGxcMgAC8jvyw0WFByrkJASA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=peter.crosthwaite@xilinx.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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;
as well as URLs for NNTP newsgroup(s).