From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sipsolutions.net (s3.sipsolutions.net [168.119.38.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9FE253BD62A for ; Tue, 21 Apr 2026 11:08:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=168.119.38.16 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776769731; cv=none; b=YgwTPZUn9RmSYVSrufgJlJbtscPw+NZ6XXAcGwpGTW0FxWD1gL41OWH2uOacWg1LmdnrIiQAuFzxhSTXdrF0uJ17rAiKe5PxCJLodfXUHzukofzQk4W2aMjwWRbjaquOP7IpZgiBqj633trKrzf5CtQhIWCWMXe+4WAaxW/bcxs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776769731; c=relaxed/simple; bh=W8jRFpBUaQuQW6ou3LHF++dWPa3sR54jkS5sxP4hDp8=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=A9/fr/hw+pvT/nNMJXX/1ZFJRAHu2eovQyRf8wQT+BlIyj8ldTO5WWcdwoRADrMF+qn4qo0jp5Eo9YKmkCvvhNzmPKyLVC4AUYFa5OGS1Ecjox4GE0+dRaarttgVMm7XiHM5uRtDlwHq1a3G0iyka+901E7SVGUb6auGm/PZgwI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=permerror header.from=sipsolutions.net; spf=pass smtp.mailfrom=sipsolutions.net; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b=tK0UNuSF; arc=none smtp.client-ip=168.119.38.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=permerror header.from=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b="tK0UNuSF" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=W8jRFpBUaQuQW6ou3LHF++dWPa3sR54jkS5sxP4hDp8=; t=1776769730; x=1777979330; b=tK0UNuSFv/Q5SAWIZiy7dPwnd1H78EWNZPjM2KScp8oQeCJ 497PndDh1aaHRoB6QwypviSFQdsmgVewTYsKOxNsX3oREmE/7cFfYlbv9AfUyctmh/0GJhuS1WW7J KLnv3udY0ZIJaDy/R1qcfpZ0hSmkTGLMdZVvWR18ac8nRfP3I8VpGfUXlXBuYuWdim5LlO2lfO4e4 n6bi7pPBoypPTB8Qxl7VuMEyvuos3eYvNVIY8mhHzoWdDip/GluoWwNB2TmF70tthBX6yAwW7WUSX yunhua/x2YzCBrw5Vjxu1tixMRQtsHIcCOsAvRwg8xfkbOBuw2jUbZLAPUlEHmXg==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.98.2) (envelope-from ) id 1wF8yF-00000004xH0-3057; Tue, 21 Apr 2026 13:08:47 +0200 Message-ID: <152dc405d288d6a8cb3cb695362e00b6319102e3.camel@sipsolutions.net> Subject: Re: [PATCH v3] wifi: rtw89: add bounds check on firmware mac_id in link lookup From: Johannes Berg To: Tristan Madani , Ping-Ke Shih Cc: linux-wireless@vger.kernel.org, Tristan Madani Date: Tue, 21 Apr 2026 13:08:45 +0200 In-Reply-To: <5160c46cda019dee1a01406fbd13cc0b9b02b3e2.camel@sipsolutions.net> References: <20260421110133.2957818-1-tristmd@gmail.com> (sfid-20260421_130137_392604_8BC916E6) <5160c46cda019dee1a01406fbd13cc0b9b02b3e2.camel@sipsolutions.net> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.58.3 (3.58.3-1.fc43) Precedence: bulk X-Mailing-List: linux-wireless@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-malware-bazaar: not-scanned On Tue, 2026-04-21 at 13:05 +0200, Johannes Berg wrote: >=20 > Please stop sending patches until you've figured out how to generate > patches that can actually (and reproducibly) be *applied*. FWIW, I've just dropped *all* of your wireless related patches except three that provably worked, you can see it here: https://patchwork.kernel.org/project/linux-wireless/list/?submitter=3D22141= 1&state=3D* Feel free to resend after you figure out how your sending email path has (not even subtly) corrupted most of your patches. johannes