All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, apatel@ventanamicro.com,
	palmer@dabbelt.com, devicetree@vger.kernel.org,
	ajones@ventanamicro.com, robh@kernel.org,
	conor.dooley@microchip.com
Subject: Re: [PATCH] dt-bindings: riscv: Document cbop-block-size
Date: Thu, 11 Jan 2024 15:40:27 +0000	[thread overview]
Message-ID: <170498762718.16494.12898852163164457210.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231029123500.739409-1-dbarboza@ventanamicro.com>

Hello:

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

On Sun, 29 Oct 2023 09:35:00 -0300 you wrote:
> Following the examples of cbom-block-size and cboz-block-size,
> cbop-block-size is the cache size of Zicbop (cbo.prefetch) operations.
> The most common case is to have all cache block sizes to be the same
> size (e.g. profiles such as rva22u64 mandates a 64 bytes size for all
> cache operations), but there's no specification requirement for that,
> and an implementation can have different cache sizes for each operation.
> 
> [...]

Here is the summary with links:
  - dt-bindings: riscv: Document cbop-block-size
    https://git.kernel.org/riscv/c/d3e591a38c98

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: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, apatel@ventanamicro.com,
	palmer@dabbelt.com, devicetree@vger.kernel.org,
	ajones@ventanamicro.com, robh@kernel.org,
	conor.dooley@microchip.com
Subject: Re: [PATCH] dt-bindings: riscv: Document cbop-block-size
Date: Thu, 11 Jan 2024 15:40:27 +0000	[thread overview]
Message-ID: <170498762718.16494.12898852163164457210.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231029123500.739409-1-dbarboza@ventanamicro.com>

Hello:

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

On Sun, 29 Oct 2023 09:35:00 -0300 you wrote:
> Following the examples of cbom-block-size and cboz-block-size,
> cbop-block-size is the cache size of Zicbop (cbo.prefetch) operations.
> The most common case is to have all cache block sizes to be the same
> size (e.g. profiles such as rva22u64 mandates a 64 bytes size for all
> cache operations), but there's no specification requirement for that,
> and an implementation can have different cache sizes for each operation.
> 
> [...]

Here is the summary with links:
  - dt-bindings: riscv: Document cbop-block-size
    https://git.kernel.org/riscv/c/d3e591a38c98

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



  parent reply	other threads:[~2024-01-11 15:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-29 12:35 [PATCH] dt-bindings: riscv: Document cbop-block-size Daniel Henrique Barboza
2023-10-29 12:35 ` Daniel Henrique Barboza
2023-10-29 14:53 ` Conor Dooley
2023-10-29 14:53   ` Conor Dooley
2023-10-29 19:49   ` Daniel Henrique Barboza
2023-10-29 19:49     ` Daniel Henrique Barboza
2023-10-29 22:21     ` Conor Dooley
2023-10-29 22:21       ` Conor Dooley
2023-10-30  8:18       ` Andrew Jones
2023-10-30  8:18         ` Andrew Jones
2023-10-30  9:14         ` Daniel Henrique Barboza
2023-10-30  9:14           ` Daniel Henrique Barboza
2023-10-30 10:56           ` Conor Dooley
2023-10-30 10:56             ` Conor Dooley
2023-10-30  8:02 ` Krzysztof Kozlowski
2023-10-30  8:03   ` Krzysztof Kozlowski
2024-01-03 11:56 ` Andrew Jones
2024-01-03 11:56   ` Andrew Jones
2024-01-11 15:40 ` patchwork-bot+linux-riscv [this message]
2024-01-11 15:40   ` 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=170498762718.16494.12898852163164457210.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=apatel@ventanamicro.com \
    --cc=conor.dooley@microchip.com \
    --cc=dbarboza@ventanamicro.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=robh@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 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.