From: Zong Li <zongbox@gmail.com>
To: palmer@sifive.com, aou@eecs.berkeley.edu,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
zong@andestech.com
Cc: Zong Li <zongbox@gmail.com>
Subject: [PATCH 0/2] Fix some issue on RV32
Date: Mon, 12 Nov 2018 12:07:42 +0800 [thread overview]
Message-ID: <cover.1541995312.git.zongbox@gmail.com> (raw)
This patches fix the build fail and kernel module install failed on RV32.
Zong Li (2):
RISC-V: Request stat64 on RV32
RISC-V: Support MODULE_SECTIONS mechanism on RV32
arch/riscv/Kconfig | 2 +-
arch/riscv/include/asm/module.h | 28 +++++++++++++++-------------
arch/riscv/include/asm/unistd.h | 1 +
arch/riscv/kernel/module-sections.c | 30 ++++++++++++++++--------------
4 files changed, 33 insertions(+), 28 deletions(-)
--
2.7.4
next reply other threads:[~2018-11-12 4:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 4:07 Zong Li [this message]
2018-11-12 4:07 ` [PATCH 1/2] RISC-V: Request stat64 on RV32 Zong Li
2018-11-12 6:19 ` David Abdurachmanov
2018-11-12 8:29 ` Zong Li
2018-11-12 17:01 ` Palmer Dabbelt
2018-11-12 4:07 ` [PATCH 2/2] RISC-V: Support MODULE_SECTIONS mechanism " Zong Li
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=cover.1541995312.git.zongbox@gmail.com \
--to=zongbox@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=zong@andestech.com \
/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