lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Thu, 8 Sep 2022 16:40:32 +0700
From:   Ammar Faizi <ammarfaizi2@...weeb.org>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Sasha Levin <sashal@...nel.org>
Cc:     stable@...r.kernel.org, Colin Ian King <colin.i.king@...il.com>,
        Zhi Wang <zhi.a.wang@...el.com>,
        Zhenyu Wang <zhenyuw@...ux.intel.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5.19 086/155] drm/i915/reg: Fix spelling mistake
 "Unsupport" -> "Unsupported"

On 9/6/22 8:30 PM, Greg Kroah-Hartman wrote:
> From: Colin Ian King <colin.i.king@...il.com>
> 
> [ Upstream commit 233f56745be446b289edac2ba8184c09365c005e ]
> 
> There is a spelling mistake in a gvt_vgpu_err error message. Fix it.
> 
> Fixes: 695fbc08d80f ("drm/i915/gvt: replace the gvt_err with gvt_vgpu_err")
> Signed-off-by: Colin Ian King <colin.i.king@...il.com>
> Signed-off-by: Zhi Wang <zhi.a.wang@...el.com>
> Link: http://patchwork.freedesktop.org/patch/msgid/20220315202449.2952845-1-colin.i.king@gmail.com
> Reviewed-by: Zhi Wang <zhi.a.wang@...el.com>
> Signed-off-by: Zhenyu Wang <zhenyuw@...ux.intel.com>
> Signed-off-by: Sasha Levin <sashal@...nel.org>
> ---
>   drivers/gpu/drm/i915/gvt/handlers.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/gvt/handlers.c b/drivers/gpu/drm/i915/gvt/handlers.c
> index beea5895e4992..73e74a6a76037 100644
> --- a/drivers/gpu/drm/i915/gvt/handlers.c
> +++ b/drivers/gpu/drm/i915/gvt/handlers.c
> @@ -905,7 +905,7 @@ static int update_fdi_rx_iir_status(struct intel_vgpu *vgpu,
>   	else if (FDI_RX_IMR_TO_PIPE(offset) != INVALID_INDEX)
>   		index = FDI_RX_IMR_TO_PIPE(offset);
>   	else {
> -		gvt_vgpu_err("Unsupport registers %x\n", offset);
> +		gvt_vgpu_err("Unsupported registers %x\n", offset);
>   		return -EINVAL;
>   	}

I don't think this one is a stable material. How did this get picked up?

-- 
Ammar Faizi

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ