um: virtio: clean up a comment

There's no 'simtime' device, because implementing that through
virtio was just too much complexity. Clean up the comment that
still refers to it.

Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Richard Weinberger <richard@nod.at>

diff --git a/arch/um/drivers/virtio_uml.c b/arch/um/drivers/virtio_uml.c
index 5d957b7e7fd5279a2344254693b9b136931f8401..515d648d3c3d34d7f71c55bc63b6e7d41f15e107 100644 (file)
--- a/arch/um/drivers/virtio_uml.c
+++ b/arch/um/drivers/virtio_uml.c
@@ -914,8 +914,7 @@ static struct virtqueue *vu_setup_vq(struct virtio_device *vdev,
 #ifdef CONFIG_UML_TIME_TRAVEL_SUPPORT
        /*
         * When we get an interrupt, we must bounce it through the simulation
-        * calendar (the simtime device), except for the simtime device itself
-        * since that's part of the simulation control.
+        * calendar (the time-travel=ext:... socket).
         */
        if (time_travel_mode == TT_MODE_EXTERNAL && callback) {
                info->callback = callback;