Received: by 10.192.165.148 with SMTP id m20csp4841732imm; Tue, 8 May 2018 15:42:09 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqd25OTr1ZI7oaEASZN+Fme1HjN7738nCVpEFtTUObnyFlPoU3HnDpzK+4RlZeLXw9PvU8Z X-Received: by 2002:a65:4d07:: with SMTP id i7-v6mr20204054pgt.149.1525819329116; Tue, 08 May 2018 15:42:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525819329; cv=none; d=google.com; s=arc-20160816; b=WQNRfgMVWRx3NDk3WQVBUTNnOFfK/X/74sdtuc9kLsVtjBdeNMDtsk/AY3MMAZR/Aa qWFfrTtE+Xl0JTCa+6g8qn/rxJL23PZGwwLqjRZJwEh8NjG3u0m2DKL/5R+JsfmtCk0z RZm4Jie81NpnfcrcpsSzsB6PRGmQxRrhKWGlRxnh2B0caqBM6jGgLAK4TvDQCh/jlog5 +vSoyCllqPr49INQaJdwDj735A5rWfu80aAbsCLu8zAeDnM7QbqynESJsz+mNNXbe+ro lOOdlRhBiOzmEoKhO+h1sAG0/OC3uzluhOD9SeOPTTBMspFulA6cF9dPz3ZS/E1sQgPU Y3fA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :dkim-signature:arc-authentication-results; bh=vlAWbyGtT0VoCkKUj5Elbe2OrNgM+ceAq8dpvj4FFLI=; b=LGfCrybt0Rh5nrNAzAizLeyhyo1AJPMotIwNVZuz7J91jgcSuub6SZTk2hSrOx/6/N 136EVHSJU1IVxlCUc7xTANtpqLiaeXTyms3R5CXjcG3RoUUbFa6qJtnEPq4LB/C+sKu4 fFAICQHaKlcbCsxyYrdqA3u4yRTkAHvhHo4eYmO0MUwKMddlERt0IZp7Wds+47q4rO8j dktO2rxKRSuu/HNkaY4kjmpIFjW8ybhE+k/w/vLJDsD9gBCBl/eumd43dSzTlM1537Ba taq/+1GZMNlIdM9SZTOR/ltaji9sJfBVGD/ZHcDunz0L2ZzNDfyXLLZvDy0DfvBTmcXo 4x0A== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@hansenpartnership.com header.s=20151216 header.b=GCtqioUB; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=hansenpartnership.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c3si22372001pfn.245.2018.05.08.15.41.55; Tue, 08 May 2018 15:42:09 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@hansenpartnership.com header.s=20151216 header.b=GCtqioUB; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=hansenpartnership.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933004AbeEHWlk (ORCPT + 99 others); Tue, 8 May 2018 18:41:40 -0400 Received: from bedivere.hansenpartnership.com ([66.63.167.143]:55060 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755973AbeEHWlj (ORCPT ); Tue, 8 May 2018 18:41:39 -0400 Received: from localhost (localhost [127.0.0.1]) by bedivere.hansenpartnership.com (Postfix) with ESMTP id 76D9B8EE11E; Tue, 8 May 2018 15:41:39 -0700 (PDT) Received: from bedivere.hansenpartnership.com ([127.0.0.1]) by localhost (bedivere.hansenpartnership.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z7sc0dYZwxW1; Tue, 8 May 2018 15:41:39 -0700 (PDT) Received: from [153.66.254.194] (unknown [50.35.65.221]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by bedivere.hansenpartnership.com (Postfix) with ESMTPSA id E0ECD8EE0C7; Tue, 8 May 2018 15:41:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=hansenpartnership.com; s=20151216; t=1525819299; bh=atgn9E+VZm4kLpN73jnDGWHQDTT0G4CJhZFKEwYC+5M=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=GCtqioUBqPjDun0mekkwNAvSrFvLC6AaB8BERUGqOoBchYlrsut8Cfa2yPASJsT4F KAmnCYRpQ38cRmVlCGLkVRXjUDSFpCHPSs+1NgTSvafU+npve/zFbGnJU+5iSWbx9Z 3xRU1nW1/LYIxSATDbCoBTHX3PeEu7gyGMeeD594= Message-ID: <1525819297.13798.3.camel@HansenPartnership.com> Subject: Re: [Ksummit-discuss] bug-introducing patches From: James Bottomley To: Sasha Levin , David Lang Cc: "ksummit-discuss@lists.linuxfoundation.org" , Greg Kroah-Hartman , Linux Kernel Mailing List , "w@1wt.eu" Date: Tue, 08 May 2018 15:41:37 -0700 In-Reply-To: <20180508214339.GE8514@sasha-vm> References: <20180503031000.GC29205@thunk.org> <0276fcda-0385-8f22-dbdb-e063f7ed8bbe@roeck-us.net> <20180503224217.GR2714@sirena.org.uk> <20180503230905.GA98604@atomide.com> <20180508023439.GA8514@sasha-vm> <20180508034820.GE999@thunk.org> <20180508202912.GC8514@sasha-vm> <20180508205505.GD8514@sasha-vm> <20180508214339.GE8514@sasha-vm> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2018-05-08 at 21:43 +0000, Sasha Levin via Ksummit-discuss wrote: > On Tue, May 08, 2018 at 01:59:18PM -0700, David Lang wrote: > > On Tue, 8 May 2018, Sasha Levin wrote: > > > > > There's no one, for example, who picked up vanilla v4.16 and > > > plans to keep using it for a year. > > > > Actually, at a prior job I would do almost exactly that. > > > > I never intended to go a year without updating, but it would happen > > if  nothing came up that was related to the hardware/features I > > was running. > > > > so 'no one uses the Linus kernel is false. > > My point is not that "no one ever uses Linus kernel" but that no one > takes one of those kernels and plans to stick with it for 3 months > until the next one comes up, even if there are updates relevant to > that user.. Actually, I have sometimes done that. My current laptop is running the v4.16 tag now, not because I intended to run it for this long but because I've run into a Round Tuit shortage as far as the -rc candidates go. > Yes, some users will use a .0 release until either Greg releases a > -stable, or until the next -rc is out. > > What I'm trying to say is that there is that the .0 release makes > some people rush poorly tested commits in it even though the .0 > release is not significant in any way. As a milestone, it's extremely significant because it's the cadence from which everything else flows. If we as developers stop taking the -rc cycle seriously, you'll find immediate negative consequences for your stable kernels. And I mean way worse consequences than the odd bad judgment call about a patch that ought not to have gone in right before a Linus release. James