From: Johannes Berg <johannes.berg@intel.com>
Date: Tue, 15 Dec 2020 09:52:21 +0000 (+0100)
Subject: um: virtio: clean up a comment
X-Git-Tag: accepted/tizen/unified/20230118.172025~7838^2~16
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=74e919d2307d9014400c818b82e752c623a4da94;p=platform%2Fkernel%2Flinux-rpi.git

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 5d957b7..515d648 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;