All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: Andrew Jones <ajones@ventanamicro.com>,
	linux-riscv@lists.infradead.org, apatel@ventanamicro.com,
	palmer@dabbelt.com, devicetree@vger.kernel.org,
	Rob Herring <robh@kernel.org>,
	Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH] dt-bindings: riscv: Document cbop-block-size
Date: Mon, 30 Oct 2023 10:56:17 +0000	[thread overview]
Message-ID: <20231030-attest-unchain-ab99981a5738@spud> (raw)
In-Reply-To: <513ea612-b354-44d4-b6d7-490741ed14a3@ventanamicro.com>


[-- Attachment #1.1: Type: text/plain, Size: 553 bytes --]

On Mon, Oct 30, 2023 at 06:14:45AM -0300, Daniel Henrique Barboza wrote:
> On 10/30/23 05:18, Andrew Jones wrote:

> > I guess after letting this ping-pong back and forth in my brain a few
> > times the ball is currently resting on the "let's add cbop-block-size"
> > side.
> 
> I'll go ahead and understand that it is ok for QEMU to add a riscv,cbop-block-size DT
> then.

Aye. And in case it was not clear, here's an unqualified ack.

Acked-by: Conor Dooley <conor.dooley@microchip.com>

Can you pick this up Palmer?

Cheers,
Conor.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
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: Conor Dooley <conor@kernel.org>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: Andrew Jones <ajones@ventanamicro.com>,
	linux-riscv@lists.infradead.org, apatel@ventanamicro.com,
	palmer@dabbelt.com, devicetree@vger.kernel.org,
	Rob Herring <robh@kernel.org>,
	Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH] dt-bindings: riscv: Document cbop-block-size
Date: Mon, 30 Oct 2023 10:56:17 +0000	[thread overview]
Message-ID: <20231030-attest-unchain-ab99981a5738@spud> (raw)
In-Reply-To: <513ea612-b354-44d4-b6d7-490741ed14a3@ventanamicro.com>

[-- Attachment #1: Type: text/plain, Size: 553 bytes --]

On Mon, Oct 30, 2023 at 06:14:45AM -0300, Daniel Henrique Barboza wrote:
> On 10/30/23 05:18, Andrew Jones wrote:

> > I guess after letting this ping-pong back and forth in my brain a few
> > times the ball is currently resting on the "let's add cbop-block-size"
> > side.
> 
> I'll go ahead and understand that it is ok for QEMU to add a riscv,cbop-block-size DT
> then.

Aye. And in case it was not clear, here's an unqualified ack.

Acked-by: Conor Dooley <conor.dooley@microchip.com>

Can you pick this up Palmer?

Cheers,
Conor.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-10-30 10:56 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 [this message]
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
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=20231030-attest-unchain-ab99981a5738@spud \
    --to=conor@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.