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.9
Date: Fri, 02 Oct 2020 09:07:27 -0700 (PDT) [thread overview]
Message-ID: <mhng-c32d6fbf-32dd-45ed-90f1-ffbb7e455aaa@palmerdabbelt-glaptop1> (raw)
The following changes since commit a1b8638ba1320e6684aa98233c15255eb803fac7:
Linux 5.9-rc7 (2020-09-27 14:38:10 -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.9-rc8
for you to fetch changes up to aa9887608e77b835d51f05a54940380391cd4e21:
RISC-V: Check clint_time_val before use (2020-09-30 11:05:14 -0700)
----------------------------------------------------------------
RISC-V Fixes for 5.9
I have two fixes for this week:
* The addition of a symbol export for clint_time_val, which has been inlined
into some timex functions and can be used by drivers.
* A fix to avoid calling get_cycles() before the timers have been probed.
These both only effect !MMU systems.
----------------------------------------------------------------
Anup Patel (1):
RISC-V: Check clint_time_val before use
Palmer Dabbelt (1):
clocksource: clint: Export clint_time_val for modules
arch/riscv/include/asm/stackprotector.h | 4 ----
arch/riscv/include/asm/timex.h | 13 +++++++++++++
drivers/clocksource/timer-clint.c | 1 +
3 files changed, 14 insertions(+), 4 deletions(-)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2020-10-02 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 16:07 Palmer Dabbelt [this message]
2020-10-02 17:15 ` [GIT PULL] RISC-V Fixes for 5.9 pr-tracker-bot
2020-10-05 7:16 ` Christoph Hellwig
2020-10-05 15:50 ` Palmer Dabbelt
2020-10-09 17:52 Palmer Dabbelt
2020-10-09 19:31 ` 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-c32d6fbf-32dd-45ed-90f1-ffbb7e455aaa@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).