All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Grigori Goronzy <greg@chown.ath.cx>
Cc: Johan Hovold <johan@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 10/13] USB: ch341: clean up messages
Date: Fri, 29 Apr 2016 15:40:12 +0200	[thread overview]
Message-ID: <20160429134012.GN22229@localhost> (raw)
In-Reply-To: <1460754856-27908-11-git-send-email-greg@chown.ath.cx>

On Fri, Apr 15, 2016 at 11:14:13PM +0200, Grigori Goronzy wrote:
> No functional change.  Remove explicit function name printing, it's
> easy to use dynamic debug to print it every time, if required.

While that is true, we currently use __func__ in a lot of debug messages
as a compact form for a self-contained message (e.g. "%s - x=y\n",
__func__) and that should be ok.

> Fix capitalization and phrasing in some cases.

No need to capitalise either. I'd even prefer sticking to lower-case
consistently.

> Drop useless
> information like a USB buffer pointer, which is not helpful.
> 
> Signed-off-by: Grigori Goronzy <greg@chown.ath.cx>
> ---
>  drivers/usb/serial/ch341.c | 48 +++++++++++++++++++++-------------------------
>  1 file changed, 22 insertions(+), 26 deletions(-)
> 
> diff --git a/drivers/usb/serial/ch341.c b/drivers/usb/serial/ch341.c
> index f524aa9..22cfd88 100644
> --- a/drivers/usb/serial/ch341.c
> +++ b/drivers/usb/serial/ch341.c
> @@ -106,7 +106,7 @@ static int ch341_control_out(struct usb_device *dev, u8 request,
>  {
>  	int r;
>  
> -	dev_dbg(&dev->dev, "ch341_control_out(%02x,%02x,%04x,%04x)\n",
> +	dev_dbg(&dev->dev, "control_out(%02x,%02x,%04x,%04x)\n",

Drop this one or do use __func__ here.

>  		USB_DIR_OUT|0x40, (int)request, (int)value, (int)index);
>  
>  	r = usb_control_msg(dev, usb_sndctrlpipe(dev, 0), request,
> @@ -122,8 +122,8 @@ static int ch341_control_in(struct usb_device *dev,
>  {
>  	int r;
>  
> -	dev_dbg(&dev->dev, "ch341_control_in(%02x,%02x,%04x,%04x,%p,%u)\n",
> -		USB_DIR_IN|0x40, (int)request, (int)value, (int)index, buf,
> +	dev_dbg(&dev->dev, "control_in(%02x,%02x,%04x,%04x,%u)\n",
> +		USB_DIR_IN|0x40, (int)request, (int)value, (int)index,

Ditto.

>  		(int)bufsize);
>  
>  	r = usb_control_msg(dev, usb_rcvctrlpipe(dev, 0), request,
> @@ -327,11 +327,11 @@ static int ch341_open(struct tty_struct *tty, struct usb_serial_port *port)
>  	if (tty)
>  		ch341_set_termios(tty, port, NULL);
>  
> -	dev_dbg(&port->dev, "%s - submitting interrupt urb\n", __func__);
> +	dev_dbg(&port->dev, "Submitting interrupt URB\n");

Drop.

>  	r = usb_submit_urb(port->interrupt_in_urb, GFP_KERNEL);
>  	if (r) {
> -		dev_err(&port->dev, "%s - failed to submit interrupt urb: %d\n",
> -			__func__, r);
> +		dev_err(&port->dev,
> +			"Failed to submit interrupt URB: %d\n", r);

Error message, so I agree that this should be spelled out, but not need
to capitalise "failed".

>  		goto out;
>  	}
>  
> @@ -409,8 +409,7 @@ static void ch341_set_termios(struct tty_struct *tty,
>  				CH341_REG_RTSCTS | ((uint16_t)CH341_REG_RTSCTS << 8),
>  				0x0101);
>  		if (r < 0) {
> -			dev_err(&port->dev, "%s - USB control write error (%d)\n",
> -					__func__, r);
> +			dev_err(&port->dev, "USB control write error: %d\n", r);

Please say what went wrong instead of what function failed. (I think I
already commented on this one when you added it, fix it at the source).

>  			tty->termios.c_cflag &= ~CRTSCTS;
>  		}
>  	}
> @@ -432,29 +431,27 @@ static void ch341_break_ctl(struct tty_struct *tty, int break_state)
>  	r = ch341_control_in(port->serial->dev, CH341_REQ_READ_REG,
>  			ch341_break_reg, 0, break_reg, 2);
>  	if (r < 0) {
> -		dev_err(&port->dev, "%s - USB control read error (%d)\n",
> -				__func__, r);
> +		dev_err(&port->dev, "USB control read error: %d\n", r);

"failed to read break status: %d\n", or similar.

>  		goto out;
>  	}
> -	dev_dbg(&port->dev, "%s - initial ch341 break register contents - reg1: %x, reg2: %x\n",
> -		__func__, break_reg[0], break_reg[1]);
> +	dev_dbg(&port->dev, "Initial break register contents - reg1: %x, reg2: %x\n",
> +		break_reg[0], break_reg[1]);

__func__ is fine for compact debug messages, but you can remove the
verbose text if you want. I'd prefer the form

	"%s - x = a, y = b\n"

>  	if (break_state != 0) {
> -		dev_dbg(&port->dev, "%s - Enter break state requested\n", __func__);
> +		dev_dbg(&port->dev, "Enter break state requested\n");
>  		break_reg[0] &= ~CH341_NBREAK_BITS_REG1;
>  		break_reg[1] &= ~CH341_LCR_ENABLE_TX;
>  	} else {
> -		dev_dbg(&port->dev, "%s - Leave break state requested\n", __func__);
> +		dev_dbg(&port->dev, "Leave break state requested\n");
>  		break_reg[0] |= CH341_NBREAK_BITS_REG1;
>  		break_reg[1] |= CH341_LCR_ENABLE_TX;
>  	}

A common "%s - break = %d\n" would do instead of the two above.

> -	dev_dbg(&port->dev, "%s - New ch341 break register contents - reg1: %x, reg2: %x\n",
> -		__func__, break_reg[0], break_reg[1]);
> +	dev_dbg(&port->dev, "New break register contents - reg1: %x, reg2: %x\n",
> +		break_reg[0], break_reg[1]);

I think you get the idea, so won't comment on the rest.

Thanks,
Johan

  reply	other threads:[~2016-04-29 13:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15 21:14 Major improvements to the ch341 driver v4 Grigori Goronzy
2016-04-15 21:14 ` [PATCH v4 01/13] USB: ch341: fix error handling on resume Grigori Goronzy
2016-04-29 12:16   ` Johan Hovold
2016-04-29 15:11     ` Grigori Goronzy
2016-05-02 13:45       ` Johan Hovold
2016-04-15 21:14 ` [PATCH v4 02/13] USB: ch341: add LCR register definitions Grigori Goronzy
2016-04-29 12:18   ` Johan Hovold
2016-04-15 21:14 ` [PATCH v4 03/13] USB: ch341: add definitions for modem control Grigori Goronzy
2016-04-29 12:22   ` Johan Hovold
2016-04-15 21:14 ` [PATCH v4 04/13] USB: ch341: fix USB buffer allocations Grigori Goronzy
2016-04-29 12:52   ` Johan Hovold
2016-04-29 15:12     ` Grigori Goronzy
2016-04-15 21:14 ` [PATCH v4 05/13] USB: ch341: reinitialize chip on reconfiguration Grigori Goronzy
2016-04-29 13:03   ` Johan Hovold
2016-04-15 21:14 ` [PATCH v4 06/13] USB: ch341: add support for parity, frame length, stop bits Grigori Goronzy
2016-04-29 13:11   ` Johan Hovold
2016-04-15 21:14 ` [PATCH v4 07/13] USB: ch341: add debug output for chip version Grigori Goronzy
2016-04-29 13:13   ` Johan Hovold
2016-04-15 21:14 ` [PATCH v4 08/13] USB: ch341: add support for RTS/CTS flow control Grigori Goronzy
2016-04-29 13:23   ` Johan Hovold
2016-04-15 21:14 ` [PATCH v4 09/13] USB: ch341: fix coding style Grigori Goronzy
2016-04-29 13:29   ` Johan Hovold
2016-04-15 21:14 ` [PATCH v4 10/13] USB: ch341: clean up messages Grigori Goronzy
2016-04-29 13:40   ` Johan Hovold [this message]
2016-04-15 21:14 ` [PATCH v4 11/13] USB: ch341: improve B0 handling Grigori Goronzy
2016-04-29 13:41   ` Johan Hovold
2016-04-15 21:14 ` [PATCH v4 12/13] USB: ch341: get rid of default configuration Grigori Goronzy
2016-04-29 13:43   ` Johan Hovold
2016-04-15 21:14 ` [PATCH v4 13/13] USB: ch341: implement tx_empty callback Grigori Goronzy
2016-04-29 13:47   ` Johan Hovold
2016-04-28 23:24 ` Major improvements to the ch341 driver v4 Grigori Goronzy

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=20160429134012.GN22229@localhost \
    --to=johan@kernel.org \
    --cc=greg@chown.ath.cx \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.