public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Quentin Deslandes <quentin.deslandes@itdev.co.uk>
To: Gabriela Bittencourt <gabrielabittencourt00@gmail.com>
Cc: "outreachy-kernel@googlegroups.com" 
	<outreachy-kernel@googlegroups.com>,
	"forest@alittletooquiet.net" <forest@alittletooquiet.net>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"trivial@kernel.org" <trivial@kernel.org>
Subject: Re: [PATCH] staging: vt6656: remove duplicated blank line
Date: Mon, 7 Oct 2019 09:33:14 +0000	[thread overview]
Message-ID: <20191007093313.GA9232@qd-ubuntu> (raw)
In-Reply-To: <20191006195854.9843-1-gabrielabittencourt00@gmail.com>

On Sun, Oct 06, 2019 at 04:58:54PM -0300, Gabriela Bittencourt wrote:
> Cleans up checks of "don't use multiple blank line"
> 
> Signed-off-by: Gabriela Bittencourt <gabrielabittencourt00@gmail.com>
> ---
>  drivers/staging/vt6656/main_usb.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/staging/vt6656/main_usb.c b/drivers/staging/vt6656/main_usb.c
> index 856ba97aec4f..a1884b5cc915 100644
> --- a/drivers/staging/vt6656/main_usb.c
> +++ b/drivers/staging/vt6656/main_usb.c
> @@ -362,7 +362,6 @@ static int vnt_init_registers(struct vnt_private *priv)
>  			goto end;
>  	}
>  
> -
>  	ret = vnt_mac_set_led(priv, LEDSTS_TMLEN, 0x38);
>  	if (ret)
>  		goto end;
> -- 
> 2.20.1
> 

Reviewed-by: Quentin Deslandes <quentin.deslandes@itdev.co.uk>

Thank you,
Quentin

      reply	other threads:[~2019-10-07  9:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-06 19:58 [PATCH] staging: vt6656: remove duplicated blank line Gabriela Bittencourt
2019-10-07  9:33 ` Quentin Deslandes [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=20191007093313.GA9232@qd-ubuntu \
    --to=quentin.deslandes@itdev.co.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=forest@alittletooquiet.net \
    --cc=gabrielabittencourt00@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=trivial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox