From: "Michael S. Tsirkin" <mst@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Rusty Russell <rusty@rustcorp.com.au>,
virtualization@lists.linux-foundation.org
Subject: [PATCH 0/3] fix up vringh/mic sparse errors
Date: Mon, 15 Dec 2014 23:13:59 +0200 [thread overview]
Message-ID: <1418678019-31629-1-git-send-email-mst@redhat.com> (raw)
This fixes remaining sparse warnings in vringh and mic by using
virtio 1.0 compliant wrappers.
This also needs by get_user patches to avoid getting warnings
from these calls.
Tested by running vringh_test.
Rusty, I prefer fixing all these warnings for 3.19, any objections?
Michael S. Tsirkin (3):
vringh: 64 bit features
vringh: initial virtio 1.0 support
mic/host: initial virtio 1.0 support
include/linux/vringh.h | 37 ++++++++++-
drivers/misc/mic/host/mic_debugfs.c | 18 ++++--
drivers/vhost/vringh.c | 125 ++++++++++++++++++++++--------------
3 files changed, 123 insertions(+), 57 deletions(-)
--
MST
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: virtualization@lists.linux-foundation.org
Subject: [PATCH 0/3] fix up vringh/mic sparse errors
Date: Mon, 15 Dec 2014 23:13:59 +0200 [thread overview]
Message-ID: <1418678019-31629-1-git-send-email-mst@redhat.com> (raw)
This fixes remaining sparse warnings in vringh and mic by using
virtio 1.0 compliant wrappers.
This also needs by get_user patches to avoid getting warnings
from these calls.
Tested by running vringh_test.
Rusty, I prefer fixing all these warnings for 3.19, any objections?
Michael S. Tsirkin (3):
vringh: 64 bit features
vringh: initial virtio 1.0 support
mic/host: initial virtio 1.0 support
include/linux/vringh.h | 37 ++++++++++-
drivers/misc/mic/host/mic_debugfs.c | 18 ++++--
drivers/vhost/vringh.c | 125 ++++++++++++++++++++++--------------
3 files changed, 123 insertions(+), 57 deletions(-)
--
MST
next reply other threads:[~2014-12-15 21:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 21:13 Michael S. Tsirkin [this message]
2014-12-15 21:13 ` [PATCH 0/3] fix up vringh/mic sparse errors Michael S. Tsirkin
2014-12-15 21:14 ` [PATCH 1/3] vringh: 64 bit features Michael S. Tsirkin
2014-12-15 21:14 ` Michael S. Tsirkin
2014-12-15 21:14 ` [PATCH 2/3] vringh: initial virtio 1.0 support Michael S. Tsirkin
2014-12-15 21:14 ` Michael S. Tsirkin
2014-12-15 21:14 ` [PATCH 3/3] mic/host: " Michael S. Tsirkin
2014-12-15 21:14 ` Michael S. Tsirkin
2014-12-19 1:27 ` [PATCH 0/3] fix up vringh/mic sparse errors Rusty Russell
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=1418678019-31629-1-git-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.