From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 4D297CDB474 for ; Mon, 23 Oct 2023 13:46:12 +0000 (UTC) Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=gOiJyFf5; dkim-atps=neutral Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4SDc0f6xxMz3cX3 for ; Tue, 24 Oct 2023 00:46:10 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=gOiJyFf5; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=kernel.org (client-ip=139.178.84.217; helo=dfw.source.kernel.org; envelope-from=kvalo@kernel.org; receiver=lists.ozlabs.org) Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4SDbzm0zTbz2y1l for ; Tue, 24 Oct 2023 00:45:24 +1100 (AEDT) Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 4702460C52; Mon, 23 Oct 2023 13:45:20 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id CEAA1C433C8; Mon, 23 Oct 2023 13:45:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1698068720; bh=n95Zh41JGelr3O3p08QGkpOeR0lKk99ScJmZPITwFqg=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=gOiJyFf58KDoI1EC+uvC5TLms/dSNPrL8X/ENM0gtmJt8gSaRROYUg8eoYeYA8MmI cgHFl/ELTh3IVs2GHzBmW9CAy0eIjLZr3qgVOFqA9Cripw3UMpcZTeZODLYhC75OrI YJewTnFvm5/SF3SkC9pl3Mcz3sCSy6eO4Q2gJP2eb7sdHNP3F6x0zEAgp/ooPf3eyr b3AoITkafQvIhj4iN7rQutmE1lo1YjZJG1t8l9rZGvnXv1PWwGHgNYCzM1nwspVaiV 6RHuPi/t7XVs9Sem5+IEBnIg28qFeR2VGsqdU+1bKNQ/Pn5mGgLd1Rnr1DlDg4zxJe VR6udzdAzs38w== From: Kalle Valo To: Arnd Bergmann Subject: Re: [PATCH 00/10] Remove obsolete and orphaned wifi drivers References: <20231023131953.2876682-1-arnd@kernel.org> Date: Mon, 23 Oct 2023 16:45:13 +0300 In-Reply-To: <20231023131953.2876682-1-arnd@kernel.org> (Arnd Bergmann's message of "Mon, 23 Oct 2023 15:19:42 +0200") Message-ID: <87v8axzc46.fsf@kernel.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Stanislaw Gruszka , Alexandre Belloni , linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org, Arnd Bergmann , Geoff Levand , Greg Kroah-Hartman , linuxppc-dev , linux-wireless@vger.kernel.org, Claudiu Beznea , Nicolas Ferre , Geert Uytterhoeven , Pavel Machek , Gregory Greenman , Jakub Kicinski , Johannes Berg , Jeff Johnson , "David S . Miller" , linux-arm-kernel@lists.infradead.org, Larry Finger Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" Arnd Bergmann writes: > From: Arnd Bergmann > > As discussed previously, a lot of the older wifi drivers are likely > entirely unused, Though we can't know for sure. > > As suggested by both Greg and Jakub, let's remove the ones that look > are most likely to have no users left and also get in the way of the > wext cleanup. If anyone is still using any of these, we can revert the > driver removal individually. > > I would suggest merging these for net-next after 6.7-rc1 is out Why net-next? I want to take these to wireless-next to avoid any conflicts with other wireless patches. We could take these to wireless-next after we submit the last new features (-next) pull request to v6.7, so most likely already next week. So if anyone has any problems with these speak up now. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches