public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Johan Hovold <johan@kernel.org>
Cc: Lode Willems <me@lodewillems.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: serial: ch341: use fix-width types consistently
Date: Wed, 8 Jan 2025 13:10:43 +0100	[thread overview]
Message-ID: <2025010835-foil-designer-84e0@gregkh> (raw)
In-Reply-To: <20250108101518.30607-1-johan@kernel.org>

On Wed, Jan 08, 2025 at 11:15:18AM +0100, Johan Hovold wrote:
> Use Linux fix-width types consistently and drop a related unnecessary
> cast.
> 
> Signed-off-by: Johan Hovold <johan@kernel.org>
> ---
>  drivers/usb/serial/ch341.c | 7 +++----
>  1 file changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/usb/serial/ch341.c b/drivers/usb/serial/ch341.c
> index ac74b353b26d..7cc36f84821f 100644
> --- a/drivers/usb/serial/ch341.c
> +++ b/drivers/usb/serial/ch341.c
> @@ -660,13 +660,12 @@ static int ch341_simulate_break(struct tty_struct *tty, int break_state)
>  
>  static int ch341_break_ctl(struct tty_struct *tty, int break_state)
>  {
> -	const uint16_t ch341_break_reg =
> -			((uint16_t) CH341_REG_LCR << 8) | CH341_REG_BREAK;
> +	const u16 ch341_break_reg = (CH341_REG_LCR << 8) | CH341_REG_BREAK;
>  	struct usb_serial_port *port = tty->driver_data;
>  	struct ch341_private *priv = usb_get_serial_port_data(port);
> +	u16 reg_contents;
> +	u8 break_reg[2];
>  	int r;
> -	uint16_t reg_contents;
> -	uint8_t break_reg[2];
>  
>  	if (priv->quirks & CH341_QUIRK_SIMULATE_BREAK)
>  		return ch341_simulate_break(tty, break_state);
> -- 
> 2.45.2
> 
> 

Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

      reply	other threads:[~2025-01-08 12:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08 10:15 [PATCH] USB: serial: ch341: use fix-width types consistently Johan Hovold
2025-01-08 12:10 ` Greg KH [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=2025010835-foil-designer-84e0@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=me@lodewillems.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