From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: "Esther Zilberberg" <esty5664@gmail.com>,
"Ethan Tidmore" <ethantidmore06@gmail.com>
Cc: <gregkh@linuxfoundation.org>, <arthur.stupa@gmail.com>,
<jannik@jrehkemper.de>, <william.hansen.baird@gmail.com>,
<kaizhetan@yahoo.com>, <s9430939@naver.com>,
<straube.linux@gmail.com>, <ysinghcin@gmail.com>,
<kees@kernel.org>, <linux-staging@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: rtl8723bs: rename supportRateNum to support_rate_num
Date: Wed, 04 Mar 2026 15:00:44 -0600 [thread overview]
Message-ID: <DGUATZH7A7R7.UIOINNCCWP8V@gmail.com> (raw)
In-Reply-To: <CAPMPFbjpTjwMfK_hawUnF_CmiKPaZ0w6V+f5_NcGVKC4B6UhGg@mail.gmail.com>
On Wed Mar 4, 2026 at 2:39 PM CST, Esther Zilberberg wrote:
> On Mon, Mar 2, 2026 at 7:43 PM Ethan Tidmore <ethantidmore06@gmail.com> wrote:
>>
>> On Mon Mar 2, 2026 at 3:08 AM CST, Esther Zilberberg wrote:
>> > Rename supportRateNum to support_rate_num to fix warning
>> > reported by checkpatch.pl.
>> >
>> > Signed-off-by: Esther Zilberberg <esty5664@gmail.com>
>> > ---
...
> I am using the mainline (master) branch.
>
> Thanks,
> Esther
When I tried to apply this patch against staging-next it didn't apply
cleanly, so try and rebase it against staging-next.
Thanks,
ET
next prev parent reply other threads:[~2026-03-04 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 9:08 [PATCH] staging: rtl8723bs: rename supportRateNum to support_rate_num Esther Zilberberg
2026-03-02 17:43 ` Ethan Tidmore
2026-03-04 20:39 ` Esther Zilberberg
2026-03-04 21:00 ` Ethan Tidmore [this message]
2026-03-07 23:54 ` Esther Zilberberg
-- strict thread matches above, loose matches on Subject: below --
2026-02-09 16:34 Esther Zilberberg
2026-02-23 14:40 ` Greg KH
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=DGUATZH7A7R7.UIOINNCCWP8V@gmail.com \
--to=ethantidmore06@gmail.com \
--cc=arthur.stupa@gmail.com \
--cc=esty5664@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jannik@jrehkemper.de \
--cc=kaizhetan@yahoo.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=s9430939@naver.com \
--cc=straube.linux@gmail.com \
--cc=william.hansen.baird@gmail.com \
--cc=ysinghcin@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