From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: "Luka Gejak" <luka.gejak@linux.dev>,
<pavankumaryalagada@gmail.com>, <gregkh@linuxfoundation.org>,
<outreachy@lists.linux.dev>
Cc: <error27@gmail.com>, <ethantidmore06@gmail.com>,
<dennylin0707@gmail.com>, <linux-staging@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: rtl8723bs: remove unnecessary parentheses
Date: Thu, 15 Oct 2026 10:41:53 -0500 [thread overview]
Message-ID: <DM5IYFCRBE9W.1U3KCU36BUE36@gmail.com> (raw)
In-Reply-To: <5d577cb1b4a91e8cdfda171bc7100105ae90d91e@linux.dev>
On Thu Oct 15, 2026 at 9:11 AM CDT, Luka Gejak wrote:
> October 15, 2026 at 2:06 PM, pavankumaryalagada@gmail.com wrote:
>
>
>>
>> From: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
>>
>> Remove redundant parentheses around the address-of operator to
>> follow kernel coding style.
>>
>> Signed-off-by: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
>> ---
>
> Hi Yalagada,
>
> I'm just letting you know that this change is no longer needed as the
> entire staging/rtl8723bs driver is being deprecated and removed.
> Support for RTL8723BS has been ported to rtw88 subsystem.
So rtl8723bs patches aren't being accepted anymore? I saw Dan reviewing
one earlier, just wondering.
>
> Best regards,
> Luka Gejak
next prev parent reply other threads:[~2026-10-15 15:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 12:06 [PATCH] staging: rtl8723bs: remove unnecessary parentheses pavankumaryalagada
2026-10-15 14:11 ` Luka Gejak
2026-10-15 15:31 ` Jeremy Clifton
2026-10-15 15:31 ` Yalagada Pavan Kumar
2026-10-15 15:41 ` Ethan Tidmore [this message]
2026-10-15 15:57 ` Luka Gejak
-- strict thread matches above, loose matches on Subject: below --
2026-05-30 3:16 Eugene Mavick
2026-02-22 7:26 Yan Pan
2026-01-29 22:17 Siwanan Bungtong
2025-12-04 11:53 [PATCH] staging: rtl8723bs: Remove " Nazar Kletskii
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=DM5IYFCRBE9W.1U3KCU36BUE36@gmail.com \
--to=ethantidmore06@gmail.com \
--cc=dennylin0707@gmail.com \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=luka.gejak@linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=pavankumaryalagada@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