From: Peter Maydell <peter.maydell@linaro.org>
To: manish tiwari <tiwari.manish.0998@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Beaglebone Black emulation
Date: Sun, 3 May 2015 23:11:11 +0100 [thread overview]
Message-ID: <CAFEAcA-mX7bC_0Z6Yspi3wd=Gu+7M-iTzcqJo3__aAtkVX4cow@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA-HwxFawZZ5-JVFiudDVsBt6ickUTyT=zyG9rNDQ+Q4_w@mail.gmail.com>
On 3 May 2015 at 17:45, Peter Maydell <peter.maydell@linaro.org> wrote:
> 1) rebase the patchset on to qemu master and fix up
> the breakage due to API changes in qemu
> [this will be moderately painful if you haven't been
> following the API changes as they happened; if you're
> interested in taking on the omap3 patches then I can
> do this step for you because it will be a lot faster...]
I went ahead and did this part.
-- PMM
prev parent reply other threads:[~2015-05-03 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 11:17 [Qemu-devel] Beaglebone Black emulation manish tiwari
2015-05-03 16:45 ` Peter Maydell
2015-05-03 22:11 ` Peter Maydell [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='CAFEAcA-mX7bC_0Z6Yspi3wd=Gu+7M-iTzcqJo3__aAtkVX4cow@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=tiwari.manish.0998@gmail.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).