[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YgS2dAHofenuyVjg@kroah.com>
Date: Thu, 10 Feb 2022 07:53:40 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Leonardo Araujo <leonardo.aa88@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-staging@...ts.linux.dev
Subject: Re: [PATCH] Staging: r8188eu: core: Avoid CamelCase: <bEnterPS>
On Wed, Feb 09, 2022 at 05:57:40PM -0300, Leonardo Araujo wrote:
> Fixed a coding style issue.
Please read the kernel documentation for how to write better subject
lines and changelog texts. These need a lot of work, you can't just put
the checkpatch message in the subject and then nothing in the changelog
body.
>
> Signed-off-by: Leonardo Araujo <leonardo.aa88@...il.com>
> ---
> drivers/staging/r8188eu/core/rtw_cmd.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/r8188eu/core/rtw_cmd.c b/drivers/staging/r8188eu/core/rtw_cmd.c
> index e42119e16284..4ec4da6d3078 100644
> --- a/drivers/staging/r8188eu/core/rtw_cmd.c
> +++ b/drivers/staging/r8188eu/core/rtw_cmd.c
> @@ -880,7 +880,7 @@ u8 rtw_set_chplan_cmd(struct adapter *padapter, u8 chplan)
>
> static void traffic_status_watchdog(struct adapter *padapter)
> {
> - u8 bEnterPS;
> + u8 b_enter_ps;
No, think about what you are changing here. Why keep the "b" at all?
What does this variable name? Why was there a "b" to start with?
> u8 bBusyTraffic = false, bTxBusyTraffic = false, bRxBusyTraffic = false;
What about all of these other variables, why ignore them and not send a
patch series to fix them all up?
Remember where the "b" comes from, this is "hungarian notation" and is
trying to describe the type of the variable, which makes no sense in
this century. Please do not keep it around for no reason at all.
thanks,
greg k-h
Powered by blists - more mailing lists