From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:58190)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <B07421@freescale.com>) id 1SloAY-0002TF-S2
	for qemu-devel@nongnu.org; Mon, 02 Jul 2012 17:28:32 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <B07421@freescale.com>) id 1SloAW-0001T6-L6
	for qemu-devel@nongnu.org; Mon, 02 Jul 2012 17:28:30 -0400
Message-ID: <4FF21273.2040307@freescale.com>
Date: Mon, 2 Jul 2012 16:28:19 -0500
From: Scott Wood <scottwood@freescale.com>
MIME-Version: 1.0
References: <20120627235055.GA9149@tyr.buserror.net>
	<4FF1D151.6050604@suse.de> <4FF1D4F8.1020708@freescale.com>
	<4FF20575.9090708@freescale.com> <4FF20B89.7030007@suse.de>
	<4FF20D85.20609@freescale.com>
	<4BF58A38-954C-49A8-BDBD-3CE15D379BBF@suse.de>
	<4FF20FAA.5000306@freescale.com>
	<17B4AA66-74DA-47D6-BB0B-12EA67B6C7F1@suse.de>
In-Reply-To: <17B4AA66-74DA-47D6-BB0B-12EA67B6C7F1@suse.de>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 1/4] PPC: e500: rename mpc8544ds
 into generic file
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Alexander Graf <agraf@suse.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>, "qemu-ppc@nongnu.org
	List" <qemu-ppc@nongnu.org>, =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= <afaerber@suse.de>, qemu-devel qemu-devel <qemu-devel@nongnu.org>

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