Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Luka Gejak" <luka.gejak@linux.dev>
To: "Ping-Ke Shih" <pkshih@realtek.com>,
	"Carl Quist" <equalizerjr@gmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH rtw-next] wifi: rtw88: 8723d: add iface combination
Date: Sun, 25 Oct 2026 08:29:58 +0000	[thread overview]
Message-ID: <8331a75e3ee92551eaa9256be8329a843d7bc184@linux.dev> (raw)
In-Reply-To: <836925ba243944dbbc74a713d63d74c7@realtek.com>

October 25, 2026 at 3:38 AM, "Ping-Ke Shih" <pkshih@realtek.com> wrote:


> 
> Carl Quist <equalizerjr@gmail.com> wrote:
> 
> > 
> > Would you be fine with sending v2 as it is, with the commit message
> >  stating exactly what was and was not tested? Or would you rather wait
> >  until someone with a sniffer can run your checks?
> > 
> With your tests from user point of view, I think it is okay. That'd be
> good if someone can capture a sniffer and analyze it, but that isn't
> a blocking item to merge this patch. Please follow Luka's suggestions
> to spin v2. 

I can test v2 on rtl8723du and another card as a sniffer if that helps :)

> 
> > 
> > If there is a way to
> >  check any of those points with a single adapter, I am happy to try it.
> > 
> I think no. Driver isn't aware that packets sent by firmware/hardware.
> 
> Ping-Ke
>

      reply	other threads:[~2026-10-25  8:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 21:41 [PATCH rtw-next] wifi: rtw88: 8723d: add iface combination Carl Quist
2026-10-17 10:41 ` Luka Gejak
2026-10-17 12:40   ` Carl Quist
2026-10-19  1:59     ` Ping-Ke Shih
2026-10-23 20:17       ` Carl Quist
2026-10-25  2:38         ` Ping-Ke Shih
2026-10-25  8:29           ` Luka Gejak [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=8331a75e3ee92551eaa9256be8329a843d7bc184@linux.dev \
    --to=luka.gejak@linux.dev \
    --cc=equalizerjr@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.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