From: Dan Carpenter <dan.carpenter@linaro.org>
To: vivek t s <vivek6429.ts@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: rtl8723bs: Rename function SelectChannel()
Date: Wed, 28 Aug 2024 13:25:10 +0300 [thread overview]
Message-ID: <2092a3f1-e319-45c5-a33c-3f271e70785f@stanley.mountain> (raw)
In-Reply-To: <Zs7vQXhcYRCxCDaH@victor-IdeaPad-Gaming-3-16IAH7>
On Wed, Aug 28, 2024 at 03:04:57PM +0530, vivek t s wrote:
> Rename SelectChannel() to select_channel() to avoid
> CamelCase warning from checkpatch.
I wouldn't have commented on this except there are some other issues.
Line wrap your commit message at 72-75 characters (similar to email).
So "CamelCase warning" moves to the line before.
Rename SelectChannel() to select_channel() to avoid CamelCase warning
from checkpatch.
>
> compile tested.
>
Put this under the --- cut off. (This is the real reason why I'm responding to
your patch)
> Signed-off-by: vivek t s <vivek6429.ts@gmail.com>
Your signed-off-by is like signing a legal document. If you were buying a
house, then would you write your name like this? If so then that's fine.
> ---
^^^
Cut off line here.
regards,
dan carpenter
> drivers/staging/rtl8723bs/core/rtw_ap.c | 4 ++--
> drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 4 ++--
> drivers/staging/rtl8723bs/core/rtw_wlan_util.c | 2 +-
> drivers/staging/rtl8723bs/include/rtw_mlme_ext.h | 2 +-
> 4 files changed, 6 insertions(+), 6 deletions(-)
prev parent reply other threads:[~2024-08-28 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 9:34 [PATCH] Staging: rtl8723bs: Rename function SelectChannel() vivek t s
2024-08-28 9:38 ` Greg KH
2024-08-28 10:01 ` YOUR NAME
2024-08-28 10:25 ` Dan Carpenter [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=2092a3f1-e319-45c5-a33c-3f271e70785f@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=vivek6429.ts@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