linux-mips
[Top] [All Lists]

Re: [PATCH] MIPS: fix code generation for non-DSP capable CPUs

To: linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: fix code generation for non-DSP capable CPUs
From: Florian Fainelli <florian@openwrt.org>
Date: Sat, 16 Mar 2013 15:06:14 +0100
Cc: "Steven J. Hill" <Steven.Hill@imgtec.com>, "ralf@linux-mips.org" <ralf@linux-mips.org>, "blogic@openwrt.org" <blogic@openwrt.org>
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:from:organization:to:subject:date:user-agent:cc :references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=LCJJJxILpnubTQy/uD6B39xlS20WPtkr89WBF6fyWlw=; b=XXFazFpkwI7gZFH1O88zmC8pblsI1JCX3J4GWcN9To0cJXghvZtqS/dvDF+tcCJha5 GWpO7yJ5Ma3uCM6ClMFTl15nB8uRaWO/mKhat04nUg8lzdCV6q7Wa8msB8Dg9pDKEg5N wbYF16toaklAT5luVxjPWX7EavzO7qzqPVqXNPDE6dqY2IR55ofcZ+FIW+jrm0CUYq1R CE4vdBUSFcXDIZjNrXtTpS4fHefMMqb1q5MeC43vlLUmM2X3l6rBCy2v+bhofzO10qvH X1N6pyypAFxSf9niw7EyXYAuVae7T+hFjTuQSlQER+1LFYMsiMgpcBoGsAFEnVSaxPCS +WPA==
In-reply-to: <0573B2AE5BBFFC408CC8740092293B5ACBA1F3@bamail02.ba.imgtec.org>
List-archive: <http://www.linux-mips.org/archives/linux-mips/>
List-help: <mailto:ecartis@linux-mips.org?Subject=help>
List-id: linux-mips <linux-mips.eddie.linux-mips.org>
List-owner: <mailto:ralf@linux-mips.org>
List-post: <mailto:linux-mips@linux-mips.org>
List-software: Ecartis version 1.0.0
List-subscribe: <mailto:ecartis@linux-mips.org?subject=subscribe%20linux-mips>
List-unsubscribe: <mailto:ecartis@linux-mips.org?subject=unsubscribe%20linux-mips>
Organization: OpenWrt
References: <1363267128-8918-1-git-send-email-florian@openwrt.org> <0573B2AE5BBFFC408CC8740092293B5ACBA1F3@bamail02.ba.imgtec.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: KMail/1.13.7 (Linux/3.7-trunk-amd64; KDE/4.8.4; x86_64; ; )
Hey Steven,

Le jeudi 14 mars 2013 15:22:28, Steven J. Hill a écrit :
> Florian,
> 
> Let me test this patch out with our DSP testsuite and then I can give you
> an ACK or NACK. Thanks!

Have you been able to give this a try?
-- 
Florian

<Prev in Thread] Current Thread [Next in Thread>