Message ID | 20230316082034.14191-1-bagasdotme@gmail.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:604a:0:0:0:0:0 with SMTP id j10csp363277wrt; Thu, 16 Mar 2023 01:53:16 -0700 (PDT) X-Google-Smtp-Source: AK7set9xCdtVPQzkQblCCd7vZjYGyzLPoDGJXZ3g638tc0dbndawdA4R0kp+VMucKVMqFi7UuN1/ X-Received: by 2002:a17:902:e0c4:b0:19c:e05a:ea6 with SMTP id e4-20020a170902e0c400b0019ce05a0ea6mr1709498pla.56.1678956795915; Thu, 16 Mar 2023 01:53:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1678956795; cv=none; d=google.com; s=arc-20160816; b=F/2oqAm/tDeCms8h27oTQMKyoI9+0UxEjDf5j5W6VJKY6Zk6i93QWa7yWkX/lHB7qa iLgiD9iuFjYVWDND4yzwNqV0HzrkvB6Kw3eqNtwowDzb2tQCC8Voge6lTrisnCY1vXgw PVw/q3WTUclvoOGPAdCAKhlt/9AF4QZH3O5jRDduql/dFNx8co35/d5lGtYydjNhmWz8 Ib8JX5RUoVntq4Qvl5MKBftYahp95jRPN8ShxB6+eFxw40J6en9X+9REheV7k7Uf+EOD VNcLiPB2Ra4qaMDA4xMxBfxtjHzC3GQRO2boWo3BiW0MrMKX4GXzeCGo0fjxgqfRqZqv ULvA== 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:dkim-signature; bh=kTCGCOoDJTxIEcj5bZXvO/9uvZr0Hq0Yj/9WZl7ZrcM=; b=D2MggFqwpLwxNUJpWhnsyjjWyqn5gWlAH5E7OibO0g2yzcEK1xiUlphfOkESPz6V4q U5J/DVk7sfxHo87CL6U+dQQwzIpszzUADGCyw57cY/EiVK/gP3PV0n7v8uD92wBXiUXW 4KF3tRlmDEKJk4PyycMDyNfy0Tv3Pb1m1WHsImxc/rZgAV0T2FzIJqOoGD/D180+51MX LelkFJWnJV8VTbLZ3FmJP61xWwCE8MFJStFraxvoXIlZjuH3gr19oTVhE5g10aawe7m0 c6nbcmY9Gax/yxVQSnfCGFLHyFan26eifyniLtVeE+cDDMzNhnMiBwjyQNo9OTOPvljs e9jQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=LYfWJ2Im; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id ju9-20020a170903428900b0019f38df24cbsi7548096plb.161.2023.03.16.01.53.03; Thu, 16 Mar 2023 01:53:15 -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; dkim=pass header.i=@gmail.com header.s=20210112 header.b=LYfWJ2Im; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229799AbjCPIV0 (ORCPT <rfc822;pwkd43@gmail.com> + 99 others); Thu, 16 Mar 2023 04:21:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50298 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229616AbjCPIVT (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Thu, 16 Mar 2023 04:21:19 -0400 Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E67C147437; Thu, 16 Mar 2023 01:20:59 -0700 (PDT) Received: by mail-pl1-x636.google.com with SMTP id c18so882657ple.11; Thu, 16 Mar 2023 01:20:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678954843; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=kTCGCOoDJTxIEcj5bZXvO/9uvZr0Hq0Yj/9WZl7ZrcM=; b=LYfWJ2Im6lx8NmcnsrXeODvku8gcbTvbt9carygzY+TwIPeiu1A33V+kNAb7EPte92 0hbI0dZBniexpxPcHjkIDK+v0cSGSbsJPuqDIldmeutDJ4zpaXZUkZv3Mp+dHKmywp/p h04H5tfWUP2FdZbfJsbzDWlw9KQTuCgpFqergXH9QpouFFeK1VJDvmb2ZgZCajm5708j 4V0e4DnMp0TVLUckRKfK1owtAM3P0g0nzEsh97UAUxAHqsdQalhvQEww2YHfbZHqLKAI /c4bPnpQMjHblyyG0Z35Lj9QQwuWz/1eYVyRFM8hobDVRAe7P7KhUFmCZ8PTL5VHS3XW IG9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678954843; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=kTCGCOoDJTxIEcj5bZXvO/9uvZr0Hq0Yj/9WZl7ZrcM=; b=hMRKi63Tlbf8lKMuxQcze5Q+9l5yGqUiq6Qx858N+8lVhLL56fDzqiQAjl5ySc46+a b/417cl2/AzIEfxElGyAtVprbbYCGNHRBOBU45mFDp1OgxrdwRHveSxlNFZiUoxD83md rbVxHxrO85u4u6wTLt7LhXqoI3HbF55oCat7XFfTo5l1KeWiv45mFo/iVpE2wFwksNVi BpZMiTR9VS1LH8PwZVaVfX1hFHoqYTeF04/CgvP/2G1Kf1Jzsw7kKmJtUlLHWvbIsNs4 qYjebGWs6p+5vxDgA7FkVjrMIsVXz/zJ9mk4YeDpMqAPTaM5s+EwUaK3gu1MxsjinP4D Ae1w== X-Gm-Message-State: AO0yUKWhQRzGMANx+hgPdsT1Iawn/1YpugsH1AkhoQKbp7m+OxpAHopm qILRL88KOgRZCWlcyqUUioN00O3lLJLSzA== X-Received: by 2002:a05:6a20:28a2:b0:d6:5b4d:3704 with SMTP id q34-20020a056a2028a200b000d65b4d3704mr2504937pzf.14.1678954843511; Thu, 16 Mar 2023 01:20:43 -0700 (PDT) Received: from debian.me (subs02-180-214-232-12.three.co.id. [180.214.232.12]) by smtp.gmail.com with ESMTPSA id x52-20020a056a000bf400b005a8b4dcd21asm5031137pfu.15.2023.03.16.01.20.42 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 16 Mar 2023 01:20:43 -0700 (PDT) Received: by debian.me (Postfix, from userid 1000) id F3F3A106628; Thu, 16 Mar 2023 15:20:39 +0700 (WIB) From: Bagas Sanjaya <bagasdotme@gmail.com> To: Linux Documentation <linux-doc@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Linux Outreachy <outreachy@lists.linux.dev> Cc: Jonathan Corbet <corbet@lwn.net>, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>, Thorsten Leemhuis <linux@leemhuis.info>, Bagas Sanjaya <bagasdotme@gmail.com>, Greg KH <gregkh@linuxfoundation.org>, Lukas Bulwahn <lukas.bulwahn@gmail.com>, Akira Yokosawa <akiyks@gmail.com>, Alison Schofield <alison.schofield@intel.com>, Kloudifold <cloudifold.3125@gmail.com>, Sudip Mukherjee <sudipm.mukherjee@gmail.com> Subject: [PATCH] Documentation: submitting-patches: Disqualify style fixes from Fixes: tag Date: Thu, 16 Mar 2023 15:20:34 +0700 Message-Id: <20230316082034.14191-1-bagasdotme@gmail.com> X-Mailer: git-send-email 2.40.0 MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=1357; i=bagasdotme@gmail.com; h=from:subject; bh=9Ccoy6InasjXBSua2evwgPqlaLuGC0nVBJcOlvJaLvc=; b=owGbwMvMwCX2bWenZ2ig32LG02pJDClCF/3ur/SWuHvxPt+tjII3EvPUW84mHNfTmVj36Ez6z 8gndy6bd5SyMIhxMciKKbJMSuRrOr3LSORC+1pHmDmsTCBDGLg4BWAi6+MY/tnlzYs8/D5zYtPW fMOYyO7/KepNN7VclmV9iGZzb9+rxsTI0P5YVE+l6YrY5Enyd//Prcm5tX3HrxO5sf/0OLZYPNj rwwMA X-Developer-Key: i=bagasdotme@gmail.com; a=openpgp; fpr=701B806FDCA5D3A58FFB8F7D7C276C64A5E44A1D Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-0.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_WEB,SPF_HELO_NONE,SPF_PASS autolearn=no 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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1760513791542784310?= X-GMAIL-MSGID: =?utf-8?q?1760513801126252999?= |
Series |
Documentation: submitting-patches: Disqualify style fixes from Fixes: tag
|
|
Commit Message
Bagas Sanjaya
March 16, 2023, 8:20 a.m. UTC
An interpretation of submitting-patches.rst regarding Fixes: tag
interprets that the tag can be attributed to all kinds of issues
(including coding style ones). However, from the discussion on Outreachy
mailing list [1], Greg noted that the tag should not be meant for
patches that fix coding style issues.
Clarify the position on the doc.
Link: https://lore.kernel.org/outreachy/ZBFPnZbvdI46Ah6r@kroah.com/ [1]
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/process/submitting-patches.rst | 3 +++
1 file changed, 3 insertions(+)
base-commit: 6015b1aca1a233379625385feb01dd014aca60b5
Comments
On 16/03/2023 09:20, Bagas Sanjaya wrote: > An interpretation of submitting-patches.rst regarding Fixes: tag > interprets that the tag can be attributed to all kinds of issues > (including coding style ones). However, from the discussion on Outreachy > mailing list [1], Greg noted that the tag should not be meant for > patches that fix coding style issues. > > Clarify the position on the doc. > > Link: https://lore.kernel.org/outreachy/ZBFPnZbvdI46Ah6r@kroah.com/ [1] > Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com> > --- > Documentation/process/submitting-patches.rst | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst > index 69ce64e03c70f8..564418e42ffc01 100644 > --- a/Documentation/process/submitting-patches.rst > +++ b/Documentation/process/submitting-patches.rst > @@ -568,6 +568,9 @@ process nor the requirement to Cc: stable@vger.kernel.org on all stable > patch candidates. For more information, please read > Documentation/process/stable-kernel-rules.rst. > > +Note: Fixes: tag is appropriate only for real issues (e.g. reported bugs > +or compiler warnings). Coding style fixes should not bear this tag. I think it is pretty clear already. The doc says: "If your patch fixes a bug in a specific commit," and you are now repeating this. Coding style is not a bug, but that's obvious. Best regards, Krzysztof
On Thu, Mar 16, 2023 at 09:26:21AM +0100, Greg KH wrote: > > Coding style is not a bug, but that's obvious. > > I agree, let's not make this file even longer than it is if at all > possible. > I've actually been wondering if there is some way to split the file since it's quite large already. It's been unclear to me whether that would make it easier or harder to find stuff though. :-/ - Ted
"Theodore Ts'o" <tytso@mit.edu> writes: > On Thu, Mar 16, 2023 at 09:26:21AM +0100, Greg KH wrote: >> > Coding style is not a bug, but that's obvious. >> >> I agree, let's not make this file even longer than it is if at all >> possible. >> > > I've actually been wondering if there is some way to split the file > since it's quite large already. It's been unclear to me whether that > would make it easier or harder to find stuff though. :-/ I made a pass over it a few years ago and managed to shorten it a fair amount, but it clearly still needs attention. This is one of our most important and heavily referenced documents, and it would be nice if newcomers didn't feel like they were being asked to read a version of War and Peace written by Kafka before they can contribute. I'll try to find time to think about this some. jon
On 3/16/23 15:23, Krzysztof Kozlowski wrote: > I think it is pretty clear already. The doc says: > "If your patch fixes a bug in a specific commit," > Oops, I don't see the whole file before writing this patch. Thanks anyway!
diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst index 69ce64e03c70f8..564418e42ffc01 100644 --- a/Documentation/process/submitting-patches.rst +++ b/Documentation/process/submitting-patches.rst @@ -568,6 +568,9 @@ process nor the requirement to Cc: stable@vger.kernel.org on all stable patch candidates. For more information, please read Documentation/process/stable-kernel-rules.rst. +Note: Fixes: tag is appropriate only for real issues (e.g. reported bugs +or compiler warnings). Coding style fixes should not bear this tag. + .. _the_canonical_patch_format: The canonical patch format