public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH] dt-bindings: riscv: Add mmu-type riscv,sv57
Date: Thu, 14 Apr 2022 15:39:05 +0000	[thread overview]
Message-ID: <YlhAFzwARnesLuTS@x1-carbon> (raw)
In-Reply-To: <20220414151639.1359969-1-niklas.cassel@wdc.com>

On Thu, Apr 14, 2022 at 05:16:38PM +0200, Niklas Cassel wrote:
> sv57 is defined in the RISC-V Privileged Specification document.
> 
> Additionally, commit 011f09d12052 ("riscv: mm: Set sv57 on defaultly")
> changed the default MMU mode to sv57, if supported by current hardware.
> 
> Add riscv,sv57 to the list of valid mmu-type values.
> 
> Signed-off-by: Niklas Cassel <niklas.cassel@wdc.com>
> ---
>  Documentation/devicetree/bindings/riscv/cpus.yaml | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/riscv/cpus.yaml b/Documentation/devicetree/bindings/riscv/cpus.yaml
> index d632ac76532e..3100fa233ca4 100644
> --- a/Documentation/devicetree/bindings/riscv/cpus.yaml
> +++ b/Documentation/devicetree/bindings/riscv/cpus.yaml
> @@ -61,6 +61,7 @@ properties:
>        - riscv,sv32
>        - riscv,sv39
>        - riscv,sv48
> +      - riscv,sv57
>        - riscv,none
>  
>    riscv,isa:
> -- 
> 2.35.1
> 

Hello Palmer,

I got a bounce on your old email address.

My git-send-email scripts, for getting the list of CC, uses:
./scripts/get_maintainer.pl --nom --norolestats --nogit --nogit-fallback <patch>


You might want to either:

a) Update your email in the DT bindings:

$ git grep palmer@sifive
Documentation/devicetree/bindings/dma/sifive,fu540-c000-pdma.yaml:  - Palmer Debbelt <palmer@sifive.com>
Documentation/devicetree/bindings/riscv/cpus.yaml:  - Palmer Dabbelt <palmer@sifive.com>
Documentation/devicetree/bindings/riscv/sifive.yaml:  - Palmer Dabbelt <palmer@sifive.com>
Documentation/devicetree/bindings/serial/sifive-serial.yaml:  - Palmer Dabbelt <palmer@sifive.com>
Documentation/devicetree/bindings/spi/spi-sifive.yaml:  - Palmer Dabbelt <palmer@sifive.com>

or

b) Tell get_maintainer.pl to redirect your old address to your new address
by adding an entry in the .mailmap file:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/.mailmap


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

  reply	other threads:[~2022-04-14 15:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 15:16 [PATCH] dt-bindings: riscv: Add mmu-type riscv,sv57 Niklas Cassel
2022-04-14 15:39 ` Niklas Cassel [this message]
2022-04-19 18:15 ` Rob Herring

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=YlhAFzwARnesLuTS@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