From: Dan Carpenter <error27@gmail.com>
To: bruce ou <oubruce1234@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: fix CamelCase warnings in rtw_efuse.c
Date: Tue, 23 Jun 2026 14:28:36 +0300 [thread overview]
Message-ID: <ajpt5G71ap5Vzk5T@stanley.mountain> (raw)
In-Reply-To: <CA+h2PQjd8D7yiF8N8R-FwtTFfT7gJH-z9jMOA84esykGP4J+bw@mail.gmail.com>
On Tue, Jun 23, 2026 at 07:25:55PM +0800, bruce ou wrote:
> Hi Dan,
>
> Thank you for your review and guidance!
>
> I have switched my local tree to the latest staging/staging-next branch
> and squashed all the CamelCase local variable cleanups in rtw_efuse.c
> into a single, comprehensive patch with a proper commit message.
>
> I will send the new patch shortly.
Not as one patch, but as a collection of patches in a patchset.
regards,
dan carpenter
prev parent reply other threads:[~2026-06-23 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 7:55 [PATCH] staging: rtl8723bs: fix CamelCase warnings in rtw_efuse.c Bruce Ou
2026-06-23 9:21 ` Dan Carpenter
2026-06-23 11:25 ` bruce ou
2026-06-23 11:28 ` 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=ajpt5G71ap5Vzk5T@stanley.mountain \
--to=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=oubruce1234@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.