From: Aurelien Jarno <aurelien@aurel32.net>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Anthony Green <green@moxielogic.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v11 0/4] Moxie CPU port
Date: Sun, 24 Mar 2013 01:16:11 +0100 [thread overview]
Message-ID: <20130324001611.GA11420@hall.aurel32.net> (raw)
In-Reply-To: <CAAu8pHt_G93F8=zBBsiQJozsuNP3QJePU8R7fvD8OmtMzSpS2g@mail.gmail.com>
On Sat, Mar 23, 2013 at 06:22:39PM +0000, Blue Swirl wrote:
> On Mon, Mar 18, 2013 at 7:49 PM, Anthony Green <green@moxielogic.com> wrote:
> > This version of the patch addresses recent changes in the upstream
> > qemu sources (where interrupt_request resides).
> >
> > Please consider applying this version of the patch.
>
> Thanks, applied all.
>
After these commits, QEMU doesn't build anymore:
| $ make
| make[1]: *** No rule to make target `hw/moxie/../device_tree.o', needed by `qemu-system-moxie'. Stop.
| make: *** [subdir-moxie-softmmu] Error 2
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
prev parent reply other threads:[~2013-03-24 0:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 19:49 [Qemu-devel] [PATCH v11 0/4] Moxie CPU port Anthony Green
2013-03-18 19:49 ` [Qemu-devel] [PATCH v11 1/4] Add moxie target code Anthony Green
2013-03-18 19:49 ` [Qemu-devel] [PATCH v11 2/4] Add moxie disassembler Anthony Green
2013-03-18 19:49 ` [Qemu-devel] [PATCH v11 3/4] Add sample moxie system Anthony Green
2013-03-18 19:49 ` [Qemu-devel] [PATCH v11 4/4] Add top level changes for moxie Anthony Green
2013-03-23 18:22 ` [Qemu-devel] [PATCH v11 0/4] Moxie CPU port Blue Swirl
2013-03-24 0:16 ` Aurelien Jarno [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=20130324001611.GA11420@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=green@moxielogic.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).