From: Haixu Cui <quic_haixcui@quicinc.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Cornelia Huck <cohuck@redhat.com>
Cc: <virtio-dev@lists.oasis-open.org>, <quic_ztu@quicinc.com>,
<virtio-comment@lists.oasis-open.org>, <jrreinhart@google.com>
Subject: [virtio-comment] Re: [virtio-dev][PATCH 1/2] virtio-spi: define the DEVICE ID for virtio SPI master
Date: Fri, 7 Jul 2023 17:17:59 +0800 [thread overview]
Message-ID: <40e540f0-b07e-63af-d639-bcd71e4b23a1@quicinc.com> (raw)
In-Reply-To: <20230630105606-mutt-send-email-mst@kernel.org>
Hi Michael S. Tsirkin, Cornelia Huck,
I have created an issue
https://github.com/oasis-tcs/virtio-spec/issues/174 to request Device ID
45 for SPI master. Please help to deal with it, thank you very much.
Best Regards
Haixu Cui
On 6/30/2023 10:57 PM, Michael S. Tsirkin wrote:
> On Mon, Apr 17, 2023 at 10:03:52PM +0800, Haixu Cui wrote:
>> Define the DEVICE ID of virtio SPI master device as 45.
>
> It does not looks like patch 2 will make it in time for 1.3
> but should we vote on reserving device id maybe?
> If yes pls create a github issue and request vote on list.
>
>> ---
>> content.tex | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/content.tex b/content.tex
>> index cff548a..29f2859 100644
>> --- a/content.tex
>> +++ b/content.tex
>> @@ -682,6 +682,8 @@ \chapter{Device Types}\label{sec:Device Types}
>> \hline
>> 44 & ISM device \\
>> \hline
>> +45 & SPI master \\
>> +\hline
>> \end{tabular}
>>
>> Some of the devices above are unspecified by this document,
>> --
>> 2.17.1
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
>> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
>
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next parent reply other threads:[~2023-07-07 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230417140353.870-1-quic_haixcui@quicinc.com>
[not found] ` <20230417140353.870-2-quic_haixcui@quicinc.com>
[not found] ` <20230630105606-mutt-send-email-mst@kernel.org>
2023-07-07 9:17 ` Haixu Cui [this message]
2023-07-10 8:47 ` [virtio-comment] Re: [virtio-dev][PATCH 1/2] virtio-spi: define the DEVICE ID for virtio SPI master Cornelia Huck
2023-07-10 9:14 ` Michael S. Tsirkin
[not found] ` <20230417140353.870-3-quic_haixcui@quicinc.com>
[not found] ` <98b247c1-b970-72ba-6888-f83144f08116@opensynergy.com>
2023-07-28 6:53 ` [virtio-comment] Re: [virtio-dev][PATCH 2/2] virtio-spi: add the device specification Haixu Cui
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=40e540f0-b07e-63af-d639-bcd71e4b23a1@quicinc.com \
--to=quic_haixcui@quicinc.com \
--cc=cohuck@redhat.com \
--cc=jrreinhart@google.com \
--cc=mst@redhat.com \
--cc=quic_ztu@quicinc.com \
--cc=virtio-comment@lists.oasis-open.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).