From: "Bera Yüzlü" <b9788213@gmail.com>
To: tommyguo039@gmail.com
Cc: b9788213@gmail.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
tommyguo024@outlook.com
Subject: Re: [PATCH v2] staging: rtl8723bs: fix CamelCase warning for READ_MACREG
Date: Sun, 29 Mar 2026 12:35:09 +0300 [thread overview]
Message-ID: <20260329093508.11560-2-b9788213@gmail.com> (raw)
In-Reply-To: <20260329075941.60247-1-tommyguo024@outlook.com>
On Sun, 29 Mar 2026 03:59:41 -0400, Xiyuan Guo wrote:
> Rename the _Read_MACREG macro to READ_MACREG to resolve the
> checkpatch.pl "Avoid CamelCase" warning.
>
> Signed-off-by: Xiyuan Guo <tommyguo024@outlook.com>
> ---
You sent this patch with tommyguo039@gmail.com but signed with
tommyguo024@outlook.com. Also add a changelog after the '---' and wait
at least 24h before the next version.
Thanks,
Bera
next prev parent reply other threads:[~2026-03-29 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 7:59 [PATCH v2] staging: rtl8723bs: fix CamelCase warning for READ_MACREG Xiyuan Guo
2026-03-29 9:35 ` Bera Yüzlü [this message]
2026-03-29 18:34 ` Tommy
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=20260329093508.11560-2-b9788213@gmail.com \
--to=b9788213@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=tommyguo024@outlook.com \
--cc=tommyguo039@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