linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sevinj Aghayeva <sevinj.aghayeva@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	outreachy@lists.linux.dev
Subject: Re: [PATCH 1/3] staging: rtl8723bs: remove redundant braces in if statements
Date: Sun, 3 Apr 2022 13:03:32 +0200	[thread overview]
Message-ID: <Ykl/BCgJx1V7OHSI@kroah.com> (raw)
In-Reply-To: <d157392b32cbc02455f8c1813a09c5cc8f11fcf7.1648817213.git.sevinj.aghayeva@gmail.com>

On Fri, Apr 01, 2022 at 09:02:45AM -0400, Sevinj Aghayeva wrote:
> Adhere to Linux kernel coding style.
> 
> Reported by checkpatch:
> 
> WARNING: braces {} are not necessary for single statement blocks
> 
> Signed-off-by: Sevinj Aghayeva <sevinj.aghayeva@gmail.com>
> ---
>  drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 76 +++++++------------
>  1 file changed, 26 insertions(+), 50 deletions(-)

Does not apply to my tree :(

  reply	other threads:[~2022-04-03 11:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01 13:02 [PATCH 0/3] rlt8723bs cleanup Sevinj Aghayeva
2022-04-01 13:02 ` [PATCH 1/3] staging: rtl8723bs: remove redundant braces in if statements Sevinj Aghayeva
2022-04-03 11:03   ` Greg Kroah-Hartman [this message]
2022-04-01 13:02 ` [PATCH 2/3] staging: rtl8723bs: place constants on the right side of tests Sevinj Aghayeva
2022-04-01 13:02 ` [PATCH 3/3] staging: rtl8723bs: remove redundant else branches Sevinj Aghayeva
2022-04-01 18:08   ` kernel test robot
2022-04-03 11:03   ` Greg Kroah-Hartman
2022-04-03 15:33     ` Sevinj Aghayeva
2022-04-01 19:06 [PATCH v2 0/3] rlt8723bs cleanup Sevinj Aghayeva
2022-04-01 19:06 ` [PATCH 1/3] staging: rtl8723bs: remove redundant braces in if statements Sevinj Aghayeva

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=Ykl/BCgJx1V7OHSI@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=outreachy@lists.linux.dev \
    --cc=sevinj.aghayeva@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;
as well as URLs for NNTP newsgroup(s).