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 9206C1E47DB; Fri, 3 Jan 2025 09:32:37 +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=1735896759; cv=none; b=UV3HES+mNkfyJSvEkL7WcU0BwsLCGMyHuNsCjrAotLgHo1w7tZlk49w8smSTMS5ABpdMyPia8lRCGUuc23hyFM4xzdqNoTO/ijysDfcpGx3GOye7XIAjmMD8fRDoG2pieYh9FNfUreJHvTIR/Mk60puWcIj5JjQOW2oSzto6R0I= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1735896759; c=relaxed/simple; bh=ns/LDV0S2a9mmpzFjocIineirzbQRti0e980RrsKsG4=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=KGxgrAcbluqOL3Dh1MPuaZi0LuDN6vwNffbnXOua2wU9INhfsH9Rlxc8roOhDkRcbni5D4e6CJ91VxcrzQdDM79Kjjhi+CM3NalnVxUPWZNdUut1yMPhnOZoXvKN08v02/+sb9guHwyrpqdQxNTWzrEXXhwW47ysDzvnS/kEBX4= 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=L3+R9bOl; 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="L3+R9bOl" 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=ns/LDV0S2a9mmpzFjocIineirzbQRti0e980RrsKsG4=; t=1735896757; x=1737106357; b=L3+R9bOlNJTYB+5VvWLH0RGuT+yEmWwRkbhsY62ENdnGBEM A4FvOrOllAIszTSzpBPhTlKjbHA+TsdKLz/t5aZFQUv3THUv8YYHdD+KZh0fEjAruVwdgn0ng4bRH IeMxv47pGgKJ1KWL+PqbatLtkRBpCrpTaY1yhW6Y1uwaSE3Ncu0Gyg7c5qb7cXhzEsSoSrtP5DoN9 YKLncFVO8iVLA+hu8+YufuTp/wXN8QQi+alFQQXtObf6N3HA9JKabBoXGBefDrnz2obyjlBItEK4c F3fuZVx+7FK+2XkGBKj1O8Liri36afF1ps+xteW5fNNz5CgD9t7p8QDsHf7BXx0Q==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.98) (envelope-from ) id 1tTe2O-00000002St6-2Pxg; Fri, 03 Jan 2025 10:32:12 +0100 Message-ID: Subject: Re: [PATCH] net: ethernet: toshiba: ps3_gelic_wireless: Remove driver using deprecated API wext From: Johannes Berg To: Geert Uytterhoeven , David Woodhouse Cc: Philipp Hortmann , Andrew Lunn , "David S . Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Geoff Levand , Simon Horman , Alexander Lobakin , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Kalle Valo , Alexandre Belloni , Claudiu Beznea , Greg Kroah-Hartman , Jeff Johnson , Larry Finger , Nicolas Ferre , Pavel Machek , Stanislaw Gruszka , linuxppc-dev , linux-staging@lists.linux.dev, linux-wireless@vger.kernel.org, Arnd Bergmann , Stefan Lippers-Hollmann , Christoph Hellwig Date: Fri, 03 Jan 2025 10:32:11 +0100 In-Reply-To: References: <20241224080755.194508-1-philipp.g.hortmann@gmail.com> <39256db9-3d73-4e86-a49b-300dfd670212@gmail.com> <11ae0b7362284d4828021068b05b38a280a9cee5.camel@infradead.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.54.2 (3.54.2-1.fc41) Precedence: bulk X-Mailing-List: linux-staging@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-malware-bazaar: not-scanned On Fri, 2025-01-03 at 10:25 +0100, Geert Uytterhoeven wrote: >=20 > I was also considering it from the side of the wireless access point: > if you have to provide an non-secure access point just for your PS3, It supports WPA2/PSK (~2004) which is plenty secure. It's not "non- secure", it's just "not secure per WPA3 (2018) standard". Many other drivers in tree don't support WPA3 for one reason or the other (mostly lack of management frame protection support.) johannes