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 X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AF1A1C433DB for ; Thu, 18 Feb 2021 14:31:07 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 34A1364EB2 for ; Thu, 18 Feb 2021 14:31:07 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 34A1364EB2 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linuxfoundation.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=7VCAKLF9y6X4IFGNDqN/OLb5UaMjA60YdYKUWzAJyUU=; b=gK3I2Gj6dpC5RPufpeGVG7RMK JJQAnlDMNAonTRvpyfSMg2/s1sVE1roNQ5BrnNvNufzVzsudksf4axbFV8+ObReB1h95uAWs8YZrm fT1Cm+asLsYvtry2XuAOYYJa6GDv0RX5l6+Y7U6vKcaWSX0w+P2KwTCM7wHdy3dfsEuuhtskweXV8 DP4mpJOuragcAzxRpdWjKgISSdmcgc68JzFIphRLeKKsMsY9XxkhvJfBXwh7ri0mV3eFC4Thq6YvJ 7+5m7LgRXCBwB9SFTTn8nJqqdp8LsRCcW1wqD9L8mmrwa3SnGIxVb3sY67MBWSyvrRO2gNvBZHpLd vSSMyrRjQ==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1lCkIw-0006r9-32; Thu, 18 Feb 2021 14:29:18 +0000 Received: from mail.kernel.org ([198.145.29.99]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1lCkIt-0006qj-FU for linux-arm-kernel@lists.infradead.org; Thu, 18 Feb 2021 14:29:16 +0000 Received: by mail.kernel.org (Postfix) with ESMTPSA id D9E0264E76; Thu, 18 Feb 2021 14:29:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1613658554; bh=W/vP5B7kuDrYnokP92ychColA8JdWdOs46EX1GvjWFM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=atkky+PvrUMS2jEIL1tOYbPwGA99pLkmcTrYyIl/FmA9pVjRo3Hpa2ZfORr4qJUdd AMIeDbZjjesr+WO//NH9EDXqzfzNoUJbqnRAN3nZwZqKJ77m4o5b/Tjvj/zirbNRGW gGw/9Rix8+I+QKT2h9rLOVg6gYJtQHIZn2Kzgh5U= Date: Thu, 18 Feb 2021 15:29:11 +0100 From: Greg Kroah-Hartman To: Jari Ruusu Subject: Re: 5.10 LTS Kernel: 2 or 6 years? Message-ID: References: <8cf503db-ac4c-a546-13c0-aac6da5c073b@broadcom.com> <20210218113107.GA12547@1wt.eu> <602E766F.758C74D8@users.sourceforge.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <602E766F.758C74D8@users.sourceforge.net> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210218_092915_616306_3FFCCBB5 X-CRM114-Status: GOOD ( 17.32 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: LKML , BCM Kernel Feedback , Willy Tarreau , Linux ARM , Scott Branden Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Feb 18, 2021 at 04:15:11PM +0200, Jari Ruusu wrote: > Willy Tarreau wrote: > > The only set of fixes that can be trusted are the "official" stable > > kernels, because they are the only ones that are approved by the patches > > authors themselves. Adding more stuff on top of stable kernels is fine > > (and done at your own risk), but randomly dropping stuff from stable > > kernels just because you don't think you need that is totally non-sense > > and must not be done anymore! > > This may be little bit off-topic... but stable kernel.org kernels > can also bit-rot badly because of "selective" backporting... as in > anything that does not apply cleanly gets dropped regardless of > how critical they are. > > I will give you one example: Intel WiFi (iwlwifi) on 4.19.y > kernel.org stable kernels is currently missing many critical > locking fixes. Why has no one asked for the specific upstream commits to be backported if this is the case? > As a result, that in-tree iwlwifi driver causes > erratic behavior to random unrelated processes, and has been doing > so for many months now. My not-so-politically correct opinion is > that in-tree iwlwifi is completely FUBAR unless someone steps up > to do professional quality backport of those locking fixes from > upstream out-of-tree Intel version [1] [2] of the driver. Why does any out-of-tree driver come into play here? What is wrong with the in-kernel code? > For me > only way to get properly working WiFi on my laptop computer is to > compile that Intel out-of-tree version. Sad, but true. Why use 4.19.y on a laptop in the firstplace? That feels very wrong and is not the recommended thing to use the LTS kernels for. thanks, greg k-h _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel