From: Stafford Horne <shorne@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] Openrisc fixes for 4.11
Date: Sun, 19 Mar 2017 07:47:14 +0900 [thread overview]
Message-ID: <20170318224714.GQ2418@lianli.shorne-pla.net> (raw)
Hi Linus
Please consider for pull,
OpenRISC fixes for build issues that were exposed by kbuild robots after
4.11 merge. All from allmodconfig builds. This includes:
- bug handling 8 byte get_user calls
- module build failure due to multile missing symbol exports
Also, FYI, there is a build warning due to statx syscall missing in
asm-generic/unistd.h. I have patch for that waiting for ok from arm64 guys
who also use asm-generic:
https://lkml.org/lkml/2017/3/13/657
I figure that will go in through another queue, if not, I can pick it up.
The following changes since commit 4495c08e84729385774601b5146d51d9e5849f81:
Linux 4.11-rc2 (2017-03-12 14:47:08 -0700)
are available in the git repository at:
https://github.com/openrisc/linux.git tags/openrisc-for-linus
for you to fetch changes up to 363dad58e4a0f72dce0bf12d361d617239a80317:
openrisc: Export symbols needed by modules (2017-03-16 00:12:57 +0900)
----------------------------------------------------------------
OpenRISC fixes for 4.11
----------------------------------------------------------------
Stafford Horne (3):
openrisc: xchg: fix `computed is not used` warning
openrisc: fix issue handling 8 byte get_user calls
openrisc: Export symbols needed by modules
arch/openrisc/include/asm/cmpxchg.h | 8 ++++++--
arch/openrisc/include/asm/uaccess.h | 2 +-
arch/openrisc/kernel/or32_ksyms.c | 4 ++++
arch/openrisc/kernel/process.c | 1 +
4 files changed, 12 insertions(+), 3 deletions(-)
-Stafford
reply other threads:[~2017-03-18 22:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170318224714.GQ2418@lianli.shorne-pla.net \
--to=shorne@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.