Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp372861pxb; Fri, 28 Jan 2022 00:41:42 -0800 (PST) X-Google-Smtp-Source: ABdhPJxLzF5LUnj4De2mDwohbT6OnCPO5gi/Nu3KQDvuhIf5tkCTHyzi/FxI2FNp1CcW3zHAx3A8 X-Received: by 2002:a17:902:b40b:: with SMTP id x11mr2846333plr.75.1643359302216; Fri, 28 Jan 2022 00:41:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643359302; cv=none; d=google.com; s=arc-20160816; b=Q6aPgGgrgR59CpSY7g/TRypAQZNRqwrOh8x5ZiHadWHHrqtcR1HsYE0cuDt6qc9Xcf Uu+QdX4LZY8+V6Xpz+apeGetBxbvkQbh0X5SuJpygvy7Q1IWLbqOJv+Dg2RrZv3foZ1B vebHK0MEjzrZOXz7GHro+02FOwYFzEp8YEP719jcAkDwHhSNNdDAWd5dl2qu/r1Mk7W2 5uQ+Ff5gmU+6EATyQGbXa+pk++BH0/yr19/Xccyuk09Vbu+qjwP/baWUdME9SOOMXZ9P rjsG7EYlACkdSUj5hmJWuTMtTJmPokc0n1lwunMmvgkL/bkYQsu0b4meB5h3NiXOqTQv HVBw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:dkim-signature:dkim-filter; bh=rQeVCu4PDNsyGpc74Exoe0ByVIF33X+J4U9OePlxRCM=; b=AgNk5mBZL/BTQFG8kuvMPeDabD15sSbS063mgD9qj3qp80hvcnLCSFzGbIyHPv0uCC ijeCOMz9iakOB3YTlYEzGKj9cB4V5aT7JkZSjMqTrkxnLIndGjtTZCkg7aRQwtp1O8TK /XZXwCLRFQfgKPw5iLKIRV1efuvtJ2T4fYSjBEw1ulDiwip15++LlRMWKWWesQUwAI/b VfRYf7AxgpoPujPe5Vc+SuS7n9Z+rETAafiYdLRw2xQFOANlMC669Z0XiBLT+Lv/S+3N e9ucniuLm0awPSaF+QsMULdOrnyVdBr+jvUvBpi33qcBuL/tYBh487SXyvdVRVvy8E5X aw4w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lwn.net header.s=20201203 header.b=OzgaTzFZ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d187si4645786pgc.678.2022.01.28.00.41.29; Fri, 28 Jan 2022 00:41:42 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@lwn.net header.s=20201203 header.b=OzgaTzFZ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238456AbiA0QHg (ORCPT + 99 others); Thu, 27 Jan 2022 11:07:36 -0500 Received: from ms.lwn.net ([45.79.88.28]:52000 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230464AbiA0QHg (ORCPT ); Thu, 27 Jan 2022 11:07:36 -0500 Received: from localhost (unknown [IPv6:2601:281:8300:104d::5f6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id C202F2D5; Thu, 27 Jan 2022 16:07:35 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 ms.lwn.net C202F2D5 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lwn.net; s=20201203; t=1643299655; bh=rQeVCu4PDNsyGpc74Exoe0ByVIF33X+J4U9OePlxRCM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=OzgaTzFZPZFjL0IYa7oQO5S4uncY9TYHSkGRSLC4qLx1bVUT8GkSg7+P96uadNkL9 AE7u199u8VUztM0ND1vDVqGRbfPUYtT/9AcdHG+39ZgL0WiZgn/x6Q5nmVIrw9bULx kugK7lt6LvXlLjMqlOadoARb7YHIk7Kjui78jJ7p1DOi0H0JsXp9XLYhxRZrN1Va1V VVkBFZHigc8Q+D+Ob0nJlucR9nQzKVQ520/jrz1mWuwsyAgJqEf6GQsi9MSBXibmeK DGE0WvHigUXjT14eIraZJRAG21/77byQkExAtSNRyBo2psVI4j2JdVKeBkufVFYL+n t4YpsSs30er5A== From: Jonathan Corbet To: Andy Shevchenko , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Andy Shevchenko , Florian Eckert Subject: Re: [PATCH v1 1/1] docs: process: submitting-patches: Clarify the Reported-by usage In-Reply-To: <20220127155334.47154-1-andriy.shevchenko@linux.intel.com> References: <20220127155334.47154-1-andriy.shevchenko@linux.intel.com> Date: Thu, 27 Jan 2022 09:08:06 -0700 Message-ID: <87o83xrwk9.fsf@meer.lwn.net> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Andy Shevchenko writes: > It's unclear from "Submitting Patches" documentation that Reported-by > is not supposed to be used against new features. (It's more clear > in the section 5.4 "Patch formatting and changelogs" of the "A guide > to the Kernel Development Process", where it suggests that change > should fix something existing in the kernel. Clarify the Reported-by > usage in the "Submitting Patches". > > Reported-by: Florian Eckert You're sure this added documentation isn't a new feature that shouldn't have a Reported-by? :) > Signed-off-by: Andy Shevchenko > --- > Documentation/process/submitting-patches.rst | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst > index 31ea120ce531..24c1a5565385 100644 > --- a/Documentation/process/submitting-patches.rst > +++ b/Documentation/process/submitting-patches.rst > @@ -495,7 +495,8 @@ Using Reported-by:, Tested-by:, Reviewed-by:, Suggested-by: and Fixes: > The Reported-by tag gives credit to people who find bugs and report them and it > hopefully inspires them to help us again in the future. Please note that if > the bug was reported in private, then ask for permission first before using the > -Reported-by tag. > +Reported-by tag. A new feature can't be reported since there is no code in the > +kernel to fix. How about instead something like "Reported-by is intended for bugs; please do not use it to credit feature requests"? (i.e. I want the shed in green :) Thanks, jon