Correct minor typos in comments within the virtio_mem driver:
- "bock" -> "block"
- "valued" -> "value"
- "actipn" -> "action"

Signed-off-by: Alok Tiwari <[email protected]>
---
 drivers/virtio/virtio_mem.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/virtio/virtio_mem.c b/drivers/virtio/virtio_mem.c
index 1688ecd69a04..800cc7f9805d 100644
--- a/drivers/virtio/virtio_mem.c
+++ b/drivers/virtio/virtio_mem.c
@@ -164,7 +164,7 @@ struct virtio_mem {
                        unsigned long first_mb_id;
                        /* Id of the last usable memory block of this device. */
                        unsigned long last_usable_mb_id;
-                       /* Id of the next memory bock to prepare when needed. */
+                       /* Id of the next memory block to prepare when needed. 
*/
                        unsigned long next_mb_id;
 
                        /* The subblock size. */
@@ -240,7 +240,7 @@ struct virtio_mem {
        /* An error occurred we cannot handle - stop processing requests. */
        bool broken;
 
-       /* Cached valued of is_kdump_kernel() when the device was probed. */
+       /* Cached value of is_kdump_kernel() when the device was probed. */
        bool in_kdump;
 
        /* The driver is being removed. */
@@ -1080,7 +1080,7 @@ static int virtio_mem_memory_notifier_cb(struct 
notifier_block *nb,
                atomic64_sub(size, &vm->offline_size);
                /*
                 * Start adding more memory once we onlined half of our
-                * threshold. Don't trigger if it's possibly due to our actipn
+                * threshold. Don't trigger if it's possibly due to our action
                 * (e.g., us adding memory which gets onlined immediately from
                 * the core).
                 */
-- 
2.50.1


Reply via email to