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 6E801C6FA8E for ; Fri, 3 Mar 2023 02:10:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229639AbjCCCKR (ORCPT ); Thu, 2 Mar 2023 21:10:17 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44586 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229437AbjCCCKO (ORCPT ); Thu, 2 Mar 2023 21:10:14 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2B9A8222D7 for ; Thu, 2 Mar 2023 18:10:13 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id A1B0461700 for ; Fri, 3 Mar 2023 02:10:12 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8E710C433D2; Fri, 3 Mar 2023 02:10:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1677809412; bh=CXprjgttjcNhTZRdnnWpGCKK5+rU8482L6ioskIdys0=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=vxcWv0/WZvAi32V5w0khxosgYuH3j5vIIicPgQ2GfYOB17I42nEybfV7qnSgmAylw VvL5CiQuD2qX6slNl4DCbeuhgTBNdCJxgzENXPjwTA33ktdtJh/PrmD/z2g5CM/8Mh QrUDA/jaTgc5It7Bhg1Gzy0NnkUlln09En//m6zM= Date: Thu, 2 Mar 2023 18:10:10 -0800 From: Andrew Morton To: Thorsten Leemhuis Cc: Dmitry Vyukov , Jakub Kicinski , Joe Perches , Andy Whitcroft , Dwaipayan Ray , Lukas Bulwahn , Kai =?ISO-8859-1?Q?Wasserb=E4ch?= , linux-kernel@vger.kernel.org, Aleksandr Nogikh , Taras Madan , syzkaller , Theodore Ts'o Subject: Re: [PATCH v4 2/3] checkpatch: warn when Reported-by: is not followed by Link: Message-Id: <20230302181010.859456e24e8aaf0990b0dead@linux-foundation.org> In-Reply-To: <3275c17f-1a62-4e4a-4a5b-06b34098f8d2@leemhuis.info> References: <20230301204602.5e9bf3c0@kernel.org> <20230301214023.610a9feb@kernel.org> <17fdf6f1-60ab-bfde-afc8-5afef6cc797b@leemhuis.info> <3275c17f-1a62-4e4a-4a5b-06b34098f8d2@leemhuis.info> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2 Mar 2023 10:48:22 +0100 Thorsten Leemhuis wrote: > > We can parse out our hash from any tag, but the problem is that the > > current email api we use, does not allow to specify Message-ID before > > sending, so we don't know it when generating the text. > > We don't even know it after sending, the API is super simple: > > https://pkg.go.dev/google.golang.org/appengine/mail > > So we don't know what the lore link will be... > > That's... unfortunate, as from my understanding of things that would be > the most important "Link:" to have in any patches that fix issues report > by syzbot. But well, that's how it is for now. In that case I'd vote for > this: > > Reported-by: syzbot@syzkaller.appspotmail.com > Link: https://syzkaller.appspot.com/b/cafecafecaca0cafecafe As you previously mentioned, patch preparers should also include the lore link so any followup discussion is easily located.