From: kmpark@infradead.org (Kyungmin Park)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Declare __copy_to_user_std as a function using ENDPROC
Date: Fri, 7 May 2010 10:48:25 +0900 [thread overview]
Message-ID: <s2h9c9fda241005061848l24e80fd5q1ddc71ad7006166d@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1005061334190.14468@xanadu.home>
Tested-by: Kyungmin Park <kyungmin.park@samsung.com>
On Fri, May 7, 2010 at 2:35 AM, Nicolas Pitre <nico@fluxnic.net> wrote:
> On Thu, 6 May 2010, Catalin Marinas wrote:
>
>> This is needed for Thumb-2 kernel builds, otherwise the compiler
>> generates branches into ARM mode to this function.
>>
>> Reported-by: Kyungmin Park <kmpark@infradead.org>
>> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
>
> You need to do the same with __clear_user_std as well. ?With that change
> added:
>
> Acked-by: Nicolas Pitre <nico@fluxnic.net>
>
>
>
>
>> ---
>> ?arch/arm/lib/copy_to_user.S | ? ?1 +
>> ?1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/arm/lib/copy_to_user.S b/arch/arm/lib/copy_to_user.S
>> index 1a71e15..5941fbc 100644
>> --- a/arch/arm/lib/copy_to_user.S
>> +++ b/arch/arm/lib/copy_to_user.S
>> @@ -93,6 +93,7 @@ WEAK(__copy_to_user)
>> ?#include "copy_template.S"
>>
>> ?ENDPROC(__copy_to_user)
>> +ENDPROC(__copy_to_user_std)
>>
>> ? ? ? .section .fixup,"ax"
>> ? ? ? .align 0
>>
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>>
>
prev parent reply other threads:[~2010-05-07 1:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 14:12 [PATCH] ARM: Declare __copy_to_user_std as a function using ENDPROC Catalin Marinas
2010-05-06 17:35 ` Nicolas Pitre
2010-05-07 1:48 ` Kyungmin Park [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=s2h9c9fda241005061848l24e80fd5q1ddc71ad7006166d@mail.gmail.com \
--to=kmpark@infradead.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).