From: Palmer Dabbelt <palmer@dabbelt.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] RISC-V Fixes for 5.8-rc3
Date: Fri, 26 Jun 2020 10:40:28 -0700 (PDT) [thread overview]
Message-ID: <mhng-f93a0d3b-0f13-4426-8f7a-77c153f1098b@palmerdabbelt-glaptop1> (raw)
The following changes since commit 48778464bb7d346b47157d21ffde2af6b2d39110:
Linux 5.8-rc2 (2020-06-21 15:45:29 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv-for-linus-5.8-rc3
for you to fetch changes up to e05d57dcb8c71492268ff46ba9bfe9a9cfb1f95d:
riscv: Fixup __vdso_gettimeofday broke dynamic ftrace (2020-06-25 15:38:39 -0700)
----------------------------------------------------------------
RISC-V Fixes for 5.8-rc3
This contains a handful of fixes I'd like to target for rc3. Most of them fix
issues with the conversion of our vDSO to C. There is also one fix to the
SiFive PRCI driver that I picked up as it's causing boot issues on the
hardware.
* A fix to allow kernels with dynamic ftrace to use the vDSO.
* Some build fixes for the C vDSO functions.
* A fix to the PRCI driver's memory allocation, which was the cause of some
boot panics with FREELIST_RANDOM.
----------------------------------------------------------------
Guo Ren (1):
riscv: Fixup __vdso_gettimeofday broke dynamic ftrace
Vincent Chen (3):
riscv: Add -fPIC option to CFLAGS_vgettimeofday.o
clk: sifive: allocate sufficient memory for struct __prci_data
riscv: Add extern declarations for vDSO time-related functions
arch/riscv/kernel/vdso/Makefile | 5 ++++-
arch/riscv/kernel/vdso/vgettimeofday.c | 6 ++++++
drivers/clk/sifive/fu540-prci.c | 5 ++++-
3 files changed, 14 insertions(+), 2 deletions(-)
next reply other threads:[~2020-06-26 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 17:40 Palmer Dabbelt [this message]
2020-06-27 16:00 ` [GIT PULL] RISC-V Fixes for 5.8-rc3 pr-tracker-bot
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=mhng-f93a0d3b-0f13-4426-8f7a-77c153f1098b@palmerdabbelt-glaptop1 \
--to=palmer@dabbelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.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 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).