Linux kernel staging patches
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Deepak R Varma <drv@mailo.com>
Cc: outreachy@lists.linux.dev, Larry.Finger@lwfinger.net,
	 phil@philpotter.co.uk, paskripkin@gmail.com,
	gregkh@linuxfoundation.org,  linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org,  kumarpraveen@linux.microsoft.com,
	saurabh.truth@gmail.com
Subject: Re: [PATCH 3/4] staging: r8188eu: remove {} for single statement blocks
Date: Mon, 17 Oct 2022 15:57:16 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2210171556290.16433@hadrien> (raw)
In-Reply-To: <478d652b9f467d47685c1af72a876f34dd92710f.1666011479.git.drv@mailo.com>



On Mon, 17 Oct 2022, Deepak R Varma wrote:

> As per the Linux kernel coding-style guidelines, there is no need to
> use {} for single statement blocks. Address following checkpatch script
> complaint:
> 	WARNING: braces {} are not necessary for single statement blocks

It's nice to say something like "Problem identified using checkpatch".
But putting the verbatim checkpatch message that says what you just said
doesn't seem necessary.

julia

>
> Signed-off-by: Deepak R Varma <drv@mailo.com>
> ---
>  drivers/staging/r8188eu/core/rtw_br_ext.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/staging/r8188eu/core/rtw_br_ext.c b/drivers/staging/r8188eu/core/rtw_br_ext.c
> index 427da7e8ba4c..290affe50d0b 100644
> --- a/drivers/staging/r8188eu/core/rtw_br_ext.c
> +++ b/drivers/staging/r8188eu/core/rtw_br_ext.c
> @@ -655,9 +655,8 @@ void *scdb_findEntry(struct adapter *priv, unsigned char *ip_addr)
>  	hash = __nat25_network_hash(network_addr);
>  	db = priv->nethash[hash];
>  	while (db) {
> -		if (!memcmp(db->networkAddr, network_addr, MAX_NETWORK_ADDR_LEN)) {
> +		if (!memcmp(db->networkAddr, network_addr, MAX_NETWORK_ADDR_LEN))
>  			return (void *)db;
> -		}
>
>  		db = db->next_hash;
>  	}
> --
> 2.30.2
>
>
>
>
>

  reply	other threads:[~2022-10-17 13:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 13:20 [PATCH 0/4] staging: r8188eu: trivial code cleanup patches Deepak R Varma
2022-10-17 13:21 ` [PATCH 1/4] staging: r8188eu: use Linux kernel variable naming convention Deepak R Varma
2022-10-17 13:56   ` Julia Lawall
2022-10-17 14:12     ` Deepak R Varma
2022-10-17 13:23 ` [PATCH 3/4] staging: r8188eu: remove {} for single statement blocks Deepak R Varma
2022-10-17 13:57   ` Julia Lawall [this message]
2022-10-17 14:13     ` Deepak R Varma
2022-10-17 13:24 ` [PATCH 4/4] staging: r8188eu: use htons macro instead of __constant_htons Deepak R Varma
2022-10-19  6:08   ` Joe Perches
2022-10-19  9:27     ` Deepak R Varma
2022-11-05 15:00     ` Deepak R Varma
2022-10-17 13:26 ` [PATCH 2/4] staging: r8188eu: reformat long computation lines Deepak R Varma
2022-10-17 13:22   ` Deepak R Varma
2022-10-17 14:09   ` Greg KH
2022-10-17 14:10     ` Deepak R Varma
2022-10-17 14:52       ` Greg KH
2022-10-18 11:21     ` David Laight
2022-10-18 12:42       ` Deepak R Varma
2022-10-19  5:43         ` Joe Perches
2022-10-19  6:17           ` Deepak R Varma
2022-10-19  6:38             ` Joe Perches
2022-10-19  6:44               ` Deepak R Varma
2022-10-19  9:02                 ` Deepak R Varma

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=alpine.DEB.2.22.394.2210171556290.16433@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=Larry.Finger@lwfinger.net \
    --cc=drv@mailo.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kumarpraveen@linux.microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=outreachy@lists.linux.dev \
    --cc=paskripkin@gmail.com \
    --cc=phil@philpotter.co.uk \
    --cc=saurabh.truth@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