From: Andreas Schwab <schwab@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k/uaccess: Fix asm constraints for userspace access
Date: Thu, 13 Jun 2013 14:25:20 +0200 [thread overview]
Message-ID: <mvm7ghyrydr.fsf@hawking.suse.de> (raw)
In-Reply-To: <1371124784-13306-1-git-send-email-geert@linux-m68k.org> (Geert Uytterhoeven's message of "Thu, 13 Jun 2013 13:59:44 +0200")
Geert Uytterhoeven <geert@linux-m68k.org> writes:
> Also, relax the asm constraints for 16-bit userspace accesses in
> __put_user() and __get_user(), as both "move" and "moves" do support
> such transfers between memory and address registers.
There's another occurrence in __constant_copy_from_user and
__constant_copy_to_user.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2013-06-13 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 11:59 [PATCH] m68k/uaccess: Fix asm constraints for userspace access Geert Uytterhoeven
2013-06-13 12:25 ` Andreas Schwab [this message]
2013-06-13 13:16 ` Geert Uytterhoeven
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=mvm7ghyrydr.fsf@hawking.suse.de \
--to=schwab@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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