[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240213214342.GFZcvijhGJ0b1y3wAg@fat_crate.local>
Date: Tue, 13 Feb 2024 22:43:42 +0100
From: Borislav Petkov <bp@...en8.de>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
Sohil Mehta <sohil.mehta@...el.com>
Subject: Re: [PATCH v2] x86/usercopy: fix kernel-doc function param name
On Sat, Feb 10, 2024 at 10:25:01PM -0800, Randy Dunlap wrote:
> Correct the function parameter name in clean_cache_range() to prevent
> kernel-doc warnings:
>
> usercopy_64.c:29: warning: Function parameter or member 'addr' not described in 'clean_cache_range'
> usercopy_64.c:29: warning: Excess function parameter 'vaddr' description in 'clean_cache_range'
>
> Signed-off-by: Randy Dunlap <rdunlap@...radead.org>
> Cc: Thomas Gleixner <tglx@...utronix.de>
> Cc: Ingo Molnar <mingo@...hat.com>
> Cc: Borislav Petkov <bp@...en8.de>
> Cc: Dave Hansen <dave.hansen@...ux.intel.com>
> Cc: x86@...nel.org
> Reviewed-by: Sohil Mehta <sohil.mehta@...el.com>
> ---
> v2: add Rev-by: Sohil Mehta
>
> From: Randy Dunlap <rdunlap@...radead.org>
> Subject: [PATCH v2] x86/usercopy: fix kernel-doc function param name
>
> Correct the function parameter name in clean_cache_range() to prevent
> kernel-doc warnings:
>
> usercopy_64.c:29: warning: Function parameter or member 'addr' not described in 'clean_cache_range'
> usercopy_64.c:29: warning: Excess function parameter 'vaddr' description in 'clean_cache_range'
>
> Signed-off-by: Randy Dunlap <rdunlap@...radead.org>
> Cc: Thomas Gleixner <tglx@...utronix.de>
> Cc: Ingo Molnar <mingo@...hat.com>
> Cc: Borislav Petkov <bp@...en8.de>
> Cc: Dave Hansen <dave.hansen@...ux.intel.com>
> Cc: x86@...nel.org
> Reviewed-by: Sohil Mehta <sohil.mehta@...el.com>
> ---
> v2: add Rev-by: Sohil Mehta
>
> arch/x86/lib/usercopy_64.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff -- a/arch/x86/lib/usercopy_64.c b/arch/x86/lib/usercopy_64.c
> --- a/arch/x86/lib/usercopy_64.c
> +++ b/arch/x86/lib/usercopy_64.c
> @@ -18,7 +18,7 @@
> #ifdef CONFIG_ARCH_HAS_UACCESS_FLUSHCACHE
> /**
> * clean_cache_range - write back a cache range with CLWB
> - * @vaddr: virtual start address
> + * @addr: virtual start address
> * @size: number of bytes to write back
> *
> * Write back a cache range using the CLWB (cache line write back)
> arch/x86/lib/usercopy_64.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff -- a/arch/x86/lib/usercopy_64.c b/arch/x86/lib/usercopy_64.c
> --- a/arch/x86/lib/usercopy_64.c
> +++ b/arch/x86/lib/usercopy_64.c
> @@ -18,7 +18,7 @@
> #ifdef CONFIG_ARCH_HAS_UACCESS_FLUSHCACHE
> /**
> * clean_cache_range - write back a cache range with CLWB
> - * @vaddr: virtual start address
> + * @addr: virtual start address
> * @size: number of bytes to write back
> *
> * Write back a cache range using the CLWB (cache line write back)
What happened here? :)
Commit message and patch diff appear twice.
Once not enough huh?
:-P
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists