From: Cornelia Huck <cohuck@redhat.com>
To: Harald Mommer <Harald.Mommer@opensynergy.com>,
virtio-dev@lists.oasis-open.org,
Haixu Cui <quic_haixcui@quicinc.com>,
Mark Brown <broonie@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: quic_ztu@quicinc.com, Matti Moell <Matti.Moell@opensynergy.com>,
Mikhail Golubev <Mikhail.Golubev@opensynergy.com>
Subject: Re: [virtio-dev] [RFC PATCH v3 0/3] Virtio SPI Linux driver compliant to draft spec V10
Date: Wed, 14 Feb 2024 17:22:28 +0100 [thread overview]
Message-ID: <87v86rf22j.fsf@redhat.com> (raw)
In-Reply-To: <20240213135350.5878-1-Harald.Mommer@opensynergy.com>
On Tue, Feb 13 2024, Harald Mommer <Harald.Mommer@opensynergy.com> wrote:
> This is the 3rd RFC version of a virtio SPI Linux driver which is
> intended to be compliant with the proposed virtio SPI draft
> specification V10.
FWIW: this version of the SPI spec has been voted in for virtio 1.4 (and
is consequently available on the virtio-1.4 branch of the virtio spec.)
For all intents and purposes, this makes this spec final (modulo
possible future extensions).
WARNING: multiple messages have this Message-ID (diff)
From: Cornelia Huck <cohuck@redhat.com>
To: Harald Mommer <Harald.Mommer@opensynergy.com>,
virtio-dev@lists.oasis-open.org,
Haixu Cui <quic_haixcui@quicinc.com>,
Mark Brown <broonie@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: quic_ztu@quicinc.com, Matti Moell <Matti.Moell@opensynergy.com>,
Mikhail Golubev <Mikhail.Golubev@opensynergy.com>
Subject: Re: [virtio-dev] [RFC PATCH v3 0/3] Virtio SPI Linux driver compliant to draft spec V10
Date: Wed, 14 Feb 2024 17:22:28 +0100 [thread overview]
Message-ID: <87v86rf22j.fsf@redhat.com> (raw)
In-Reply-To: <20240213135350.5878-1-Harald.Mommer@opensynergy.com>
On Tue, Feb 13 2024, Harald Mommer <Harald.Mommer@opensynergy.com> wrote:
> This is the 3rd RFC version of a virtio SPI Linux driver which is
> intended to be compliant with the proposed virtio SPI draft
> specification V10.
FWIW: this version of the SPI spec has been voted in for virtio 1.4 (and
is consequently available on the virtio-1.4 branch of the virtio spec.)
For all intents and purposes, this makes this spec final (modulo
possible future extensions).
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2024-02-14 16:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 13:53 [RFC PATCH v3 0/3] Virtio SPI Linux driver compliant to draft spec V10 Harald Mommer
2024-02-13 13:53 ` [virtio-dev] " Harald Mommer
2024-02-13 13:53 ` [RFC PATCH v3 1/3] virtio: Add ID for virtio SPI Harald Mommer
2024-02-13 13:53 ` [virtio-dev] " Harald Mommer
2024-02-13 13:53 ` [RFC PATCH v3 2/3] virtio-spi: Add virtio-spi.h Harald Mommer
2024-02-13 13:53 ` [virtio-dev] " Harald Mommer
2024-02-13 13:53 ` [RFC PATCH v3 3/3] SPI: Add virtio SPI driver Harald Mommer
2024-02-13 13:53 ` [virtio-dev] " Harald Mommer
2024-02-13 17:49 ` Mark Brown
2024-02-27 14:12 ` Harald Mommer
2024-02-27 14:12 ` [virtio-dev] " Harald Mommer
2024-02-27 14:25 ` Mark Brown
2024-02-17 19:35 ` kernel test robot
2024-02-20 8:30 ` Haixu Cui
2024-02-20 8:30 ` [virtio-dev] " Haixu Cui
2024-02-26 10:41 ` Harald Mommer
2024-02-26 10:41 ` [virtio-dev] " Harald Mommer
2024-03-04 7:11 ` Haixu Cui
2024-03-04 7:11 ` [virtio-dev] " Haixu Cui
2024-03-04 10:52 ` Harald Mommer
2024-03-04 10:52 ` Harald Mommer
2024-03-05 7:46 ` Haixu Cui
2024-03-05 10:57 ` Harald Mommer
2024-03-05 17:54 ` [virtio-dev] Re: [RFC PATCH v3 3/3] SPI: Add virtio SPI driver. - Correction Harald Mommer
2024-03-06 7:48 ` Haixu Cui
2024-03-06 16:18 ` Harald Mommer
2024-03-11 9:28 ` Haixu Cui
2024-03-13 7:05 ` Haixu Cui
2024-02-14 16:22 ` Cornelia Huck [this message]
2024-02-14 16:22 ` [virtio-dev] [RFC PATCH v3 0/3] Virtio SPI Linux driver compliant to draft spec V10 Cornelia Huck
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=87v86rf22j.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=Harald.Mommer@opensynergy.com \
--cc=Matti.Moell@opensynergy.com \
--cc=Mikhail.Golubev@opensynergy.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=quic_haixcui@quicinc.com \
--cc=quic_ztu@quicinc.com \
--cc=viresh.kumar@linaro.org \
--cc=virtio-dev@lists.oasis-open.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.