All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Luka Gejak <luka.gejak@linux.dev>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH rtw-next v2 1/2] wifi: rtw88: move the bmc high queue decision to tx.c
Date: Sun, 25 Oct 2026 02:49:26 +0000	[thread overview]
Message-ID: <ec4065a1cf2c4d0ea357694a1a73ede8@realtek.com> (raw)
In-Reply-To: <875b4e96891a2bf256ca1805140b57aeccee4aed@linux.dev>

Luka Gejak <luka.gejak@linux.dev> wrote:
> I was thinking, as staging got removed, for 10-ish weeks(until 7.5)
> users of RTL8723BS won't have AP mode. So I was wondering if these two
> patches could pass as fixes into rc2 release(or whatever is the first
> rc into which rtw tree is merged), as this would be DHCP stall fix. To
> elaborate: when this driver was merged it, was exposingAP mode to
> userspace, due to RTW88 doing it globally. Therefore AP mode existed,
> but wasn't working properly. So maybe it's a bit of a stretch, but I
> think it's a valid proposal to send it as a fix into next rc release.

Did you think people use staging driver with AP mode? 

Personally, I want this goes to rtw-next, but if you have strong opinion
that people need this. I can pick them and let it goes to -rc. 

Ping-Ke


  reply	other threads:[~2026-10-25  2:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 12:43 [PATCH rtw-next v2 1/2] wifi: rtw88: move the bmc high queue decision to tx.c Luka Gejak
2026-10-21 12:43 ` [PATCH rtw-next v2 2/2] wifi: rtw88: sdio: limit the high queue to DTIM delivery Luka Gejak
2026-10-22  2:24   ` Ping-Ke Shih
2026-10-22  4:30     ` Luka Gejak
2026-10-22  4:33       ` Ping-Ke Shih
2026-10-22  2:20 ` [PATCH rtw-next v2 1/2] wifi: rtw88: move the bmc high queue decision to tx.c Ping-Ke Shih
2026-10-22  5:11   ` Luka Gejak
2026-10-23 21:34     ` Luka Gejak
2026-10-25  2:49       ` Ping-Ke Shih [this message]
2026-10-25  8:26         ` Luka Gejak
2026-10-27  1:19           ` Ping-Ke Shih
2026-10-27  5:22             ` Luka Gejak

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=ec4065a1cf2c4d0ea357694a1a73ede8@realtek.com \
    --to=pkshih@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luka.gejak@linux.dev \
    /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.