From: Haixu Cui <quic_haixcui@quicinc.com>
To: <virtio-dev@lists.oasis-open.org>,
<virtio-comment@lists.oasis-open.org>, <cohuck@redhat.com>,
<harald.mommer@opensynergy.com>, <broonie@kernel.org>,
<viresh.kumar@linaro.org>
Cc: <quic_ztu@quicinc.com>, Haixu Cui <quic_haixcui@quicinc.com>
Subject: [virtio-dev][PATCH V10 1/2] content: Rename SPI master to SPI controller
Date: Fri, 29 Dec 2023 16:08:54 +0800 [thread overview]
Message-ID: <20231229080855.16519-2-quic_haixcui@quicinc.com> (raw)
In-Reply-To: <20231229080855.16519-1-quic_haixcui@quicinc.com>
SPI master is an outdated term and should use SPI controller.
Signed-off-by: Haixu Cui <quic_haixcui@quicinc.com>
Reviewed-by: Viresh Kumar <viresh.kumar@linaro.org>
---
content.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content.tex b/content.tex
index 0a62dce..1c608eb 100644
--- a/content.tex
+++ b/content.tex
@@ -737,7 +737,7 @@ \chapter{Device Types}\label{sec:Device Types}
\hline
44 & ISM device \\
\hline
-45 & SPI master \\
+45 & SPI controller \\
\hline
\end{tabular}
--
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
next prev parent reply other threads:[~2023-12-29 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 8:08 [virtio-dev][PATCH V10 0/2] virtio-spi: add virtual SPI controller Haixu Cui
2023-12-29 8:08 ` Haixu Cui [this message]
2023-12-29 8:08 ` [virtio-dev][PATCH V10 2/2] virtio-spi: add the device specification Haixu Cui
-- strict thread matches above, loose matches on Subject: below --
2024-01-02 7:36 [virtio-dev][PATCH V10 0/2] virtio-spi: add virtual SPI controller Haixu Cui
2024-01-02 7:36 ` [virtio-dev][PATCH V10 1/2] content: Rename SPI master to " 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=20231229080855.16519-2-quic_haixcui@quicinc.com \
--to=quic_haixcui@quicinc.com \
--cc=broonie@kernel.org \
--cc=cohuck@redhat.com \
--cc=harald.mommer@opensynergy.com \
--cc=quic_ztu@quicinc.com \
--cc=viresh.kumar@linaro.org \
--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).