Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp620555rwb; Wed, 28 Sep 2022 07:08:32 -0700 (PDT) X-Google-Smtp-Source: AMsMyM5nA7H7LH2AHruDI0mxPW6gxxamVJdHog9rE9MsCPsTMsjTKRU9MDKOPbouBph/xGCx2ruG X-Received: by 2002:a17:90a:fd8c:b0:200:8cf9:63f4 with SMTP id cx12-20020a17090afd8c00b002008cf963f4mr10616641pjb.201.1664374111838; Wed, 28 Sep 2022 07:08:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1664374111; cv=none; d=google.com; s=arc-20160816; b=Ie0efF5PTVKHtJI1ITRRIdZDM0keBSLfScoZHpmyr+eiHiroHSOSrPKmywi7chA8gO fRBuTEBgwoojZQNvnosriHSkAVeBwAnRYJqBvczvdhCz9ozepggpxj/lcTU+rq1fb2IY 9HoTPpzKCE+M0pOMoafnXL994swAj9NYn3V10S66jCZ1b8Bhb9BRs0cHpz5EbI0S2aSX 8uVvPOtGpoAfUl9lqD9I2vDZj+4fW9ExHim7ml/KPxuyvY9R+Kncw2fEe3any4Dv9exk vGPYqKHQCeMD3HtwEfZK6s+uWgqykXvpBqAUUfzo++z3+mLNbWWJ5ie5bTsy0sXTLQIi 5nEw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=uazPUqM9cQQq7IKK4vR3IO2McCe6gP8Yc+8pSNVXXzU=; b=VG0b2xpP5OjRdMwyIlkvLpVctKqBj4IqiLLRLwabSrqyEU/O7n28L6bQAjh9h0EKXL rINFAyZXRsuCBp6GOY2mhHcxgADL0Y3JjK1PnpwtpJmLecmSupLOpAJM1e1NiPHjg0kB z6glGI2pkaCTHvENZbok0uMING93yd7j5o83wwewA6PN/dMRKm2+r8b2CNhoNMZQ6N8q gtEtmiTOEBgik4L0vWEaxwj3VTXaXClmnLD7EDuROHx7C1zE6NvmbVauNsYZo44VaIGy u3ptZFs6reEeSQLaNSs0J82fe22JQVq+8BSW6QsLsRt0rGVFoI8HI55LY8YzvNx/pIpF wLpw== ARC-Authentication-Results: i=1; mx.google.com; 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 h128-20020a625386000000b0052e677b7056si2509203pfb.279.2022.09.28.07.08.19; Wed, 28 Sep 2022 07:08:31 -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; 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 S234178AbiI1NkN (ORCPT + 99 others); Wed, 28 Sep 2022 09:40:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46426 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234212AbiI1Njq (ORCPT ); Wed, 28 Sep 2022 09:39:46 -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 AC48E5A2F9; Wed, 28 Sep 2022 06:39:44 -0700 (PDT) Received: from ip4d147bae.dynamic.kabel-deutschland.de ([77.20.123.174] helo=truhe.fritz.box); authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1odXHp-0006WL-N5; Wed, 28 Sep 2022 15:39:41 +0200 From: Thorsten Leemhuis To: Jonathan Corbet Cc: linux-doc@vger.kernel.org, Linux Kernel Mailing List Subject: [PATCH v1] docs: process/5.Posting.rst: clarify use of Reported-by: tag Date: Wed, 28 Sep 2022 15:39:40 +0200 Message-Id: <2fc7162dfb76e04da5ea903c9c170d913e735dad.1664372256.git.linux@leemhuis.info> X-Mailer: git-send-email 2.37.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-bounce-key: webpack.hosteurope.de;linux@leemhuis.info;1664372384;24a868f7; X-HE-SMSGID: 1odXHp-0006WL-N5 X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, 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 Bring the description on when to use the Reported-by: tag found in Documentation/process/5.Posting.rst more in line with the description in Documentation/process/submitting-patches.rst: before this change the two were contradicting each other, as the latter is way more permissive and only states '[...] if the bug was reported in private, then ask for permission first before using the Reported-by tag.' Signed-off-by: Thorsten Leemhuis --- Hi! I noticed some confusion in our development community on when to use the Reported-by: tag. Some of this apparently is caused by the inconsistency fixed in this patch. Ciao, Thorsten --- Documentation/process/5.Posting.rst | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Documentation/process/5.Posting.rst b/Documentation/process/5.Posting.rst index 906235c11c24..d87f1fee4cbc 100644 --- a/Documentation/process/5.Posting.rst +++ b/Documentation/process/5.Posting.rst @@ -256,8 +256,10 @@ The tags in common use are: - Cc: the named person received a copy of the patch and had the opportunity to comment on it. -Be careful in the addition of tags to your patches: only Cc: is appropriate -for addition without the explicit permission of the person named. +Be careful in the addition of tags to your patches, as only Cc: is appropriate +for addition without the explicit permission of the person named; using +Reported-by: is fine most of the time as well, but ask for permission if +the bug was reported in private. Sending the patch base-commit: 3ef859a4f6c97253b75eb53d259b7789fb92d875 -- 2.37.3