From: Krzysztof Kozlowski <krzk@kernel.org>
To: linux-riscv@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: riscv: Document cbop-block-size
Date: Mon, 30 Oct 2023 09:03:52 +0100 [thread overview]
Message-ID: <b3454ae1-1dfc-4320-8dea-c33c9c92539d@kernel.org> (raw)
In-Reply-To: <560d7e3f-f7de-4081-b2da-0e3ec83196b1@kernel.org>
On 30/10/2023 09:02, Krzysztof Kozlowski wrote:
> On 29/10/2023 13:35, Daniel Henrique Barboza 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.
>>
>> Cc: Rob Herring <robh@kernel.org>
>> Cc: Conor Dooley <conor.dooley@microchip.com>
>> Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
>> ---
>
> Please use scripts/get_maintainers.pl to get a list of necessary people
> and lists to CC. It might happen, that command when run on an older
> kernel, gives you outdated entries. Therefore please be sure you base
> your patches on recent Linux kernel.
>
> You missed at least devicetree list (maybe more), so this won't be
Sorry, wrong filters/macros. Please disregard.
Best regards,
Krzysztof
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-10-30 8:04 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 [this message]
2024-01-03 11:56 ` Andrew Jones
2024-01-03 11:56 ` Andrew Jones
2024-01-11 15:40 ` patchwork-bot+linux-riscv
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=b3454ae1-1dfc-4320-8dea-c33c9c92539d@kernel.org \
--to=krzk@kernel.org \
--cc=linux-riscv@lists.infradead.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.