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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E9321C433F5 for ; Wed, 11 May 2022 08:37:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243742AbiEKIhn (ORCPT ); Wed, 11 May 2022 04:37:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49606 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235558AbiEKIhk (ORCPT ); Wed, 11 May 2022 04:37:40 -0400 Received: from mail.skyhub.de (mail.skyhub.de [IPv6:2a01:4f8:190:11c2::b:1457]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 116E06830D for ; Wed, 11 May 2022 01:37:38 -0700 (PDT) Received: from zn.tnic (p5de8eeb4.dip0.t-ipconnect.de [93.232.238.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 4CCBD1EC04EC; Wed, 11 May 2022 10:37:33 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1652258253; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=UoVloFQ4Xl9HFnel7GHmF03+TGYLyO7LWlQCnb+R35I=; b=l3dOoSVxhX8OxWdn5IvEm2BlTXW/eeco/jsN6n5am2usrsuXp/1qIrhCmDvfGIDGxdLrSW HoPE4JYoKvvzTBo12ko8GO/V72BQl/ZwD9SaDNlGSV8Ow8com9tCiEy+w7gBmsDSUjcjj0 wqEW2UgtiOLnWs/Gixx0/k7xVWRYdkc= Date: Wed, 11 May 2022 10:37:35 +0200 From: Borislav Petkov To: Thorsten Leemhuis Cc: Linus Torvalds , Thomas Gleixner , Zhangfei Gao , Fenghua Yu , Jean-Philippe Brucker , Jacob Pan , Dave Hansen , Linux Kernel Mailing List , the arch/x86 maintainers Subject: Re: Link: tag and links to submission and reports (was: Re: [GIT pull] core/urgent for v5.18-rc6) Message-ID: References: <165201148069.536527.1960632033331546251.tglx@xen13> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 10, 2022 at 01:27:54PM +0200, Thorsten Leemhuis wrote: > Many thx for reminding people about the tag. FWIW, that's a problem in > a lot or subsystems and makes my regression tracking efforts hard, as my > tracking bot relies on the 'Link:' tag. If it's missing I thus have to > manually search if patches were posted or committed to fix a regression, > which makes the tracking hard and annoying. :-/ Here's my experience with the Link thing: So it is trivial to take the Message-ID and turn it into a link tag and our automation does that. - Now, it is not a problem when that link tag points to a patch which is part of the thread which contains the initial bug report - you just go up-thread. - If the link tag points to a patch which is version N and it is the version which passed all review and gets committed, it is a bit harder to find the previous versions and find the whole discussion how it all arrived at version N. You can search by the Subject, ofc, which, if it hasn't been changed, will give you the previous threads. And so on ... - The problem is when the discussion happened somewhere and the patch got submitted separately. I can't think of a good way to automate that so we have to pay attention and fix the link tag by hand and add the relevant one. And I try to do that when I'm especially awake when applying the patch. So I think we should simply pay attention to making sure the link tags point to the relevant discussion. And we even document that: "If related discussions or any other background information behind the change can be found on the web, add 'Link:' tags pointing to it." so we better follow through with it. :-) -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette