Message-ID: <mhng-16c7b067-954f-4321-88ce-828aa26bd270@palmer-si-x1c4>
Date:   Wed, 13 Dec 2017 12:38:36 -0800 (PST)
From:   Palmer Dabbelt <palmer@...ive.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
CC:     linux-kernel@...r.kernel.org, patches@...ups.riscv.org
Subject: [GIT PULL] RISC-V Fixes for 4.15-rc4

The following changes since commit 50c4c4e268a2d7a3e58ebb698ac74da0de40ae36:

  Linux 4.15-rc3 (2017-12-10 17:56:26 -0800)

are available in the git repository at:

  ssh://git@...olite.kernel.org/pub/scm/linux/kernel/git/palmer/linux.git tags/riscv-for-linus-4.15-rc4-riscv_fixes

for you to fetch changes up to 27b0174525325bf18919597016483a709f3372f8:

  RISC-V: Remove unused CONFIG_HVC_RISCV_SBI code (2017-12-11 07:51:09 -0800)

----------------------------------------------------------------
RISC-V Fixes for 4.15-rc4

This pull request contains three small fixes that I'm hoping to get into
4.15-rc4:

* A fix to a typo in sys_riscv_flush_icache.  This only effects error
  handling, but I think it's a small and obvious enough change that it's
  sane outside the merge window.
* The addition of smp_mb__after_spinlock(), which was recently removed
  due to an incorrect comment.  This is largly a comment change (as
  there's a big one now), and while it's necessary for complience with
  the RISC-V memory model the lack of this fence shouldn't manifest as a
  bug on current implementations.  Nonetheless, it still seems saner to
  have the fence in 4.15.
* The removal of some of the HVC_RISCV_SBI driver that snuck into the
  arch port.  This is compile-time dead code in 4.15 (as the driver
  isn't in yet), and during the review process we found a better way to
  implement early printk on RISC-V.  While this change doesn't do
  anything, it will make staging our HVC driver easier: without this
  change the HVC driver we hope to upstream won't build on 4.15 (because
  the 4.15 arch code would reference a function that no longer exists).

Additionally, I'm instituting a bit of a process change so I don't
submit things too quickly again:

* All the patches I submit during an RC will be from the week before, so
  everyone has gotten a chance to see them and they've made it through
  our autobuilders and integration trees.
* I'll cherry-pick (single patches) or merge (if it's a patch set) on
  top of the new RC on Monday morning.
* I'll sign the tag on Monday morning, to let the autobuilders pick up
  exactly what I'm submitting.
* Assuming nothing goes wrong, I'll mail the pull request out on
  Wednesday.  If something goes wrong, I'll wait at least a day after
  re-spinning the tag to let the autobuilders pick things up.

Hopefully this will avoid any headaches in the future, barring any
emergency fixes.

I don't think this is the last patch set we'll want for 4.15: I think
I'll want to remove some of the first-level irqchip driver that snuck in
as well, which will look a lot like the HVC patch here.  This is pending
some asm-generic cleanup I'm doing that I haven't quite gotten clean
enough to send out yet, though, but hopefully it'll be ready by next
week (and still OK for that late).

----------------------------------------------------------------
Dan Carpenter (1):
      RISC-V: Logical vs Bitwise typo

Palmer Dabbelt (2):
      RISC-V: Resurrect smp_mb__after_spinlock()
      RISC-V: Remove unused CONFIG_HVC_RISCV_SBI code

 arch/riscv/include/asm/barrier.h | 19 +++++++++++++++++++
 arch/riscv/kernel/setup.c        | 11 -----------
 arch/riscv/kernel/sys_riscv.c    |  2 +-
 3 files changed, 20 insertions(+), 12 deletions(-)

Powered by blists - more mailing lists