From: Hans de Goede <hdegoede@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Hans de Goede <hdegoede@redhat.com>, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/8] virt: vbox: Add support for the new VBG_IOCTL_ACQUIRE_GUEST_CAPABILITIES ioctl
Date: Tue, 23 Jun 2020 16:23:53 +0200 [thread overview]
Message-ID: <20200623142401.3742-1-hdegoede@redhat.com> (raw)
Hi All,
Here is v2 of my vboxguest driver patch-set adding support for the
new VBG_IOCTL_ACQUIRE_GUEST_CAPABILITIES ioctl which is necessary to
make guest resizing work with the new(ish) VMSVGA emulation in vbox +
some other small fixes.
The only change since v2 is rate-limiting the error-logging in:
[PATCH v2 7/8] virt: vbox: Log unknown ioctl requests as error
Regards,
Hans
next reply other threads:[~2020-06-23 14:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 14:23 Hans de Goede [this message]
2020-06-23 14:23 ` [PATCH v2 1/8] virt: vbox: Fix VBGL_IOCTL_VMMDEV_REQUEST_BIG and _LOG req numbers to match upstream Hans de Goede
2020-06-23 14:23 ` [PATCH v2 2/8] virt: vbox: Fix guest capabilities mask check Hans de Goede
2020-06-23 14:23 ` [PATCH v2 3/8] virt: vbox: Rename guest_caps struct members to set_guest_caps Hans de Goede
2020-06-23 14:23 ` [PATCH v2 4/8] virt: vbox: Add vbg_set_host_capabilities() helper function Hans de Goede
2020-06-23 14:23 ` [PATCH v2 5/8] virt: vbox: Add support for the new VBG_IOCTL_ACQUIRE_GUEST_CAPABILITIES ioctl Hans de Goede
2020-06-23 14:23 ` [PATCH v2 6/8] virt: vbox: Add a few new vmmdev request types to the userspace whitelist Hans de Goede
2020-06-23 14:24 ` [PATCH v2 7/8] virt: vbox: Log unknown ioctl requests as error Hans de Goede
2020-06-23 14:24 ` [PATCH v2 8/8] virt: vbox: Fix some comments which talk about the "session spinlock" Hans de Goede
2020-07-07 15:37 ` [PATCH v2 0/8] virt: vbox: Add support for the new VBG_IOCTL_ACQUIRE_GUEST_CAPABILITIES ioctl Hans de Goede
2020-07-07 20:22 ` Arnd Bergmann
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=20200623142401.3742-1-hdegoede@redhat.com \
--to=hdegoede@redhat.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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).