linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leyfoon Tan <leyfoon.tan@starfivetech.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Alexandre Ghiti <alexandre.ghiti@canonical.com>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: arch/riscv: SV48 patch series questions
Date: Fri, 27 May 2022 09:37:34 +0000	[thread overview]
Message-ID: <83813d991f96428c95c6d681c16ae852@EXMBX161.cuchost.com> (raw)

Hi Palmer

Alex's "Introduce sv48 support without relocatable kernel" patch series in [1] was partially merged to Linux v5.17. But there are 4 patches are not merged (Patch-10 to 13).

May I know what is the plan for these patches? Will them merged to next v5.19 merging window? Or do you expect any changes for these patches or Alex needs resend with rebase to latest kernel version?

Note, we would like to use the Patch-13 in this series.

Patches not merged:
[v3,10/13] riscv: Improve virtual kernel memory layout dump
[v3,11/13] Documentation: riscv: Add sv48 description to VM layout
[v3,12/13] riscv: Initialize thread pointer before calling C functions
[v3,13/13] riscv: Allow user to downgrade to sv39 when hw supports sv48 if !KASAN

[1]: https://patchwork.kernel.org/project/linux-riscv/cover/20211206104657.433304-1-alexandre.ghiti@canonical.com/

Thanks.

Regards
Ley Foon

             reply	other threads:[~2022-05-27  9:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27  9:37 Leyfoon Tan [this message]
2022-06-02  3:44 ` arch/riscv: SV48 patch series questions Palmer Dabbelt
2022-06-02  5:43   ` Leyfoon Tan
2022-07-01  2:34     ` Leyfoon Tan

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=83813d991f96428c95c6d681c16ae852@EXMBX161.cuchost.com \
    --to=leyfoon.tan@starfivetech.com \
    --cc=alexandre.ghiti@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    /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).