All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Jisheng Zhang <jszhang@kernel.org>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu,
	linux-kernel@vger.kernel.org, guoren@kernel.org,
	dfustini@baylibre.com
Subject: Re: [PATCH v2] riscv: mm: update T-Head memory type definitions
Date: Mon, 06 Nov 2023 15:00:29 +0000	[thread overview]
Message-ID: <169928282920.16503.8733188249165369994.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230912072510.2510-1-jszhang@kernel.org>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Tue, 12 Sep 2023 15:25:10 +0800 you wrote:
> Update T-Head memory type definitions according to C910 doc [1]
> For NC and IO, SH property isn't configurable, hardcoded as SH,
> so set SH for NOCACHE and IO.
> 
> And also set bit[61](Bufferable) for NOCACHE according to the
> table 6.1 in the doc [1].
> 
> [...]

Here is the summary with links:
  - [v2] riscv: mm: update T-Head memory type definitions
    https://git.kernel.org/riscv/c/dbfbda3bd6bf

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



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

WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Jisheng Zhang <jszhang@kernel.org>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu,
	linux-kernel@vger.kernel.org, guoren@kernel.org,
	dfustini@baylibre.com
Subject: Re: [PATCH v2] riscv: mm: update T-Head memory type definitions
Date: Mon, 06 Nov 2023 15:00:29 +0000	[thread overview]
Message-ID: <169928282920.16503.8733188249165369994.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230912072510.2510-1-jszhang@kernel.org>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Tue, 12 Sep 2023 15:25:10 +0800 you wrote:
> Update T-Head memory type definitions according to C910 doc [1]
> For NC and IO, SH property isn't configurable, hardcoded as SH,
> so set SH for NOCACHE and IO.
> 
> And also set bit[61](Bufferable) for NOCACHE according to the
> table 6.1 in the doc [1].
> 
> [...]

Here is the summary with links:
  - [v2] riscv: mm: update T-Head memory type definitions
    https://git.kernel.org/riscv/c/dbfbda3bd6bf

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2023-11-06 15:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12  7:25 [PATCH v2] riscv: mm: update T-Head memory type definitions Jisheng Zhang
2023-09-12  7:25 ` Jisheng Zhang
2023-10-04 12:07 ` Jisheng Zhang
2023-10-04 12:07   ` Jisheng Zhang
2023-11-05 22:18   ` Palmer Dabbelt
2023-11-05 22:18     ` Palmer Dabbelt
2023-11-06 15:00 ` patchwork-bot+linux-riscv [this message]
2023-11-06 15:00   ` patchwork-bot+linux-riscv

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=169928282920.16503.8733188249165369994.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=dfustini@baylibre.com \
    --cc=guoren@kernel.org \
    --cc=jszhang@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.