Linux wireless drivers development
 help / color / mirror / Atom feed
From: Luka Gejak <luka.gejak@linux.dev>
To: Ping-Ke Shih <pkshih@realtek.com>,
	Zeshan Ahmed Nobin <zeshanahmednobin@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Kalle Valo <kvalo@kernel.org>
Subject: RE: [PATCH rtw-next v2 0/2] wifi: rtw88: 8822c: check register values in cck_pd_set
Date: Mon, 09 Nov 2026 07:06:23 +0100	[thread overview]
Message-ID: <32B31B48-2A08-4A09-8D19-39FF49FE7306@linux.dev> (raw)
In-Reply-To: <b91cf87116d04aa7b3d1758ff58fab1f@realtek.com>

On November 9, 2026 3:10:10 AM GMT+01:00, Ping-Ke Shih <pkshih@realtek.com>
wrote:
>
>
>Luka Gejak <luka.gejak@linux.dev> wrote:
>> November 8, 2026 at 8:32 AM, "Luka Gejak" <luka.gejak@linux.dev> wrote:
>> 
>> Typo:
>> > Do you mind resending this series and putting
>linux-kernel.vger.kernel.org
>> > in the CC as well.
>> 
>> linux-kernel@vger.kernel.org
>
>Why is it required for wireless patches?
>
>
Wireless list is bugged out and nothing newer than 2026-11-06 15:46
UTC is appearing on it.
Best regards,
Luka Gejak

  reply	other threads:[~2026-11-09  6:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07 18:34 [PATCH rtw-next v2 0/2] wifi: rtw88: 8822c: check register values in cck_pd_set Zeshan Ahmed Nobin
2026-11-07 18:34 ` [PATCH rtw-next v2 1/2] wifi: rtw88: 8822c: fix out-of-bounds access " Zeshan Ahmed Nobin
2026-11-07 18:34 ` [PATCH rtw-next v2 2/2] wifi: rtw88: 8822c: ignore nrx values without CCK PD registers Zeshan Ahmed Nobin
2026-11-08  7:32 ` [PATCH rtw-next v2 0/2] wifi: rtw88: 8822c: check register values in cck_pd_set Luka Gejak
2026-11-08  7:34   ` Luka Gejak
2026-11-09  2:10     ` Ping-Ke Shih
2026-11-09  6:06       ` Luka Gejak [this message]
2026-11-09  6:14         ` Ping-Ke Shih

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=32B31B48-2A08-4A09-8D19-39FF49FE7306@linux.dev \
    --to=luka.gejak@linux.dev \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=zeshanahmednobin@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