From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"qemu-ppc@nongnu.org List" <qemu-ppc@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>,
"qemu-devel qemu-devel" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 1/4] PPC: e500: rename mpc8544ds into generic file
Date: Mon, 2 Jul 2012 16:28:19 -0500 [thread overview]
Message-ID: <4FF21273.2040307@freescale.com> (raw)
In-Reply-To: <17B4AA66-74DA-47D6-BB0B-12EA67B6C7F1@suse.de>
On 07/02/2012 04:17 PM, Alexander Graf wrote:
>
> On 02.07.2012, at 23:16, Scott Wood wrote:
>
>> On 07/02/2012 04:08 PM, Alexander Graf wrote:
>>>
>>> On 02.07.2012, at 23:07, Scott Wood wrote:
>>>
>>>> How is hw/ppc/e500.o better than ppc/e500.o?
>>>
>>> If I read this correctly, he's suggesting "e500.o" :)
>>
>> No, plain "e500.o" won't work no matter where you put it in the makefile
>> (unless you add more global prefix setting). I think he's suggesting
>> that the plan is to eventually migrate to everything specifying its full
>> path, though I don't see why.
>
> Why wouldn't "e500.o" in hw/ppc/Makefile.objs work? I'd hope we traverse the target specific path first, no?
Sigh, my fault for trying to read a makefile on short sleep. I hadn't
paid enough attention to exactly what that addprefix was doing. :-P
Will fix.
-Scott
next prev parent reply other threads:[~2012-07-02 21:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120627235055.GA9149@tyr.buserror.net>
2012-07-02 16:50 ` [Qemu-devel] [PATCH 1/4] PPC: e500: rename mpc8544ds into generic file Andreas Färber
2012-07-02 17:06 ` Scott Wood
2012-07-02 20:32 ` [Qemu-devel] [Qemu-ppc] " Scott Wood
2012-07-02 20:58 ` Andreas Färber
2012-07-02 21:07 ` Scott Wood
2012-07-02 21:08 ` Alexander Graf
2012-07-02 21:16 ` Scott Wood
2012-07-02 21:17 ` Alexander Graf
2012-07-02 21:28 ` Scott Wood [this message]
2012-07-03 11:33 ` Paolo Bonzini
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=4FF21273.2040307@freescale.com \
--to=scottwood@freescale.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).