From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Enrico Weigelt, metux IT consult" <info@metux.net>
Cc: linux-kernel@vger.kernel.org, linus.walleij@linaro.org,
bgolaszewski@baylibre.com, jasowang@redhat.com,
linux-gpio@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH] drivers: gpio: add virtio-gpio guest driver
Date: Sun, 29 Nov 2020 15:11:42 -0500 [thread overview]
Message-ID: <20201129151113-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20201127183003.2849-1-info@metux.net>
On Fri, Nov 27, 2020 at 07:30:03PM +0100, Enrico Weigelt, metux IT consult wrote:
> diff --git a/include/uapi/linux/virtio_ids.h b/include/uapi/linux/virtio_ids.h
> index b052355ac7a3..85772c0bcb4b 100644
> --- a/include/uapi/linux/virtio_ids.h
> +++ b/include/uapi/linux/virtio_ids.h
> @@ -48,5 +48,6 @@
> #define VIRTIO_ID_FS 26 /* virtio filesystem */
> #define VIRTIO_ID_PMEM 27 /* virtio pmem */
> #define VIRTIO_ID_MAC80211_HWSIM 29 /* virtio mac80211-hwsim */
> +#define VIRTIO_ID_GPIO 30 /* virtio GPIO */
Pls remember to reserve the ID with the virtio TC
before using it in the driver. Thanks!
> #endif /* _LINUX_VIRTIO_IDS_H */
> --
> 2.11.0
next prev parent reply other threads:[~2020-11-29 20:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 18:30 [PATCH] drivers: gpio: add virtio-gpio guest driver Enrico Weigelt, metux IT consult
2020-11-27 18:45 ` Randy Dunlap
2020-12-03 19:01 ` Enrico Weigelt, metux IT consult
2020-11-27 19:33 ` kernel test robot
2020-11-29 20:11 ` Michael S. Tsirkin [this message]
2020-11-29 22:10 ` Jonathan Neuschäfer
2020-12-03 19:12 ` Enrico Weigelt, metux IT consult
2020-12-02 14:15 ` Bartosz Golaszewski
2020-12-03 19:00 ` Enrico Weigelt, metux IT consult
2020-12-03 22:35 ` Michael Walle
2020-12-04 8:28 ` Enrico Weigelt, metux IT consult
2020-12-04 9:06 ` Michael Walle
-- strict thread matches above, loose matches on Subject: below --
2021-06-15 17:49 Enrico Weigelt, metux IT consult
2021-06-16 8:31 ` Linus Walleij
2021-06-16 11:49 ` Viresh Kumar
2021-06-16 15:04 ` Enrico Weigelt, metux IT consult
2021-06-17 3:59 ` Viresh Kumar
2021-06-17 9:54 ` Enrico Weigelt, metux IT consult
2021-06-17 11:47 ` Viresh Kumar
2021-06-16 14:41 ` Enrico Weigelt, metux IT consult
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=20201129151113-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=bgolaszewski@baylibre.com \
--cc=info@metux.net \
--cc=jasowang@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).