From: Greg KH <gregkh@linuxfoundation.org>
To: Edson Juliano Drosdeck <edson.drosdeck@gmail.com>
Cc: hdegoede@redhat.com, Larry.Finger@lwfinger.net,
ruanjinjie@huawei.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: Remove unnecessary bracks
Date: Sun, 15 Oct 2023 18:19:20 +0200 [thread overview]
Message-ID: <2023101548-catalyze-employed-a617@gregkh> (raw)
In-Reply-To: <20231013002944.14607-1-edson.drosdeck@gmail.com>
On Thu, Oct 12, 2023 at 09:29:44PM -0300, Edson Juliano Drosdeck wrote:
> Warning found by checkpatch.pl script.Remove bracks than are not necessary for
> a single statement blocks in hal/odm.c
"bracks"? I think it is called "brackets", right?
thanks,
greg k-h
next prev parent reply other threads:[~2023-10-15 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 0:29 [PATCH] staging: rtl8723bs: Remove unnecessary bracks Edson Juliano Drosdeck
2023-10-15 16:19 ` Greg KH [this message]
2023-10-15 16:35 ` edson drosdeck
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=2023101548-catalyze-employed-a617@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=edson.drosdeck@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=ruanjinjie@huawei.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