From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Enrico Weigelt, metux IT consult" <info@metux.net>
Cc: linux-kernel@vger.kernel.org, jasowang@redhat.com,
keescook@chromium.org, anton@enomsg.org, ccross@android.com,
tony.luck@intel.com, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 2/2] uapi: virtio_ids: add missing device type IDs from OASIS spec
Date: Wed, 2 Dec 2020 06:21:29 -0500 [thread overview]
Message-ID: <20201202062046-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20201202111931.31953-2-info@metux.net>
On Wed, Dec 02, 2020 at 12:19:31PM +0100, Enrico Weigelt, metux IT consult wrote:
> The OASIS virtio spec (1.1) defines several IDs that aren't reflected
> in the header yet. Fixing this by adding the missing IDs, even though
> they're not yet used by the kernel yet.
double yet ;)
>
> Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
> ---
> include/uapi/linux/virtio_ids.h | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/include/uapi/linux/virtio_ids.h b/include/uapi/linux/virtio_ids.h
> index 3cb55e5277a1..bc1c0621f5ed 100644
> --- a/include/uapi/linux/virtio_ids.h
> +++ b/include/uapi/linux/virtio_ids.h
> @@ -34,15 +34,21 @@
> #define VIRTIO_ID_CONSOLE 3 /* virtio console */
> #define VIRTIO_ID_RNG 4 /* virtio rng */
> #define VIRTIO_ID_BALLOON 5 /* virtio balloon */
> +#define VIRTIO_ID_IOMEM 6 /* virtio ioMemory */
> #define VIRTIO_ID_RPMSG 7 /* virtio remote processor messaging */
> #define VIRTIO_ID_SCSI 8 /* virtio scsi */
> #define VIRTIO_ID_9P 9 /* 9p virtio console */
> +#define VIRTIO_ID_MAC80211_WLAN 10 /* virtio WLAN MAC */
> #define VIRTIO_ID_RPROC_SERIAL 11 /* virtio remoteproc serial link */
> #define VIRTIO_ID_CAIF 12 /* Virtio caif */
> +#define VIRTIO_ID_MEMORY_BALLOON 13 /* virtio memory balloon */
> #define VIRTIO_ID_GPU 16 /* virtio GPU */
> +#define VIRTIO_ID_CLOCK 17 /* virtio clock/timer */
> #define VIRTIO_ID_INPUT 18 /* virtio input */
> #define VIRTIO_ID_VSOCK 19 /* virtio vsock transport */
> #define VIRTIO_ID_CRYPTO 20 /* virtio crypto */
> +#define VIRTIO_ID_SIGNAL_DIST 21 /* virtio signal distribution device */
> +#define VIRTIO_ID_PSTORE 22 /* virtio pstore device */
> #define VIRTIO_ID_IOMMU 23 /* virtio IOMMU */
> #define VIRTIO_ID_MEM 24 /* virtio mem */
> #define VIRTIO_ID_FS 26 /* virtio filesystem */
> --
> 2.11.0
prev parent reply other threads:[~2020-12-02 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 11:19 [PATCH 1/2] uapi: virtio_ids.h: consistent indentions Enrico Weigelt, metux IT consult
2020-12-02 11:19 ` [PATCH 2/2] uapi: virtio_ids: add missing device type IDs from OASIS spec Enrico Weigelt, metux IT consult
2020-12-02 11:21 ` Michael S. Tsirkin [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=20201202062046-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=info@metux.net \
--cc=jasowang@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=virtualization@lists.linux-foundation.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
Powered by JetHome