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 CCA8118024; Tue, 25 Mar 2025 16:45:14 +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=1742921116; cv=none; b=LSYjZMmK0wfZ10NINdN7zkJZNXSV1+ZWFFm1pLnoANAv01PEtwQJpRQ9zEERSllFPDcmJ5qW+nSWKtNJEEqcDdPJYze6WZylCGFJ+oDCs1SSpmXvLFHyoqTZ/IfpIcWLIC4bJzd2G7nTCEA2bYqr3WFja51RPYVxBeTqvV36vp8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1742921116; c=relaxed/simple; bh=c2N4XDwsMb8BKswNCl/cHwanunEs4IDpR/UWKP31p4I=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=cBBcc5tZZ1Bn8tBc2C9SfHEofaqsEsK49mYq3a59ht4CforiKred7NUPD5pQukqaGCotN8LpnRvOgZ+aBYWhO5lni+GW0D8zrFYz7+sheD/a5FytWIj8Y6SGrtme9bTzOxCc9+DxKCfPPDY+E4vpn/HVUVrvxihtVQUmHV/zVM0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) 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=HYzOoOuC; arc=none smtp.client-ip=168.119.38.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) 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="HYzOoOuC" 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=c2N4XDwsMb8BKswNCl/cHwanunEs4IDpR/UWKP31p4I=; t=1742921114; x=1744130714; b=HYzOoOuC+VcN24Cop6bZBLginbcGiV+BUiDy01gO3EB2Esq KKNPkIaOecVozQH136AwoAb6cY4rIWHY4wDyhvo0QC9kjg6r6+bIOzgwTJ2l6oVAQqE5+YCq0tlWB J7E06fR+i98mch0ZYbOh4WmcE6OhlgQlpc9O+G1hLLbY4EriiQ2xDsiP5OnRxM35UdjEbQzyn6pfI XrQskSpckQTWHTJLR+aiK5PdvfrwLOtPanN6xZsCfaQvzxgss2c+DsU+q/kIfWv1crj8VpBlNu8+2 +RxjwxyrirLrt5NLUNLMR1viBbpxm7kFEDLoXzrfGQpvwOXeHVeS432SvgySEKPQ==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.98) (envelope-from ) id 1tx7Op-00000005Dqw-3KuS; Tue, 25 Mar 2025 17:45:11 +0100 Message-ID: Subject: Re: [EXT] Re: [PATCH v4 1/2] wifi: mwifiex: Fix premature release of RF calibration data. From: Johannes Berg To: Jeff Chen , Francesco Dolcini Cc: "linux-wireless@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "briannorris@chromium.org" , Pete Hsieh , "s.hauer@pengutronix.de" Date: Tue, 25 Mar 2025 17:45:10 +0100 In-Reply-To: References: <20250220061143.1417420-2-jeff.chen_1@nxp.com> <20250318050739.2239376-2-jeff.chen_1@nxp.com> <20250319162842.GA46894@francesco-nb> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.54.3 (3.54.3-1.fc41) 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, 2025-03-25 at 16:43 +0000, Jeff Chen wrote: >=20 >=20 > I have decided to withdraw the patch. I appreciate your feedback and atte= ntion to detail,=20 > which helped identify this oversight. =20 >=20 This goes for _everyone_ on this thread... I applied this patch a long time ago. Whatever you need to fix, you need to send new patches. And I guess next time I'm not going to apply any patches for mwifiex however innocent they look ... thus making the situation of that driver even worse than it is now. So please get together and form a plan on how to maintain it. johannes