Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain;
        charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.2\))
Subject: Re: [PATCH] staging: rtl8192e: Fix BRACES warning
From:   David de Barros Tadokoro <davidbtadokoro@usp.br>
In-Reply-To: <2023052830-steep-runway-fceb@gregkh>
Date:   Sun, 28 May 2023 12:27:38 -0300
Cc:     linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <80495326-3EB0-4AE3-A328-D93BB9109AD0@usp.br>
References: <20230524040051.235250-1-davidbtadokoro@usp.br>
 <2023052830-steep-runway-fceb@gregkh>
To:     Greg KH <gregkh@linuxfoundation.org>
Precedence: bulk

> On 28 May 2023, at 06:10, Greg KH <gregkh@linuxfoundation.org> wrote:
>=20
> On Wed, May 24, 2023 at 01:00:51AM -0300, David Tadokoro wrote:
>> Fix checkpatch warning "braces {} are not necessary for single =
statement
>> blocks".
>=20
> Why do you have "BRACES" in the subject line as all caps?  Where did
> that term come from?
>=20
> No need to shout :)
>=20
> thanks,
>=20
> greg k-h

Hi, Greg

Thanks so much for your feedback.

You are right, this commit message is horrible. I based it on
a previous commit that cleaned the same warning instead of writing a =
good commit message myself. Going to fix that.

Sorry for the mess ;)

Many regards,
David=