mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandre Ghiti <alex@ghiti.fr>
To: Palmer Dabbelt <palmerdabbelt@google.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [GIT PULL] RISC-V Fixes for 5.6-rc4
Date: Wed, 26 Feb 2020 08:56:54 +0100	[thread overview]
Message-ID: <5226d756-e348-29d1-258d-0ab4b63c0677@ghiti.fr> (raw)
In-Reply-To: <mhng-464e74b9-125c-42e3-9384-60c871d22cfd@palmerdabbelt-glaptop1>

Hi Palmer,

On 2/25/20 6:37 PM, Palmer Dabbelt wrote:
> The following changes since commit 11a48a5a18c63fd7621bb050228cebf13566e4d8:
> 
>    Linux 5.6-rc2 (2020-02-16 13:16:59 -0800)
> 
> are available in the Git repository at:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv-for-linux-5.6-rc4
> 
> for you to fetch changes up to 8458ca147c204e7db124e8baa8fede219006e80d:
> 
>    riscv: adjust the indent (2020-02-24 13:12:53 -0800)
> 
> ----------------------------------------------------------------
> RISC-V Fixes for 5.6-rc4
> 
> This tag contains a handful of RISC-V related fixes that I've collected and
> would like to target for 5.6-rc4:
> 
> * A fix to set up the PMPs on boot, which allows the kernel to access memory on
>    systems that don't set up permissive PMPs before getting to Linux.  This only
>    effects machine-mode kernels, which currently means only NOMMU kernels.
> * A fix to avoid enabling supervisor-mode interrupts when running in
>    machine-mode, also only for NOMMU kernels.
> * A pair of fixes to our KASAN support to avoid corrupting memory.
> * A gitignore fix.
> 
> This boots on QEMU's virt board for me.
> 
> ----------------------------------------------------------------
> Anup Patel (1):
>        RISC-V: Don't enable all interrupts in trap_init()
> 
> Damien Le Moal (1):
>        riscv: Fix gitignore
> 
> Greentime Hu (1):
>        riscv: set pmp configuration if kernel is running in M-mode
> 
> Zong Li (2):
>        riscv: allocate a complete page size for each page table
>        riscv: adjust the indent
> 
>   arch/riscv/boot/.gitignore   |  2 ++
>   arch/riscv/include/asm/csr.h | 12 ++++++++++
>   arch/riscv/kernel/head.S     |  6 +++++
>   arch/riscv/kernel/traps.c    |  4 ++--
>   arch/riscv/mm/kasan_init.c   | 53 ++++++++++++++++++++++++++------------------
>   5 files changed, 53 insertions(+), 24 deletions(-)
> 

What about this patch https://patchwork.kernel.org/patch/11395273/ from 
Vincent that fixes module loading problems described here:

https://lore.kernel.org/linux-riscv/d868acf5-7242-93dc-0051-f97e64dc4387@ghiti.fr/T/

Do you consider it for 5.6 ?

Thanks,

Alex

  parent reply	other threads:[~2020-02-26  7:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25 17:37 Palmer Dabbelt
2020-02-25 18:55 ` pr-tracker-bot
2020-02-26  7:56 ` Alexandre Ghiti [this message]
2020-02-26 19:14   ` When are my patches getting merged [Was: Re: [GIT PULL] RISC-V Fixes for 5.6-rc4] 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=5226d756-e348-29d1-258d-0ab4b63c0677@ghiti.fr \
    --to=alex@ghiti.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmerdabbelt@google.com \
    --cc=paul.walmsley@sifive.com \
    --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

all inboxes | Powered by JetHome®