All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Payal Kshirsagar <payalskshirsagar1234@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [PATCH] [Outreachy kernel] staging: wfx: remove blank line
Date: Mon, 9 Mar 2020 12:41:28 +0100	[thread overview]
Message-ID: <20200309124128.10c8bf6d@elisabeth> (raw)
In-Reply-To: <20200308184130.5458-1-payalskshirsagar1234@gmail.com>

On Mon,  9 Mar 2020 00:11:30 +0530
Payal Kshirsagar <payalskshirsagar1234@gmail.com> wrote:

> Blank line is not necessary before a close brace '}', remove it.
> 
> Signed-off-by: Payal Kshirsagar <payalskshirsagar1234@gmail.com>
> ---
>  drivers/staging/wfx/data_rx.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/staging/wfx/data_rx.c b/drivers/staging/wfx/data_rx.c
> index 5d198457c6ce..2a09f6b978c3 100644
> --- a/drivers/staging/wfx/data_rx.c
> +++ b/drivers/staging/wfx/data_rx.c
> @@ -62,7 +62,6 @@ static int wfx_drop_encrypt_data(struct wfx_dev *wdev,
>  	memmove(skb->data + iv_len, skb->data, hdrlen);
>  	skb_pull(skb, iv_len);
>  	return 0;
> -
>  }
>  
>  void wfx_rx_cb(struct wfx_vif *wvif,

As you're removing one single blank line from a single function, for
the future, the commit title could be more descriptive: "staging: wfx:
remove excess newline in wfx_drop_encrypt_data()". This might be
subject to personal taste, though. Change looks good per se.

Same here, you should Cc: more people.

-- 
Stefano



  reply	other threads:[~2020-03-09 11:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-08 18:41 [PATCH] [Outreachy kernel] staging: wfx: remove blank line Payal Kshirsagar
2020-03-09 11:41 ` Stefano Brivio [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-03-09 16:55 Payal Kshirsagar
2020-03-09 17:36 ` Jérôme Pouiller

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=20200309124128.10c8bf6d@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=payalskshirsagar1234@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 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.