From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Graf <agraf@suse.de>,
Peter Crosthwaite <crosthwaitepeter@gmail.com>,
qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, afaerber@suse.de,
Peter Crosthwaite <crosthwaite.peter@gmail.com>
Subject: Re: [Qemu-trivial] [PATCH v2] device-tree: Make a common-obj
Date: Tue, 26 May 2015 01:01:25 +0200 [thread overview]
Message-ID: <5563A9C5.1000603@redhat.com> (raw)
In-Reply-To: <55638A0C.1000902@suse.de>
On 25/05/2015 22:46, Alexander Graf wrote:
>
> On 24.05.15 22:20, Peter Crosthwaite wrote:
>> > There is no reason for device tree API to be built per-target.
>> > common-obj it. There is an extraneous inclusion of config.h that
>> > needs to be removed.
>> >
>> > Cc: Alexander Graf <agraf@suse.de>
>> > Reviewed-by: Andreas Färber <afaerber@suse.de>
>> > Signed-off-by: Peter Crosthwaite <crosthwaite.peter@gmail.com>
> Doesn't this mean that we're now linking against libfdt on
> qemu-system-x86_64?
We already are.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Graf <agraf@suse.de>,
Peter Crosthwaite <crosthwaitepeter@gmail.com>,
qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, afaerber@suse.de,
Peter Crosthwaite <crosthwaite.peter@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v2] device-tree: Make a common-obj
Date: Tue, 26 May 2015 01:01:25 +0200 [thread overview]
Message-ID: <5563A9C5.1000603@redhat.com> (raw)
In-Reply-To: <55638A0C.1000902@suse.de>
On 25/05/2015 22:46, Alexander Graf wrote:
>
> On 24.05.15 22:20, Peter Crosthwaite wrote:
>> > There is no reason for device tree API to be built per-target.
>> > common-obj it. There is an extraneous inclusion of config.h that
>> > needs to be removed.
>> >
>> > Cc: Alexander Graf <agraf@suse.de>
>> > Reviewed-by: Andreas Färber <afaerber@suse.de>
>> > Signed-off-by: Peter Crosthwaite <crosthwaite.peter@gmail.com>
> Doesn't this mean that we're now linking against libfdt on
> qemu-system-x86_64?
We already are.
Paolo
next prev parent reply other threads:[~2015-05-25 23:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 20:20 [Qemu-trivial] [PATCH v2] device-tree: Make a common-obj Peter Crosthwaite
2015-05-24 20:20 ` [Qemu-devel] " Peter Crosthwaite
2015-05-25 20:46 ` [Qemu-trivial] " Alexander Graf
2015-05-25 20:46 ` [Qemu-devel] " Alexander Graf
2015-05-25 23:01 ` Paolo Bonzini [this message]
2015-05-25 23:01 ` Paolo Bonzini
2015-05-25 23:07 ` [Qemu-trivial] " Alexander Graf
2015-05-25 23:07 ` [Qemu-devel] " Alexander Graf
2015-05-28 12:04 ` [Qemu-trivial] " Michael Tokarev
2015-05-28 12:04 ` [Qemu-devel] " Michael Tokarev
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=5563A9C5.1000603@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=crosthwaite.peter@gmail.com \
--cc=crosthwaitepeter@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 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.