Linux wireless drivers development
 help / color / mirror / Atom feed
From: Luka Gejak <luka.gejak@linux.dev>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	linux-wireless@vger.kernel.org,
	Noah Weinberger <NoahWeinberger2003@proton.me>,
	"pkshih@realtek.com" <pkshih@realtek.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"security@kernel.org" <security@kernel.org>
Subject: Re: [PATCH] wifi: rtw88: sdio: check packet length against remaining RX data
Date: Thu, 12 Nov 2026 10:38:21 +0100	[thread overview]
Message-ID: <9EEA5565-0A03-41F8-91ED-C50D4A632AE3@linux.dev> (raw)
In-Reply-To: <912f7250-d1bb-43cd-8efc-9ad7b0c4f1a9@kernel.org>

On November 12, 2026 10:24:53 AM GMT+01:00, Krzysztof Kozlowski
<krzk@kernel.org> wrote:
>On 10/11/2026 02:34, Luka Gejak wrote:
>> Hi Noah,
>> 
>> Thanks for looking into this. A few comments below.
>> 
>> On November 8, 2026 11:27:09 PM GMT+01:00, Noah Weinberger
>> <NoahWeinberger2003@proton.me> wrote:
>> 
>>> Subject: [PATCH] wifi: rtw88: sdio: check packet length against
>remaining RX data
>> 
>> This doesn't apply to rtw-next, which is the tree rtw88 patches should
>be
>
>This was a report, not a patch whihc can be applied. It's visible by
>lack of DCO.
>
>
>
>Best regards,
>Krzysztof
>

As Noah wrote in private email, emphasis on submission and version of the
patch:

>Hi Luka,

>Thanks for the detailed review >and for pointing me to the >existing fix
>in
>rtw-next. I’ll drop this >version of the patch.

>I appreciate the corrections >and the guidance on the target >tree,
>testing
>and submission format. I’ll >keep those in mind for future >patches.

>Thanks,
>Noah

Best regards,
Luka Gejak

      reply	other threads:[~2026-11-12  9:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-08 22:27 [PATCH] wifi: rtw88: sdio: check packet length against remaining RX data Noah Weinberger
2026-11-10  1:34 ` Luka Gejak
2026-11-12  9:24   ` Krzysztof Kozlowski
2026-11-12  9:38     ` 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=9EEA5565-0A03-41F8-91ED-C50D4A632AE3@linux.dev \
    --to=luka.gejak@linux.dev \
    --cc=NoahWeinberger2003@proton.me \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=security@kernel.org \
    /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