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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3E76EC433F5 for ; Mon, 1 Nov 2021 16:19:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1BEEA6113D for ; Mon, 1 Nov 2021 16:19:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232697AbhKAQWa (ORCPT ); Mon, 1 Nov 2021 12:22:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53320 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232683AbhKAQW2 (ORCPT ); Mon, 1 Nov 2021 12:22:28 -0400 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8234::]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C74BBC061714 for ; Mon, 1 Nov 2021 09:19:54 -0700 (PDT) Received: from ip4d173d4a.dynamic.kabel-deutschland.de ([77.23.61.74] helo=[192.168.66.200]); authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1mha2K-0001qw-T3; Mon, 01 Nov 2021 17:19:52 +0100 Message-ID: Date: Mon, 1 Nov 2021 17:19:50 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.2.0 Subject: Re: Thorsten is tracking regression again and could need a little help (was: Re: Linux 5.15) Content-Language: en-BS To: Greg KH Cc: Linus Torvalds , Linux Kernel Mailing List , "regressions@lists.linux.dev" References: From: Thorsten Leemhuis In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1635783594;c3773e77; X-HE-SMSGID: 1mha2K-0001qw-T3 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01.11.21 16:27, Greg KH wrote: > On Mon, Nov 01, 2021 at 02:34:21PM +0100, Thorsten Leemhuis wrote: >> On 01.11.21 14:03, Greg KH wrote: >>> On Mon, Nov 01, 2021 at 01:44:01PM +0100, Thorsten Leemhuis wrote: >>>> On 01.11.21 13:33, Greg KH wrote: >>>>> On Mon, Nov 01, 2021 at 05:49:40AM +0100, Thorsten Leemhuis wrote: >>>>>> example by simply forwarding the mail to regressions@leemhuis.info or >>>>>> CCing that address on a reply. I'll handle everything else then and tell >>>>>> regzbot about it. But if you feel adventurous, you can also skip me as >>>>>> the man-in-the-middle and tell the bot directly. To do that, just send a >>>>>> reply to the report to the regressions mailing list >>>>>> (regressions@lists.linux.dev) either directly or by CCing it on a reply >>>>>> you would have written anyway; when doing so, place something like >>>>>> '#regzbot ^introduced v5.15..' (separated by blank lines) somewhere in >>>>>> the text, as outlined in regzbot's 'getting started guide' or its >>>>>> reference documentation: >>>>>> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md >>>>>> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md >>>>>> >>>>>> That's it, regzbot then on its next run will add the report to the list >>>>>> of tracked regression. I'll keep an eye on things and try to fix any >>>>>> problems I notice, as there likely will be a few. But then doesn't need >>>>>> to bother you. >>>>>> >>>>>> There is one thing that would really help: if one or two subsystem >>>>>> maintainers could give regzbot a shot for all the regression reports >>>>>> they get, even for easy fixes, as the bot really needs something to chew >>>>>> on. Any volunteers? >>>>> >>>>> I'll try it for the USB subsystem this merge cycle. >>>> >>>> That will be a great help, many thx. >>>> >>>>> Do you want a bug >>>>> report email redirected to that address or will a simple forward work >>>>> well enough? >>>> >>>> Redirecting will make it a little easier for me, but a simple forward is >>>> fine, too. >>> >>> Ok, I did that now for a USB bug report, hopefully that worked. If not, >>> I can forward it on. >> >> Got it, but I could need some advice on it if you have a minute. >> >> Does that report really look like a regression from your point of view? >> The part "The code has been this way in the kernel for a very long time, >> which suggests that it has been working, [...]" sounds like it is, but >> OTOH it's quite vague. > > Later in the thread it was determined that this is a regression that > showed up in the 3.4 kernel release and the commit id was referenced. Hah, stupid me, sorry, should have looked closer myself, thx for the pointer. >> I'm asking, because with my regression tracking work and regzbot I focus >> on regressions and ignore things that were always broken, as I (at least >> for now) don't want it to become yet another bug tracker (and I guess I >> would quickly drown in bugs as well). > > I agree, this shouldn't be a bug tracker, sorry, I shouldn't have > started this with a report of a really old issue, but it's all I found > at short notice :) No worries, I'm glad I get something to test regzbot better :-D > I've found another report of a regression that is newer for USB and > bounced it to you as well. Hopefully that is a bit easier to track. Many thx, much appreciated! Ciao, Thorsten