Linux virtualization list
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Francesco Valla" <francesco@valla.it>
Cc: virtualization@lists.linux.dev,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: spi: add spi-virtio
Date: Thu, 29 Oct 2026 16:36:37 +0000	[thread overview]
Message-ID: <sashiko-outbox-189664@kernel.org> (raw)
In-Reply-To: <20261029-spi-virtio-bindings-v3-1-ef30217abefd@valla.it>

> Add bindings for spi-virtio based on virtio-device, allowing proper
> validation of SPI controller nodes declared as children of virtio
> transports (e.g.: virtio-mmio). Such nodes are not used to instantiate
> devices, which are registered by the virtio transport, but to define
> their properties and establish dependencies with other nodes.
> 
> The compatible follows what the virtio framework already searches for,
> "2d" being the hexadecimal representation of the SPI controller device
> ID defined by the virtio specification [1].
> 
> [1] https://docs.oasis-open.org/virtio/virtio/v1.4/virtio-v1.4.html
> 
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> Signed-off-by: Francesco Valla <francesco@valla.it>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261029-spi-virtio-bindings-v3-0-ef30217abefd@valla.it?part=1


  reply	other threads:[~2026-10-29 16:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 16:27 [PATCH v3 0/2] Add devicetree bindings and maintainer for spi-virtio Francesco Valla
2026-10-29 16:27 ` [PATCH v3 1/2] dt-bindings: spi: add spi-virtio Francesco Valla
2026-10-29 16:36   ` sashiko-bot [this message]
2026-10-29 16:27 ` [PATCH v3 2/2] MAINTAINERS: replace spi-virtio maintainer Francesco Valla
2026-10-29 19:23   ` Krzysztof Kozlowski
2026-10-30  4:08 ` [PATCH v3 0/2] Add devicetree bindings and maintainer for spi-virtio Viresh Kumar
2026-11-05  0:32 ` Mark Brown

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=sashiko-outbox-189664@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=eperezma@redhat.com \
    --cc=francesco@valla.it \
    --cc=mst@redhat.com \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=virtualization@lists.linux.dev \
    /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