diff mbox series

[1/4] um: virtio: clean up a comment

Message ID 20201214130826.5c1b7720a11b.Ibacb1cbbdd1fa7ae866f0c3c94488dcbae01b39b@changeid
State Superseded
Headers show
Series [1/4] um: virtio: clean up a comment | expand

Commit Message

Johannes Berg Dec. 14, 2020, 12:08 p.m. UTC 
From: Johannes Berg <johannes.berg@intel.com>

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>
---
 arch/um/drivers/virtio_uml.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
diff mbox series

Patch

diff --git a/arch/um/drivers/virtio_uml.c b/arch/um/drivers/virtio_uml.c
index 27e92d3881ff..ead9a1aea192 100644
--- 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;