From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Neuling <mikey@neuling.org>
Cc: mikey@neuling.org, linuxppc-dev@lists.ozlabs.org, cyrilbur@gmail.com
Subject: Re: powerpc: Fix asm offsets to point to actual FP and VMX regs
Date: Thu, 29 Jun 2017 22:21:06 +1000 (AEST) [thread overview]
Message-ID: <3wyzKG2Twgz9s3s@ozlabs.org> (raw)
In-Reply-To: <20170508062331.11074-1-mikey@neuling.org>
On Mon, 2017-05-08 at 06:23:31 UTC, Michael Neuling wrote:
> The asm code assumes the FP regs are at the start of fp_state. While
> this is true now, it may not always be the case and there is nothing
> enforcing it.
>
> This fixes the asm-offsets to point to the actual FP registers inside
> the fp_state. Similarly for VMX.
>
> Signed-off-by: Michael Neuling <mikey@neuling.org>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/aa9a95163638bd9acb3e1f61f48cd5
cheers
prev parent reply other threads:[~2017-06-29 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 6:23 [PATCH] powerpc: Fix asm offsets to point to actual FP and VMX regs Michael Neuling
2017-06-29 12:21 ` Michael Ellerman [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=3wyzKG2Twgz9s3s@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=cyrilbur@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.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;
as well as URLs for NNTP newsgroup(s).