From: Markus Armbruster <armbru@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] Create shared-obj-y
Date: Tue, 11 May 2010 13:45:00 +0200 [thread overview]
Message-ID: <m3fx1ybr2b.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <967a05760ff3819dd26ae0e9e2fb2062e34c265f.1273576209.git.quintela@redhat.com> (Juan Quintela's message of "Tue, 11 May 2010 13:13:16 +0200")
Juan Quintela <quintela@redhat.com> writes:
> This variable contains the objects shared between tools and qemu binary.
> Add qemu-error.o only in one place, it "could" be built in two places
> depending of make ordering.
Yup, that's what I should've done when I added qemu-error.c.
next prev parent reply other threads:[~2010-05-11 11:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 11:13 [Qemu-devel] [PATCH 0/2] Makefile: remoeve duplicate qemu-error.o Juan Quintela
2010-05-11 11:13 ` [Qemu-devel] [PATCH 1/2] Create shared-obj-y Juan Quintela
2010-05-11 11:45 ` Markus Armbruster [this message]
2010-05-11 11:52 ` Kevin Wolf
2010-05-11 12:07 ` Markus Armbruster
2010-05-11 12:17 ` [Qemu-devel] " Juan Quintela
2010-05-11 11:13 ` [Qemu-devel] [PATCH 2/2] state that fsdev depends on LINUX only once Juan Quintela
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=m3fx1ybr2b.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.