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 831BAC433F5 for ; Wed, 11 May 2022 19:35:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1347012AbiEKTfP (ORCPT ); Wed, 11 May 2022 15:35:15 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50946 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229633AbiEKTfN (ORCPT ); Wed, 11 May 2022 15:35:13 -0400 Received: from mail.skyhub.de (mail.skyhub.de [5.9.137.197]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E806C177898 for ; Wed, 11 May 2022 12:35:11 -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 712BA1EC0535; Wed, 11 May 2022 21:35:06 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1652297706; 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=B7VXmh66M+2El9UzptpiYafUbsBm6o9pydX/9uOO3yk=; b=naMVL+3QI0M+uWHrRrw4Tv1CFrKKeItd5vbrSLAE2aOwAEu/foCljd+DPxtjL+fhdUrDiM VwHOH4X9fQbC/exGi2o6//8xNSN5KXHMD+UGBfDW1C4qwNxjwBsHFjzDDBguPIU1vJbncY FS/IzxDz2/3YxjjYLzE8WkAUfLvUjKg= Date: Wed, 11 May 2022 21:35:09 +0200 From: Borislav Petkov To: Linus Torvalds Cc: Theodore Ts'o , Thorsten Leemhuis , 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 Wed, May 11, 2022 at 08:55:34AM -0700, Linus Torvalds wrote: > On Wed, May 11, 2022 at 8:50 AM Theodore Ts'o wrote: > > > > I would argue that it should be the patch submitter's responsibility > > to explicitly add a URL to the problem report. > > I agree in the perfect case. > > But in practice, we have a lot more patch submitters than we have > maintainers, and not all "leaf developers" necessarily know how to do > everything. > > So the maintainer should probably expect to fix things up. Not always, > but also not a "the developer should have done this, so I won't do it" > > This isn't so different from the fact that not everybody writes > English proficiently - people do hopefully end up fixing things up as > they get passed onwards. And, in addition, what happens most often in my experience is I constantly get to point submitters to our process documentation - submitting-patches especially - as not a small number of them are not aware of different aspects of the whole patch dance: tags, SOB chains, etc. And the Link tag is no exception here. So yeah, the maintainer is kinda the last one to make sure the patch looks somewhat sane and documents the whole issue so that years from now, it can still be understood what we were fixing there. And I guess important part of that documentation is setting the proper Link so... And as said, yeah, we won't be perfect and catch all cases but at least we can pay attention. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette