mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Thomas Vegas <thomas_75@safe-mail.net>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	devel@driverdev.osuosl.org
Subject: Re: [PATCH] staging: serqt_usb2: Add blank lines after declarations.
Date: Sun, 30 Mar 2014 19:02:41 -0700	[thread overview]
Message-ID: <1396231361.21529.14.camel@joe-AO722> (raw)
In-Reply-To: <d1406d30f213cce36c8974925642fe19@mwinf5d23.me-wanadoo.net>

On Sun, 2014-03-30 at 23:29 +0200, Thomas Vegas wrote:
> Use a more common kernel coding style.
[]
> diff --git a/drivers/staging/serqt_usb2/serqt_usb2.c b/drivers/staging/serqt_usb2/serqt_usb2.c
[]
> @@ -995,8 +995,8 @@ static void qt_close(struct usb_serial_port *port)
>  	struct tty_struct *tty;
>  	int status;
>  	unsigned int index;
> -	status = 0;
>  
> +	status = 0;

My preference would be to change the declarations to

	struct tty_struct *tty = tty_port_tty_get(&port->port);
	unsigned int index = port->port_number;
	int status = 0;

>  	tty = tty_port_tty_get(&port->port);
>  	index = port->port_number;
>  
> @@ -1268,8 +1268,8 @@ static void qt_set_termios(struct tty_struct *tty,
>  	if (I_IXOFF(tty) || I_IXON(tty)) {
>  		unsigned char stop_char = STOP_CHAR(tty);
>  		unsigned char start_char = START_CHAR(tty);
> -		status =
> -		    box_set_sw_flow_ctrl(port->serial, index, stop_char,
> +
> +		status = box_set_sw_flow_ctrl(port->serial, index, stop_char,
>  				      start_char);

Please realign start_char to the open parenthesis

		status = box_set_sw_flow_ctrl(port->serial, index, stop_char,
					      start_char);



      reply	other threads:[~2014-03-31  2:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-30 21:29 Thomas Vegas
2014-03-31  2:02 ` Joe Perches [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=1396231361.21529.14.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas_75@safe-mail.net \
    /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

all inboxes | Powered by JetHome®