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 D32451D79A0; Mon, 6 Jan 2025 08:06:48 +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=1736150812; cv=none; b=f+ZmZuL6Weqeqn4Wj0eRKokNxrRngXqZv6yI8YXPVq20aXaVY0eie+GTKvntWazxjoBmFVcp4Vfiy9C/p4H2T5VBqx4bEVKRlQfScTDRXdyKTM5AynOKwfNbeIRMXWb6pOaBfFlGgYWZnf/0YL9aUv5WGkYn654L8oyWlkcYy68= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736150812; c=relaxed/simple; bh=UOjMZRVKEF8pAw+QVhlAmTbkMlSLTFrv44rO0QDuaHI=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=T3dC2XibmBGdIkJyIPEbDWGllWBw42PP7uJC25EqiTziJF3Ay+usHKd7glmDssejVxqozPd+1sbuiYcv3WIncRQi/4K1srIjL8Zwm7aZaT777BNke/FiWKdyh2gT6UNtzreeddAKJfmULK2Ky5RwM9hPLiYfO5yHGrMoIspMu/0= 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=lBSlYloT; 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="lBSlYloT" 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=UOjMZRVKEF8pAw+QVhlAmTbkMlSLTFrv44rO0QDuaHI=; t=1736150810; x=1737360410; b=lBSlYloTtX2e7qVzJsCoI3iCmBY0n5hs76jC1EHEMmN0YVY orXZT/8dxZWBL9fSlNjEWy+ZiykiVEpx44v1lMdyeQP6FlnVZn0cjcXksAYtDQuQzgynyrWGP3Ooy Usdmnie6KopLxPq/GvpVgZXzGKjelskAj6sIqjleshvhUO0gFESOWFm+O/k/qTd7lS6pPAGlToivp epdXbOCll/jaLfdPgTufFC9oz5pE0tcr3OJrk46tQoNOV4I9GPSKYIMEIV2jRtxnos6GmTeoRKqGO izhnp1+5Vk91VPG2BrMoLgzR3yUVmQtygoIDiHa0lwSwuyrdnPfZvzV4/D45DJpg==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.98) (envelope-from ) id 1tUi7e-00000005muW-0BHU; Mon, 06 Jan 2025 09:06:02 +0100 Message-ID: Subject: Re: [PATCH] net: ethernet: toshiba: ps3_gelic_wireless: Remove driver using deprecated API wext From: Johannes Berg To: Arnd Bergmann , Philipp Hortmann , Andrew Lunn , "David S . Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Geoff Levand , Simon Horman , Alexander Lobakin , Netdev , linux-kernel@vger.kernel.org Cc: Kalle Valo , Alexandre Belloni , Claudiu Beznea , Geert Uytterhoeven , Greg Kroah-Hartman , Jeff Johnson , Larry Finger , Nicolas Ferre , Pavel Machek , Stanislaw Gruszka , Gregory Greenman , linuxppc-dev , linux-staging@lists.linux.dev, linux-wireless@vger.kernel.org, Stefan Lippers-Hollmann Date: Mon, 06 Jan 2025 09:06:00 +0100 In-Reply-To: References: <20241224080755.194508-1-philipp.g.hortmann@gmail.com> <39256db9-3d73-4e86-a49b-300dfd670212@gmail.com> <8414fd0c552de87b3471468665f7fc540b9bfa69.camel@sipsolutions.net> 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 Sat, 2025-01-04 at 05:15 +0100, Arnd Bergmann wrote: >=20 > I would assume that once removing CFG80211_WEXT becomes an option, we > can just put the remaining parts of net/wireless/wext-*.c into both > ps3_gelic and ipw2x00, duplicating and then simplifying the > implementation. As far as I can tell, there is very little that is > actually shared between the two anyway. Indeed. Note that net/wireless/wext-{core,proc,priv}.c are not even related to CFG80211_WEXT (wext-{compat,sme}.c are), and just form the core wext code that can be treated completely orthogonal and independent of cfg80211. This driver doesn't even use CFG80211_WEXT code at all. johannes