From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 97941125CA; Mon, 10 Jul 2023 16:55:21 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id C2EADC433C8; Mon, 10 Jul 2023 16:55:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1689008121; bh=92QedKxPnNh0nRPl+lEtvbAjvdZYrtCfYJAIUUcekKY=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=h9XLo4wu7lBg0N5oGAc759RbT0fju5NSf+fRgRNGKv5KrBtoihuXqUzVUUs7BXkMw ZTgs8YaMAjE28qU+zL1jrVmXhmRFPr41gUPd7zAtoFlb6E4x1xOYNCv9R4K9puEZDv LyRhqxK7QNLgDUVVH3hO4494TbUbjgeLhgDu7ATjo6SP0SMnXbTTjGMmTkAIzkSHCf xfx4unSSVitYNuZF3CC+e1Oqbqyry2HOEdBgxpcRF1BRiUje4z2s8/M+RgkICU4Al+ jjcovcDLDMrNRkfxxoce5M8+MCQFoTtism9s18iuPBMlfK5LQm0/nzMPovRKHYFPh9 eI9H1aqDZYMcA== Date: Mon, 10 Jul 2023 09:55:19 -0700 From: Jakub Kicinski To: "Linux regression tracking (Thorsten Leemhuis)" Cc: Linux regressions mailing list , Andrew Lunn , Ross Maynard , Dave Jones , Bagas Sanjaya , "David S. Miller" , Linux Kernel Mailing List , Linux Networking , Linux USB , Oliver Neukum Subject: Re: 3 more broken Zaurii - SL-5600, A300, C700 Message-ID: <20230710095519.5056c98b@kernel.org> In-Reply-To: References: <7ea9abd8-c35d-d329-f0d4-c8bd220cf691@gmail.com> <50f4c10d-260c-cb98-e7d2-124f5519fa68@gmail.com> <62a9e058-c853-1fcd-5663-e2e001f881e9@bigpond.com> <14fd48c8-3955-c933-ab6f-329e54da090f@bigpond.com> <05a229e8-b0b6-4d29-8561-70d02f6dc31b@lunn.ch> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Sun, 9 Jul 2023 06:36:32 +0200 Linux regression tracking (Thorsten Leemhuis) wrote: > To chime in here: I most agree, but FWIW, it broke more than a decade > ago in v3.0, so maybe this is better suited for net-next. But of course > that up to the -net maintainers. I'm surprised to see you suggest -next for a fix to a user reported bug. IMO it's very firmly net material.