mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Francesco Valla <francesco@valla.it>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	"Mark Brown" <broonie@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Haixu Cui" <quic_haixcui@quicinc.com>,
	"Jason Wang" <jasowangio@gmail.com>,
	"Viresh Kumar" <viresh.kumar@linaro.org>,
	"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
	"Eugenio Pérez" <eperezma@redhat.com>,
	linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, virtualization@lists.linux.dev
Subject: Re: [PATCH 0/2] Add devicetree bindings for spi-virtio
Date: Wed, 30 Sep 2026 18:01:20 +0200	[thread overview]
Message-ID: <ar0wnqVFn10MISod@bywater> (raw)
In-Reply-To: <20260930-neon-automatic-rooster-e2eec5@quoll>

Hello Krzysztof,

On Wed, Sep 30, 2026 at 01:58:38PM +0200, Krzysztof Kozlowski wrote:
> On Tue, Sep 29, 2026 at 06:41:54PM +0200, Francesco Valla wrote:
> > Add bindings for spi-virtio, like the ones that already exists for
> > gpio-virtio and i2c-virtio. A node using these would not be used to
> > probe the device, which is registered by the virtio transport
> > (e.g.: virtio-mmio) but to declare properties and/or child nodes.
> 
> Keep proper versioning of your work and DO NOT IGNORE previous
> discussions. This was discussed before, no?
> 
> https://lore.kernel.org/all/20260916-remoteproc_virtio_map-v1-7-dac8c5eb4aa9@valla.it/
>

This is correct, the first patch was an accesssory part of a RFC series I
sent some days ago. I decided to drop it from that series as it was
outside its particular scope, as Mathieu noted [1], after picking up a
copy-paste error signalled by sashiko.

I should definitely have mentioned that in the cover letter.

However, I believe this to be independent of that particular series.

> b4 solves the first problem for you.
>
> Best regards,
> Krzysztof
> 

Thank you!


Regards,
Francesco



[1] https://lore.kernel.org/all/CANLsYkzC5DU8j_QJLkuUcV2tYb=G86L_G4yiBZTePKSqiRdd6w@mail.gmail.com/


      reply	other threads:[~2026-09-30 16:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 16:41 Francesco Valla
2026-09-29 16:41 ` [PATCH 1/2] dt-bindings: spi: add " Francesco Valla
2026-09-30 12:03   ` Krzysztof Kozlowski
2026-09-30 16:22     ` Francesco Valla
2026-09-29 16:41 ` [PATCH 2/2] MAINTAINERS: add Francesco as spi-virtio reviewer Francesco Valla
2026-09-30 11:58 ` [PATCH 0/2] Add devicetree bindings for spi-virtio Krzysztof Kozlowski
2026-09-30 16:01   ` Francesco Valla [this message]

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=ar0wnqVFn10MISod@bywater \
    --to=francesco@valla.it \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=eperezma@redhat.com \
    --cc=jasowangio@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=quic_haixcui@quicinc.com \
    --cc=robh@kernel.org \
    --cc=viresh.kumar@linaro.org \
    --cc=virtualization@lists.linux.dev \
    --cc=xuanzhuo@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®