From: Greg KH <gregkh@linuxfoundation.org>
To: Dragan Cvetic <dragan.m.cvetic@gmail.com>
Cc: philipp.g.hortmann@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: rtl8192e: Rename Enable, cck_Rx_path and disabledRF
Date: Sun, 23 Oct 2022 17:41:14 +0200 [thread overview]
Message-ID: <Y1Vgms28JIPluZ45@kroah.com> (raw)
In-Reply-To: <20221022151506.63725-1-dragan.m.cvetic@gmail.com>
On Sat, Oct 22, 2022 at 04:15:06PM +0100, Dragan Cvetic wrote:
> Rename variable Enable to enable, cck_Rx_path to cck_rx_path and
> disabledRF to disabled_rf to avoid CamelCase which is not accepted
> by checkpatch.
>
> Signed-off-by: Dragan Cvetic <dragan.m.cvetic@gmail.com>
Any reason you didn't cc: the staging tree maintainer? :(
Anyway, this changelog is confusing, you just list some random variable
names that you have changed, without any explaining what ties them
together.
The code itself gives you a clue:
> struct drx_path_sel {
> - u8 Enable;
> + u8 enable;
> u8 cck_method;
> - u8 cck_Rx_path;
> + u8 cck_rx_path;
>
> u8 SS_TH_low;
> u8 diff_TH;
> - u8 disabledRF;
> + u8 disabled_rf;
> u8 reserved;
>
> u8 rf_rssi[4];
Ah, you are fixing up the drx_path_sel structure.
But just some of the fields, not all of them, odd.
Please redo this and make the changelog more descriptive of what you are
doing, as well as the subject line (don't need the variable names in
there.)
Also do it for all the fields in the structure, not just 3 random ones.
thanks,
greg k-h
prev parent reply other threads:[~2022-10-23 15:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 15:15 [PATCH v2] staging: rtl8192e: Rename Enable, cck_Rx_path and disabledRF Dragan Cvetic
2022-10-23 15:41 ` Greg KH [this message]
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=Y1Vgms28JIPluZ45@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dragan.m.cvetic@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=philipp.g.hortmann@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).