All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luka Gejak" <luka.gejak@linux.dev>
To: "Cen Zhang" <cenzhang@linux.microsoft.com>,
	"Greg KH" <gregkh@linuxfoundation.org>
Cc: "Linus Probert" <linus.probert@gmail.com>,
	"Jennifer Guo" <guojy.bj@gmail.com>,
	"Khushal Chitturi" <khushalchitturi@gmail.com>,
	"Oskar Ray-Frayssinet" <rayfraytech@gmail.com>,
	"Moksh Panicker" <mokshpanicker.7@gmail.com>,
	"Andrei Khomenkov" <khomenkov@mailbox.org>,
	"Quentin Strydom" <qstrydom0@gmail.com>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	luka.gejak@linux.dev
Subject: Re: [PATCH] staging: rtl8723bs: hal: fix a multi-line comment in hal_btcoex.c
Date: Wed, 07 Oct 2026 13:12:09 +0000	[thread overview]
Message-ID: <d2f64843fa25fe259109aa19b1592d82745e40b9@linux.dev> (raw)
In-Reply-To: <20261007123221.60521-1-cenzhang@linux.microsoft.com>

October 7, 2026 at 14:32, "Cen Zhang" <cenzhang@linux.microsoft.com> wrote:


> 
> From: "Cen Zhang (Microsoft)" <cenzhang@linux.microsoft.com>
> 
> The comment in the BTC_GET_BL_WIFI_SCAN switch case of halbtcoutsrc_Get()
> has coding style issues.
> 
> Fix them by placing the opening and closing comment delimiters on
> separate lines, and keeping each line within 80 columns.
> 
> Signed-off-by: Cen Zhang (Microsoft) <cenzhang@linux.microsoft.com>
> ---
[...]

Hi Cen,

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 (rtw-next) and a pull
request that will get it into wireless-next is being sent tomorrow.

Best regards,
Luka Gejak

  reply	other threads:[~2026-10-07 13:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 12:32 [PATCH] staging: rtl8723bs: hal: fix a multi-line comment in hal_btcoex.c Cen Zhang
2026-10-07 13:12 ` Luka Gejak [this message]
2026-10-07 13:22   ` Cen Zhang

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=d2f64843fa25fe259109aa19b1592d82745e40b9@linux.dev \
    --to=luka.gejak@linux.dev \
    --cc=cenzhang@linux.microsoft.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=guojy.bj@gmail.com \
    --cc=khomenkov@mailbox.org \
    --cc=khushalchitturi@gmail.com \
    --cc=linus.probert@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mokshpanicker.7@gmail.com \
    --cc=qstrydom0@gmail.com \
    --cc=rayfraytech@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.