From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?ISO-8859-1?Q?Matthias_Wei=DFer?= <weisserm@arcor.de>
Date: Thu, 30 Jun 2011 08:31:56 +0200
Subject: [U-Boot] [PATCH V2] memcpy/memmove: Do not copy to same address
In-Reply-To: <4DF6FD2C.9090903@arcor.de>
References: <1302591520-12517-1-git-send-email-weisserm@arcor.de>
	<1306141435-24001-1-git-send-email-weisserm@arcor.de>
	<4DF6FD2C.9090903@arcor.de>
Message-ID: <4E0C185C.4090701@arcor.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Dear Wolfgang

Am 14.06.2011 08:18, schrieb Matthias Wei?er:
> Am 23.05.2011 11:03, schrieb Matthias Weisser:
>> In some cases (e.g. bootm with a elf payload which is already at the right
>> position) there is a in place copy of data to the same address. Catching this
>> saves some ms while booting.
>
> What about this patch? As the initial submission of the patch was inside
> the merge window (see http://patchwork.ozlabs.org/patch/90725/) I would
> like to see the current version of this patch (see
> http://patchwork.ozlabs.org/patch/96841/) in the upcoming release.

May I kindly ask you if http://patchwork.ozlabs.org/patch/96841/ can go 
in as the merge window is now open again?

Thanks
Matthias