From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: mst@redhat.com
Cc: virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org,
Cornelia Huck <cornelia.huck@de.ibm.com>
Subject: [PATCH 2/2] virtio: virtio_driver doc
Date: Thu, 30 Mar 2017 13:13:33 +0200 [thread overview]
Message-ID: <20170330111333.47725-3-cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <20170330111333.47725-1-cornelia.huck@de.ibm.com>
Add comments for the virtio_driver members that were not documented.
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
---
include/linux/virtio.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/include/linux/virtio.h b/include/linux/virtio.h
index 8f4d4bf..e80adf2 100644
--- a/include/linux/virtio.h
+++ b/include/linux/virtio.h
@@ -133,9 +133,13 @@ int virtio_device_restore(struct virtio_device *dev);
* @feature_table_legacy: same as feature_table but when working in legacy mode.
* @feature_table_size_legacy: number of entries in feature table legacy array.
* @probe: the function to call when a device is found. Returns 0 or -errno.
+ * @scan: optional function to call after successful probe; intended
+ * for virtio-scsi to invoke a scan.
* @remove: the function to call when a device is removed.
* @config_changed: optional function to call when the device configuration
* changes; may be called in interrupt context.
+ * @freeze: optional function to call during suspend/hibernation.
+ * @restore: optional function to call on resume.
*/
struct virtio_driver {
struct device_driver driver;
--
2.8.4
next prev parent reply other threads:[~2017-03-30 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 11:13 [PATCH 0/2] virtio: two small improvements Cornelia Huck
2017-03-30 11:13 ` [PATCH 1/2] MAINTAINERS: fix virtio file pattern Cornelia Huck
2017-03-30 11:13 ` Cornelia Huck [this message]
2017-03-30 15:00 ` [PATCH 0/2] virtio: two small improvements Michael S. Tsirkin
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=20170330111333.47725-3-cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.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
all inboxes | Powered by JetHome®