linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dave.martin@linaro.org (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: kuser: consistently use usr_ret for returning from helpers
Date: Mon, 30 Jan 2012 16:31:54 +0000	[thread overview]
Message-ID: <20120130163154.GA2248@linaro.org> (raw)
In-Reply-To: <1327678432-15345-1-git-send-email-will.deacon@arm.com>

On Fri, Jan 27, 2012 at 03:33:52PM +0000, Will Deacon wrote:
> __kuser_cmpxchg64 has a return path using bx lr to get back to the caller.
> This is actually ok since the code in question is predicated on
> CONFIG_CPU_32v6K, but for the sake of consistency using the usr_ret
> macro is probably better.
> 
> Cc: Nicolas Pitre <nico@fluxnic.net>
> Cc: Dave Martin <dave.martin@linaro.org>
> Signed-off-by: Will Deacon <will.deacon@arm.com>

This matches the way I originally intended usr_ret to be used.

Acked-by: Dave Martin <dave.martin@linaro.org>

> ---
>  arch/arm/kernel/entry-armv.S |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/arm/kernel/entry-armv.S b/arch/arm/kernel/entry-armv.S
> index 3a456c6..be16a48 100644
> --- a/arch/arm/kernel/entry-armv.S
> +++ b/arch/arm/kernel/entry-armv.S
> @@ -790,7 +790,7 @@ __kuser_cmpxchg64:				@ 0xffff0f60
>  	smp_dmb	arm
>  	rsbs	r0, r3, #0			@ set returned val and C flag
>  	ldmfd	sp!, {r4, r5, r6, r7}
> -	bx	lr
> +	usr_ret	lr
>  
>  #elif !defined(CONFIG_SMP)
>  
> -- 
> 1.7.4.1
> 

      parent reply	other threads:[~2012-01-30 16:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27 15:33 [PATCH] ARM: kuser: consistently use usr_ret for returning from helpers Will Deacon
2012-01-27 18:37 ` Nicolas Pitre
2012-01-30 16:31 ` Dave Martin [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=20120130163154.GA2248@linaro.org \
    --to=dave.martin@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).