Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Florian Fainelli <florian@openwrt.org>
To: linux-mips@linux-mips.org
Cc: "Steven J. Hill" <sjhill@mips.com>, ralf@linux-mips.org
Subject: Re: [PATCH v3] MIPS: dsp: Add assembler support for DSP ASEs.
Date: Sat, 05 Jan 2013 13:49:35 +0100	[thread overview]
Message-ID: <28281784.2mN2Dnoq8K@bender> (raw)
In-Reply-To: <1357243312-23070-1-git-send-email-sjhill@mips.com>

On Thursday 03 January 2013 14:01:52 Steven J. Hill wrote:
> From: "Steven J. Hill" <sjhill@mips.com>
> 
> Newer toolchains support the DSP and DSP Rev2 instructions. This patch
> performs a check for that support and adds compiler and assembler
> flags for only the files that need use those instructions.
> 
> Signed-off-by: Steven J. Hill <sjhill@mips.com>

Acked-by: Florian Fainelli <florian@openwrt.org>

Thanks Steven!
-- 
Florian

      reply	other threads:[~2013-01-05 12:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 20:01 [PATCH v3] MIPS: dsp: Add assembler support for DSP ASEs Steven J. Hill
2013-01-05 12:49 ` Florian Fainelli [this message]

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=28281784.2mN2Dnoq8K@bender \
    --to=florian@openwrt.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=sjhill@mips.com \
    /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