From: Alok Tiwari <[email protected]> Sent: Saturday, September 13, 2025 
12:25 PM
> To: [email protected]; [email protected]; [email protected];
> [email protected]; [email protected]
> Cc: [email protected]; [email protected]
> Subject: [PATCH 3/3] drivers: hv: vmbus: Fix typos in vmbus_drv.c
> 
> Fix two minor typos in vmbus_drv.c:
> - Correct "reponsible" -> "responsible" in a comment.
> - Add missing newline in pr_err() message ("channeln" -> "channel\n").
> 
> These are cosmetic changes only and do not affect functionality.
> 
> Signed-off-by: Alok Tiwari <[email protected]>
> ---
>  drivers/hv/vmbus_drv.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
> index fbab9f2d7fa6..69591dc7bad2 100644
> --- a/drivers/hv/vmbus_drv.c
> +++ b/drivers/hv/vmbus_drv.c
> @@ -1947,7 +1947,7 @@ static const struct kobj_type vmbus_chan_ktype = {
>   * is running.
>   * For example, HV_NIC device is used either by uio_hv_generic or hv_netvsc 
> at any given point of
>   * time, and "ring" sysfs is needed only when uio_hv_generic is bound to 
> that device. To avoid
> - * exposing the ring buffer by default, this function is reponsible to 
> enable visibility of
> + * exposing the ring buffer by default, this function is responsible to 
> enable visibility of
>   * ring for userspace to use.
>   * Note: Race conditions can happen with userspace and it is not encouraged 
> to create new
>   * use-cases for this. This was added to maintain backward compatibility, 
> while solving
> @@ -2110,7 +2110,7 @@ int vmbus_device_register(struct hv_device 
> *child_device_obj)
>       ret = vmbus_add_channel_kobj(child_device_obj,
>                                    child_device_obj->channel);
>       if (ret) {
> -             pr_err("Unable to register primary channeln");
> +             pr_err("Unable to register primary channel\n");
>               goto err_kset_unregister;
>       }
>       hv_debug_add_dev_dir(child_device_obj);
> --
> 2.50.1
>

Reviewed-by: Michael Kelley <[email protected]>
 


Reply via email to