public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Tony Chung <tony467913@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 2/6] drivers: usb: serial: mos7840: Fix Block comments coding style warnings
Date: Tue, 11 Feb 2025 10:27:36 +0100	[thread overview]
Message-ID: <Z6sYCJEsTDth_Nld@hovoldconsulting.com> (raw)
In-Reply-To: <20241025061711.198933-3-tony467913@gmail.com>

On Fri, Oct 25, 2024 at 02:17:10PM +0800, Tony Chung wrote:
> fix block comments coding style warnings.
> 1. Block comments use * on subsequent lines
> 2. Block comments use a trailing */ on a separate line

Just say something like:

	Clean up the style of the block comments.

or similar.

> Signed-off-by: Tony Chung <tony467913@gmail.com>
> ---
>  drivers/usb/serial/mos7840.c | 20 +++++++++++++-------
>  1 file changed, 13 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/usb/serial/mos7840.c b/drivers/usb/serial/mos7840.c
> index dcaed0f26..b1a794f99 100644
> --- a/drivers/usb/serial/mos7840.c
> +++ b/drivers/usb/serial/mos7840.c
> @@ -282,7 +282,8 @@ static int mos7840_set_uart_reg(struct usb_serial_port *port, __u16 reg,
>  	struct usb_device *dev = port->serial->dev;
>  	val = val & 0x00ff;
>  	/* For the UART control registers, the application number need
> -	   to be Or'ed */
> +	 * to be Or'ed
> +	 */
>  	if (port->serial->num_ports == 2 && port->port_number != 0)
>  		val |= ((__u16)port->port_number + 2) << 8;
>  	else
> @@ -1539,8 +1540,9 @@ static int mos7840_port_probe(struct usb_serial_port *port)
>  	int pnum;
>  	__u16 Data;
>  
> -	/* we set up the pointers to the endpoints in the mos7840_open *
> -	 * function, as the structures aren't created yet.             */
> +	/* we set up the pointers to the endpoints in the mos7840_open

This style is only valid in networking code; the format for block
comments should generally be:

	/*
	 * ...
	 */
	 
> +	 * function, as the structures aren't created yet.
> +	 */
>  
>  	pnum = port->port_number;
>  
> @@ -1551,14 +1553,16 @@ static int mos7840_port_probe(struct usb_serial_port *port)
>  
>  	/* Initialize all port interrupt end point to port 0 int
>  	 * endpoint. Our device has only one interrupt end point
> -	 * common to all port */
> +	 * common to all port
> +	 */
>  
>  	mos7840_port->port = port;
>  	spin_lock_init(&mos7840_port->pool_lock);
>  
>  	/* minor is not initialised until later by
>  	 * usb-serial.c:get_free_serial() and cannot therefore be used
> -	 * to index device instances */
> +	 * to index device instances
> +	 */
>  	mos7840_port->port_num = pnum + 1;
>  	dev_dbg(&port->dev, "port->minor = %d\n", port->minor);
>  	dev_dbg(&port->dev, "mos7840_port->port_num = %d\n", mos7840_port->port_num);
> @@ -1591,7 +1595,8 @@ static int mos7840_port_probe(struct usb_serial_port *port)
>  		dev_dbg(&port->dev, "ControlReg Reading success val is %x, status%d\n", Data, status);
>  	Data |= 0x08;	/* setting driver done bit */
>  	Data |= 0x04;	/* sp1_bit to have cts change reflect in
> -			   modem status reg */
> +			 * modem status reg
> +			 */

Just drop the new line, this can be an exception to the 80 char rule if
you can't find a good way to rephrase this.

>  	/* Data |= 0x20; //rx_disable bit */
>  	status = mos7840_set_reg_sync(port,

Johan

  reply	other threads:[~2025-02-11  9:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23  9:14 [PATCH] usb: serial: mos7840: Fix coding style warnings Tony Chung
2024-10-23 10:04 ` Greg KH
2024-10-24 17:37 ` kernel test robot
2024-10-24 17:58 ` kernel test robot
2024-10-25  6:17   ` [PATCH v2 0/6] " Tony Chung
2025-02-11  9:15     ` Johan Hovold
2024-10-25  6:17   ` [PATCH v2 1/6] driver: usb: serial: mos7840: fix " Tony Chung
2025-02-11  9:20     ` Johan Hovold
2024-10-25  6:17   ` [PATCH v2 2/6] drivers: usb: serial: mos7840: Fix Block comments coding " Tony Chung
2025-02-11  9:27     ` Johan Hovold [this message]
2024-10-25  6:17   ` [PATCH v2 3/6] drivers: usb: serial: mos7840: fix " Tony Chung
2025-02-11  9:28     ` Johan Hovold
2024-10-25  6:17   ` [PATCH v2 4/6] drivers: usb: serial: mos7840: using '__func__' to replace function name in dbg message Tony Chung
2025-02-11  9:29     ` Johan Hovold
2025-02-11  9:32       ` Greg KH
2025-02-11  9:38         ` Johan Hovold
2024-10-25  6:17   ` [PATCH v2 5/6] drivers: usb: serial: mos7840: replace 'unsigned' w/ 'unsigned int' Tony Chung
2025-02-11  9:31     ` Johan Hovold
2024-10-25  6:17   ` [PATCH v2 6/6] drivers: usb: serial: mos7840: fix the quoted string split across lines Tony Chung
2025-02-11  9:32     ` Johan Hovold
2024-10-25  7:49 ` [PATCH] usb: serial: mos7840: Fix coding style warnings kernel test robot
2024-10-28  5:27   ` Tony Chung

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=Z6sYCJEsTDth_Nld@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=tony467913@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