Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp2340298pxb; Sun, 30 Jan 2022 12:48:38 -0800 (PST) X-Google-Smtp-Source: ABdhPJxGK4dM48gZ6xukmzEe8Qm7LdjYjwv+CxcdGK53VJnvr3QNi5eFmPgqoDClNNCqgd3fVabv X-Received: by 2002:a05:6402:c9b:: with SMTP id cm27mr17884213edb.100.1643575718513; Sun, 30 Jan 2022 12:48:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643575718; cv=none; d=google.com; s=arc-20160816; b=x/SbnYDCwyhjS3zAAB+oGCVouWkyKQkIUlNK/aRXiVbUUCyNgFiS4gV8oja8KmSt/b Z0U7aKfLKD/1kf46HcdI8kw2hr6vfnq/ti2DJsHoxylVPSvahv7DhrpgQY0wNw9kIaf7 bz4Q7FglGDoGiNE/dAPQ5oJo/fmV31TqfFk/NC5KjtgnG9ZCJlMNtOXgEiqfrspEk74h 0+eMsmwt/RWmBbnIZugadilyrd9YF7vNp1NHVF9Il4/mQe/03Ilup2yjMDuFh+bDGW7e MtbGXtsJUryTdX8VnlyWXwtm8sKRxDwkK6+TpvGGXIxBsLJ+r5YS9PUHPFxOPFxClCnh J+0A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:references :mail-followup-to:message-id:subject:cc:to:from:date; bh=5qXP+fCfrtufkiUzSeIEiq+IXb0lOSBdY04Bp26m/Pc=; b=bpsRCuw/vNBUCA/nAHu2u0G7F1hcPQ1eCJJaaueL1JsoGWCVMnEkAWMwZ6r/74ed7Y fsJQRMoGOb9JKk4rE5LlQDDVAlBpGmyI2CJrHZl/bV8tA8Nc/kphIH67A7OK34xweZz6 rcvzqoVp5Pbka8dubHzco+DgSfIoEBbc8+xYwtVTOuBUARYtiSEnVkKHur0xUcep0zUx j3k4za0+Fu4q5N/wehaHg+TQrtviCPShd5ttvAnaOcbihTB+bPD4+yhSvaZvWWgTOzRl a8k+n6xOD5Pwy3fSzu4HBGjI5Hg73pdmWvOY32hDOB4jcXvCsfhmQb0qgy0H/tSIMkPb mLkg== ARC-Authentication-Results: i=1; mx.google.com; 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 4si6149945ejc.29.2022.01.30.12.48.14; Sun, 30 Jan 2022 12:48:38 -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; 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 S1347625AbiA1JcC (ORCPT + 99 others); Fri, 28 Jan 2022 04:32:02 -0500 Received: from mail.thorsis.com ([92.198.35.195]:58922 "EHLO mail.thorsis.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1347617AbiA1Jb6 (ORCPT ); Fri, 28 Jan 2022 04:31:58 -0500 Received: from localhost (localhost [127.0.0.1]) by mail.thorsis.com (Postfix) with ESMTP id 14AFE2984; Fri, 28 Jan 2022 10:31:57 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mail.thorsis.com Received: from mail.thorsis.com ([127.0.0.1]) by localhost (mail.thorsis.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cATs4BJi6wes; Fri, 28 Jan 2022 10:31:57 +0100 (CET) Received: by mail.thorsis.com (Postfix, from userid 109) id E6D7CCE9; Fri, 28 Jan 2022 10:31:56 +0100 (CET) X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RECEIVED,NO_RELAYS, URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Report: * 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was * blocked. See * http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block * for more information. * [URIs: intel.com] * -0.0 NO_RELAYS Informational: message was not relayed via SMTP * -0.0 NO_RECEIVED Informational: message has no Received headers Date: Fri, 28 Jan 2022 10:31:45 +0100 From: Alexander Dahl To: Jonathan Corbet Cc: Andy Shevchenko , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Florian Eckert Subject: Re: [PATCH v1 1/1] docs: process: submitting-patches: Clarify the Reported-by usage Message-ID: Mail-Followup-To: Jonathan Corbet , Andy Shevchenko , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Florian Eckert References: <20220127155334.47154-1-andriy.shevchenko@linux.intel.com> <87o83xrwk9.fsf@meer.lwn.net> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87o83xrwk9.fsf@meer.lwn.net> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, Am Thu, Jan 27, 2022 at 09:08:06AM -0700 schrieb Jonathan Corbet: > 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"? What should be used for feature requests then? Suggested-by? Would it help to mention it here? Greets Alex