linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@sifive.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-riscv@lists.infradead.org
Subject: [GIT PULL] RISC-V Updates for the 4.21 Merge Window, Part 1
Date: Fri, 21 Dec 2018 08:29:44 -0800 (PST)	[thread overview]
Message-ID: <mhng-5924ada7-ba61-4f8b-a7c8-6ad4a36882ed@palmer-si-x1c4> (raw)

The following changes since commit 7566ec393f4161572ba6f11ad5171fd5d59b0fbd:

  Linux 4.20-rc7 (2018-12-16 15:46:55 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/palmer/riscv-linux.git tags/riscv-for-linus-4.21-mw1

for you to fetch changes up to 9b9afe4a0ef149db2472f13d6fa3c705d2867c9c:

  RISC-V: Select GENERIC_SCHED_CLOCK for clocksource drivers (2018-12-21 08:17:19 -0800)

----------------------------------------------------------------
RISC-V Updates for the 4.21 Merge Window, Part 1

We don't have many patches for this merge window, probably because
everything has been a bit busy with the holidays and conferences.  The
only big user-visible change is to move over to an SBI-based earlycon
instead of our arch-specific early printk support.

The only outstanding patch set I know of is the audit patch set, which
I've managed to make a mess of and will attempt to clean up.

----------------------------------------------------------------
Andrea Parri (1):
      riscv, atomic: Add #define's for the atomic_{cmp,}xchg_*() variants

Anup Patel (3):
      RISC-V: defconfig: Enable RISC-V SBI earlycon support
      RISC-V: Remove EARLY_PRINTK support
      RISC-V: Select GENERIC_SCHED_CLOCK for clocksource drivers

Atish Patra (1):
      RISC-V: Fix of_node_* refcount

David Abdurachmanov (1):
      riscv: remove unused variable in ftrace

Nick Kossifidis (1):
      RISC-V: Update Kconfig to better handle CMDLINE

Olof Johansson (1):
      RISC-V: lib: minor asm cleanup

Palmer Dabbelt (1):
      RISC-V: Move from EARLY_PRINTK to SBI earlycon

Yangtao Li (1):
      RISC-V: add of_node_put()

 arch/riscv/Kconfig              | 58 +++++++++++++++++++++++-----------------
 arch/riscv/Kconfig.debug        |  2 --
 arch/riscv/configs/defconfig    |  1 +
 arch/riscv/include/asm/atomic.h |  9 +++++++
 arch/riscv/kernel/cacheinfo.c   | 11 ++++++++
 arch/riscv/kernel/cpu.c         |  1 +
 arch/riscv/kernel/cpufeature.c  |  2 ++
 arch/riscv/kernel/ftrace.c      |  1 -
 arch/riscv/kernel/perf_event.c  |  1 +
 arch/riscv/kernel/setup.c       | 28 -------------------
 arch/riscv/kernel/smpboot.c     |  6 ++++-
 arch/riscv/kernel/time.c        |  1 +
 arch/riscv/lib/tishift.S        | 59 ++++++++++++++++++++++-------------------
 arch/riscv/lib/udivdi3.S        | 42 +++++++++++++++--------------
 14 files changed, 118 insertions(+), 104 deletions(-)

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2018-12-21 16:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-21 16:29 Palmer Dabbelt [this message]
2019-01-08  1:34 ` [GIT PULL] RISC-V Updates for the 4.21 Merge Window, Part 1 Anup Patel
2019-01-09 18:26   ` Palmer Dabbelt

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-5924ada7-ba61-4f8b-a7c8-6ad4a36882ed@palmer-si-x1c4 \
    --to=palmer@sifive.com \
    --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).