linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
	Wen Gong <quic_wgong@quicinc.com>
Subject: Re: [PATCH] ath11k: enable IEEE80211_HW_SINGLE_SCAN_ON_ALL_BANDS for WCN6855
Date: Wed, 08 Dec 2021 10:12:59 +0100	[thread overview]
Message-ID: <2239044.ZpX2dJDJjJ@ripper> (raw)
In-Reply-To: <463b4075-e98f-d51a-d305-a7adadc8a585@quicinc.com>

[-- Attachment #1: Type: text/plain, Size: 535 bytes --]

On Wednesday, 8 December 2021 09:19:28 CET Wen Gong wrote:
> On 12/8/2021 4:16 PM, Kalle Valo wrote:
> > Wen Gong <quic_wgong@quicinc.com> wrote:
> ...
> > Sven, after your memory corruption fix is this good to take?
> 
> After Sven's fix "ath11k: Fix buffer overflow when scanning with 
> extraie", it will not happen kernel crash.
> 
> But it need Sven's confirm.

Correct, it is not causing any problems anymore when the other fix was applied 
before this change.

Tested-by: Sven Eckelmann <sven@narfation.org>

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-12-08  9:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-29 10:13 [PATCH] ath11k: enable IEEE80211_HW_SINGLE_SCAN_ON_ALL_BANDS for WCN6855 Wen Gong
2021-12-03 14:09 ` Sven Eckelmann
2021-12-06  3:29   ` Wen Gong
2021-12-06  6:56     ` Sven Eckelmann
2021-12-06  7:10       ` Wen Gong
2021-12-06 20:03         ` Sven Eckelmann
2021-12-07  4:35           ` Wen Gong
2021-12-07 14:30             ` Sven Eckelmann
2021-12-08  3:43               ` Wen Gong
2021-12-08  8:16 ` Kalle Valo
2021-12-08  8:19   ` Wen Gong
2021-12-08  9:12     ` Sven Eckelmann [this message]
2021-12-08  9:48       ` Kalle Valo
2021-12-09  7:59 ` Kalle Valo

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=2239044.ZpX2dJDJjJ@ripper \
    --to=sven@narfation.org \
    --cc=ath11k@lists.infradead.org \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_wgong@quicinc.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;
as well as URLs for NNTP newsgroup(s).