devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH v2 0/2] riscv mmu-type minor fixes
Date: Mon, 16 May 2022 07:29:18 +0000	[thread overview]
Message-ID: <YoH9TE/4ruFQw3fV@x1-carbon> (raw)
In-Reply-To: <20220502125015.1345312-1-niklas.cassel@wdc.com>

On Mon, May 02, 2022 at 02:50:12PM +0200, Niklas Cassel wrote:
> Hello there,
> 
> 
> Here are some minor riscv mmu-type related fixes.
> 
> The first patch simply adds "riscv,sv57" to the list of valid mmu-type
> values.
> 
> The second patch fixes the "mmu:" print in /proc/cpuinfo on nommu systems.
> 
> Please review.
> 
> 
> Kind regards,
> Niklas
> 
> Changes since v1:
> -Picked up tag from Rob Herring on patch 1/1.
> -Send both patches as a series, since they are relate to mmu-type.
> 
> Niklas Cassel (2):
>   dt-bindings: riscv: Add mmu-type riscv,sv57
>   riscv: Don't output a bogus mmu-type on a no MMU kernel
> 
>  Documentation/devicetree/bindings/riscv/cpus.yaml | 1 +
>  arch/riscv/kernel/cpu.c                           | 4 ++++
>  2 files changed, 5 insertions(+)
> 
> -- 
> 2.35.1
> 

Hello Palmer,

A gentle ping.
Any chance of this getting picked up?


Kind regards,
Niklas

      parent reply	other threads:[~2022-05-16  7:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02 12:50 [PATCH v2 0/2] riscv mmu-type minor fixes Niklas Cassel
2022-05-02 12:50 ` [PATCH v2 1/2] dt-bindings: riscv: Add mmu-type riscv,sv57 Niklas Cassel
2022-05-02 12:57   ` Anup Patel
2022-05-16  7:29 ` Niklas Cassel [this message]

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=YoH9TE/4ruFQw3fV@x1-carbon \
    --to=niklas.cassel@wdc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@kernel.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).