Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp3091114rwb; Mon, 3 Oct 2022 09:31:21 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7HxG2N1XhUB0sErW8gjNTaeAbt4PWown9V3qT6HekBO0yUPmmavhMvqnoEvrT/4ITqj9dn X-Received: by 2002:a17:903:24f:b0:178:bf4f:fc7c with SMTP id j15-20020a170903024f00b00178bf4ffc7cmr22978390plh.124.1664814680951; Mon, 03 Oct 2022 09:31:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1664814680; cv=none; d=google.com; s=arc-20160816; b=K+bvB9ZHnDzEU5JSlSJ5rU/qd3KaFSlt5fwVIQrJywlyzfIMnF9gKrh7FF5zfLSR/A z8wrVTuEm+BfTpwVIlnpi/VouHg0bYizwd1Trw7A2dn5wfo3W6dYnsCB8vn5vPe/+/yy eFDA1Isn6KKXE3fj+JCLGkqU2stkwFBCjkLczrjU7e1ieG/8J25tJYWcDAl8ELr0TPW5 mLxQLRftYEsQk7E6iWDLpCfQohTRDoNgD8QBUwANBaG3azK9T2DTDATNJtw5huGpPBqA b1IQHvUkCFFVBjmmZ0PoVFJHgYKQPSSL3dBh1DhnjQHlhbSAHvyzxcBeiNO4DatZHmBm fjkQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=5WZVwcwHOA9+yrjXBv3R/Jf+OrtQndenqIFp9tSl3z8=; b=GHTl6uMripERzUdZ5O073Gf1L5KtoVdaGVO1fBvMeFmlqKThk/TTzvj4PlVppsqbIO Kxqn3IebwMVyC+jzH/8jbkgVP8gjfZ3W/UFQyx0LGxqu74dPcvujzzC2ZXLurSV99fnj MGFGmq2pPol8t5iQcesy65uouD6+M+pwG8bdlsKh9oJFjJWe4HtA/fq7Eymy7XYHXHiM AYY7CsCZrRtO8ak0erCxav96+BTMfkj6GfipGNL9GSb4jhu5fDinna3cCdnDfddM8ycd 9FgImdcwOb2LTGNAFwyrB0v1SSlThPeHnAxX+zT16kEqSsNWAMxQanhxq+VFnOR4IKzN YJLA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass (test mode) header.i=@ideasonboard.com header.s=mail header.b=IeCiAmBw; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id y6-20020a17090a154600b00209a3e49f63si270104pja.94.2022.10.03.09.31.08; Mon, 03 Oct 2022 09:31:20 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass (test mode) header.i=@ideasonboard.com header.s=mail header.b=IeCiAmBw; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229488AbiJCP7a (ORCPT + 99 others); Mon, 3 Oct 2022 11:59:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57238 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229495AbiJCP72 (ORCPT ); Mon, 3 Oct 2022 11:59:28 -0400 Received: from perceval.ideasonboard.com (perceval.ideasonboard.com [IPv6:2001:4b98:dc2:55:216:3eff:fef7:d647]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B0EB92DABA; Mon, 3 Oct 2022 08:59:27 -0700 (PDT) Received: from pendragon.ideasonboard.com (62-78-145-57.bb.dnainternet.fi [62.78.145.57]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id B5198440; Mon, 3 Oct 2022 17:59:24 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1664812764; bh=lUz5Lq9T37UC12wd8MViI0mlNQ7LoqI2XtH8x6p4eWM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=IeCiAmBwYWJc7NU3g6vgKC/UNvA4IuV8tjyMS9jqvhFoNaDhZOlEthzwIe6SaM4hG +Y9Oyp3MzyCSeb8M5zTwfKcnxiw7FJgOdOdhPR0+hFVKwW20C5KX432jZaPEDe2mMP Ul0D9nwX/AQRKh17ZlV8qi4mtkyaxdRYLewCyHmM= Date: Mon, 3 Oct 2022 18:59:22 +0300 From: Laurent Pinchart To: Steven Rostedt Cc: Thorsten Leemhuis , Slade Watkins , Konstantin Ryabitsev , "Artem S. Tashkinov" , workflows@vger.kernel.org, LKML , Greg Kroah-Hartman , Linus Torvalds , "regressions@lists.linux.dev" , ksummit@lists.linux.dev Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues" Message-ID: References: <05d149a0-e3de-8b09-ecc0-3ea73e080be3@leemhuis.info> <63a8403d-b937-f870-3a9e-f92232d5306c@leemhuis.info> <534EB870-3AAE-4986-95F3-0E9AD9FCE45B@sladewatkins.net> <20221003112605.4d5ec4e9@gandalf.local.home> <20221003115102.35bff30e@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20221003115102.35bff30e@gandalf.local.home> X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 03, 2022 at 11:51:02AM -0400, Steven Rostedt wrote: > On Mon, 3 Oct 2022 18:44:45 +0300 Laurent Pinchart wrote: > > > > The sad part is that most people that are going to report a bug is not > > > going to read a full document to figure out how to do it. Usually when > > > someone hits a bug, they are doing something else. And it's a burden to > > > report it. Obviously, they want it to be fixed, but it's viewed as a favor > > > to the developer and not the user to get it fixed, as it's likely seen as a > > > mistake by the developer that the bug exists in the first place. > > > > It really depends on how badly the bug affects the reporter. I'm sure > > that a bug that prevents GPU or audio from working alone on a shiny > > brand new laptop will see lots of pings. A side issue noticed by the > > user that wouldn't really affect them is more likely to end up in a > > blackhole. I recently faced issues with a display controller. I sent > > patches for the problems affecting my use case, and only notified the > > maintainer for the other issues. Those have been "added to their todo > > list (TM)". But is that really a problem ? If I'm not affected and > > neither is the maintainer, there's likely better use of their time, at > > least until a user who is really affected by the problem shows up. > > I guess that's the main question. If we see hundreds of bugzilla reports > ignored, are they the one offs that nobody really cares about, or are they > the ones where it's preventing someone from using their new laptop properly? > > Sometimes, even if it prevents a laptop from working properly, it could be > ignored if a workaround is in place. Like just buying an external webcam if > you can't get the internal one working. That's an interesting example. https://lwn.net/Articles/904776/ shows how it made lots of users *very* unhappy. -- Regards, Laurent Pinchart