linux-kernel - Re: [PATCH] staging: octeon: type change from uint<bits>

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <aYrVPUj1nma3DUPo@stanley.mountain>
Date: Tue, 10 Feb 2026 09:50:37 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Yoelvis Oliveros <yoelvisoliveros@...il.com>
Cc: gregkh@...uxfoundation.org, linux-staging@...ts.linux.dev,
	linux-kernel@...r.kernel.org, outreachy@...ts.linux.dev
Subject: Re: [PATCH] staging: octeon: type change from uint<bits>_t to u<bits>

On Tue, Feb 10, 2026 at 12:36:31AM -0400, Yoelvis Oliveros wrote:
> Runing the ckeckpatch.pl on the staging/octeon driver they where using
> uint<8/16/32/64>_T as type declaration and the checkpatch.pl was
> putting a [CHECK] flag on those and that they should be change to
> u<8/16/32/64>
> 
> Signed-off-by: Yoelvis Oliveros <yoelvisoliveros@...il.com>
> ---
>  drivers/staging/octeon/octeon-stubs.h | 1922 +++++++++++++------------
>  1 file changed, 972 insertions(+), 950 deletions(-)
> 
> diff --git a/drivers/staging/octeon/octeon-stubs.h b/drivers/staging/octeon/octeon-stubs.h
> index 35b5078ba51e..aea3dad37cfe 100644
> --- a/drivers/staging/octeon/octeon-stubs.h
> +++ b/drivers/staging/octeon/octeon-stubs.h
> @@ -1,188 +1,190 @@
>  /* SPDX-License-Identifier: GPL-2.0 */
> -#define CONFIG_CAVIUM_OCTEON_CVMSEG_SIZE	512
> +#define CONFIG_CAVIUM_OCTEON_CVMSEG_SIZE 512
>  
>  #ifndef XKPHYS_TO_PHYS
> -# define XKPHYS_TO_PHYS(p)			(p)
> +#define XKPHYS_TO_PHYS(p) (p)
>  #endif

This isn't related to the commit message.  I'm not sure that it's
really an improvement, either.  There is honestly a lot in this
patch which is not necessarily more readable afterwards.

regards,
dan carpenter