From: Florian Fainelli <florian@openwrt.org>
To: "Steven J. Hill" <Steven.Hill@imgtec.com>
Cc: "ralf@linux-mips.org" <ralf@linux-mips.org>,
"blogic@openwrt.org" <blogic@openwrt.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: [PATCH] MIPS: fix code generation for non-DSP capable CPUs
Date: Sun, 17 Mar 2013 15:26:29 +0100 [thread overview]
Message-ID: <4237452.TNx7F0KE0x@bender> (raw)
In-Reply-To: <0573B2AE5BBFFC408CC8740092293B5ACBB9B0@bamail02.ba.imgtec.org>
On Saturday 16 March 2013 20:52:44 Steven J. Hill wrote:
> Florian,
>
> I just tested this patch with our DSP testsuite and everything works. I also
disassembled the vmlinux ELF binary to make sure the instructions were being
generated correctly.
>
>
> Acked-by: Steven J. Hill <Steven.Hill@imgtec.com>
Great, thanks Steven!
--
Florian
next prev parent reply other threads:[~2013-03-17 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 13:18 [PATCH] MIPS: fix code generation for non-DSP capable CPUs Florian Fainelli
2013-03-14 14:22 ` Steven J. Hill
2013-03-16 14:06 ` Florian Fainelli
2013-03-16 20:52 ` Steven J. Hill
2013-03-17 14:26 ` Florian Fainelli [this message]
2013-03-18 16:56 ` [PATCH v2] " Florian Fainelli
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=4237452.TNx7F0KE0x@bender \
--to=florian@openwrt.org \
--cc=Steven.Hill@imgtec.com \
--cc=blogic@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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