From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: linux-sh@vger.kernel.org
Cc: Rich Felker <dalias@libc.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de>,
linux-kernel@vger.kernel.org
Subject: [RESEND] sh: Implement __get_user_u64() required for 64-bit get_user()
Date: Fri, 29 May 2020 17:45:40 +0000 [thread overview]
Message-ID: <20200529174540.4189874-1-glaubitz@physik.fu-berlin.de> (raw)
Hi!
This is my attempt of implementing a 64-bit get_user() for SH to address the
build problem when CONFIG_INFINIBAND_USER_ACCESS is enabled.
I have carefully looked at the existing implementations of __get_user_asm(),
__put_user_asm() and the 64-bit __put_user_u64() to come up with the 64-bit
__get_user_u64().
I'm admittedly not an expert when it comes to writing GCC contraints, so the
code might be completely wrong. However, it builds fine without warnings
and fixes the aforementioned issue for me.
Hopefully someone from the more experienced group of kernel developers can
review my code and help me get it into proper shape for submission.
Resent because I forgot to add a subject for the first cover text.
Thanks,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next reply other threads:[~2020-05-29 17:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 17:45 John Paul Adrian Glaubitz [this message]
2020-05-29 17:45 ` [PATCH] sh: Implement __get_user_u64() required for 64-bit get_user() John Paul Adrian Glaubitz
2020-05-31 9:52 ` Geert Uytterhoeven
2020-05-31 9:54 ` John Paul Adrian Glaubitz
2020-05-31 9:59 ` John Paul Adrian Glaubitz
2020-05-31 10:43 ` Geert Uytterhoeven
2020-05-31 10:52 ` John Paul Adrian Glaubitz
2020-06-01 3:03 ` Rich Felker
2020-06-01 9:02 ` Geert Uytterhoeven
2020-06-01 9:13 ` John Paul Adrian Glaubitz
2020-06-01 16:57 ` Rich Felker
2020-06-01 20:26 ` Michael Karcher
2020-06-01 20:50 ` Rich Felker
2020-06-02 10:19 ` Michael Karcher
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=20200529174540.4189874-1-glaubitz@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=kernel@mkarcher.dialup.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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).