Linux kernel staging patches
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: Osama Abdelkader <osama.abdelkader@gmail.com>
Cc: gregkh@linuxfoundation.org, aleksander.lobakin@intel.com,
	sergio.paracuellos@gmail.com, pabeni@redhat.com,
	abhishektamboli9@gmail.com, linux-kernel@vger.kernel.org,
	linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: octeon: use fixed-width integer types
Date: Mon, 1 Sep 2025 13:51:00 +0300	[thread overview]
Message-ID: <aLV6lF2gutK24RtV@stanley.mountain> (raw)
In-Reply-To: <20250829200107.132443-1-osama.abdelkader@gmail.com>

On Fri, Aug 29, 2025 at 10:01:07PM +0200, Osama Abdelkader wrote:
> The kernel coding style prefers fixed-width integer types defined in
> <linux/types.h> (u8, u16, u32, u64, etc.) over the C99 stdint.h types
> (e.g. uint64_t).
> 
> Replace uint64_t with u64, uint32_t with u32, uint16_t with u16
> uint8_t with u8 in octeon-stubs.h.
> 
> Signed-off-by: Osama Abdelkader <osama.abdelkader@gmail.com>
> ---
>  drivers/staging/octeon/octeon-stubs.h | 1745 +++++++++++++------------
>  1 file changed, 873 insertions(+), 872 deletions(-)
> 
> diff --git a/drivers/staging/octeon/octeon-stubs.h b/drivers/staging/octeon/octeon-stubs.h
> index 44cced319c11..ff6509b28cdd 100644
> --- a/drivers/staging/octeon/octeon-stubs.h
> +++ b/drivers/staging/octeon/octeon-stubs.h
> @@ -43,144 +43,144 @@
>  #define CVMX_POW_WQ_INT_PC		0
>  
>  union cvmx_pip_wqe_word2 {
> -	uint64_t u64;
> +	u64 u64;

This was already done upstream so the patch doesn't apply.

The point of the octeon-stubs.h file is it allows us to compile test
a bunch of code which is specific to Octeon.  The real code lives
in arch/mips/include/asm/octeon/cvmx-wqe.h.  These files have diverged
quite a bit, unfortunately.  But I guess everything still builds...
I don't know if it's really useful to cleanup this fake code while
leaving the real code as-is.


> @@ -1380,12 +1380,13 @@ static inline union cvmx_gmxx_rxx_rx_inbnd cvmx_spi4000_check_speed(int interfac
>  	return r;
>  }
>  
> -static inline void cvmx_pko_send_packet_prepare(uint64_t port, uint64_t queue,
> +static inline void cvmx_pko_send_packet_prepare(u64 port, u64 queue,
>  						cvmx_pko_lock_t use_locking)
>  { }
>  
> -static inline cvmx_pko_status_t cvmx_pko_send_packet_finish(uint64_t port,
> -		uint64_t queue, union cvmx_pko_command_word0 pko_command,
> +static inline cvmx_pko_status_t cvmx_pko_send_packet_finish(u64 port,
> +							    u64 queue,
> +								union cvmx_pko_command_word0 cmd,
>  		union cvmx_buf_ptr packet, cvmx_pko_lock_t use_locking)

This is messed up now.  Just leave the indenting as it was and fix it in
another change if you want to.

regards,
dan carpenter


      reply	other threads:[~2025-09-01 10:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-29 20:01 [PATCH] staging: octeon: use fixed-width integer types Osama Abdelkader
2025-09-01 10:51 ` Dan Carpenter [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aLV6lF2gutK24RtV@stanley.mountain \
    --to=dan.carpenter@linaro.org \
    --cc=abhishektamboli9@gmail.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=osama.abdelkader@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=sergio.paracuellos@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox