From: Ralf Baechle <ralf@linux-mips.org>
To: James Hogan <james.hogan@imgtec.com>
Cc: linux-mips@linux-mips.org, Paul Burton <paul.burton@imgtec.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 0/4] MIPS: MSA fixes
Date: Fri, 15 Apr 2016 12:11:52 +0200 [thread overview]
Message-ID: <20160415101152.GJ1524@linux-mips.org> (raw)
In-Reply-To: <1460711246-4394-1-git-send-email-james.hogan@imgtec.com>
On Fri, Apr 15, 2016 at 10:07:22AM +0100, James Hogan wrote:
> Here are some miscellaneous fixes for MSA (MIPS SIMD Architecture)
> support:
> 1) Fix MSA build with recent toolchains
> 2) Fix 32-bit pointer additions on 64-bit with non-MSA capable
> toolchain.
> 3) Fix MSA + 64-bit + lockdep build due to large immediate offsets
> 4) Fix some MSA assembler warnings due to missing .set fp=64
>
> James Hogan (3):
> MIPS: Fix MSA ld_*/st_* asm macros to use PTR_ADDU
> MIPS: Fix MSA assembly with big thread offsets
> MIPS: Fix MSA assembly warnings
>
> Paul Burton (1):
> MIPS: Use copy_s.fmt rather than copy_u.fmt
Thanks, whole series applied.
Ralf
prev parent reply other threads:[~2016-04-15 10:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 9:07 [PATCH 0/4] MIPS: MSA fixes James Hogan
2016-04-15 9:07 ` James Hogan
2016-04-15 9:07 ` [PATCH 1/4] MIPS: Use copy_s.fmt rather than copy_u.fmt James Hogan
2016-04-15 9:07 ` James Hogan
2016-04-15 9:59 ` Ralf Baechle
2016-04-15 10:15 ` James Hogan
2016-04-15 10:15 ` James Hogan
2016-04-15 10:28 ` Ralf Baechle
2016-04-15 9:07 ` [PATCH 2/4] MIPS: Fix MSA ld_*/st_* asm macros to use PTR_ADDU James Hogan
2016-04-15 9:07 ` James Hogan
2016-04-15 9:07 ` [PATCH 3/4] MIPS: Fix MSA assembly with big thread offsets James Hogan
2016-04-15 9:07 ` James Hogan
2016-04-15 9:07 ` [PATCH 4/4] MIPS: Fix MSA assembly warnings James Hogan
2016-04-15 9:07 ` James Hogan
2016-04-15 10:11 ` Ralf Baechle [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=20160415101152.GJ1524@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=james.hogan@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=paul.burton@imgtec.com \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.