From mboxrd@z Thu Jan 1 00:00:00 1970 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 46EFFC433FE for ; Mon, 3 Oct 2022 16:24:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229880AbiJCQY3 (ORCPT ); Mon, 3 Oct 2022 12:24:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45568 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229847AbiJCQYU (ORCPT ); Mon, 3 Oct 2022 12:24:20 -0400 Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6200C1CB3E for ; Mon, 3 Oct 2022 09:24:18 -0700 (PDT) Received: by mail-wr1-x433.google.com with SMTP id r6so17526058wru.8 for ; Mon, 03 Oct 2022 09:24:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date; bh=V6sEgywP+y9yheTpj3XS7gZeAORICObdhjMK1hQwQH0=; b=yt9KY5U9okipxbrLKzskc7Gs/cvXyXtn85MqF5hFwwO+6wBbaGQ52krnt5wJ0xPqGl Oum+qr+wzL0ibMgSEBF1DFQHCiyCItNgLIZq+j2AYFiKYh+4M3VyIqZ7ygLmBK/KXGGD d9v9VWpC2yf+B9eKg7TSoaiEj4ecGgEogicf58tBXqAMN9ztsm1WiyUEGJf8bEOfbEp+ gi2FSZSCCb1Gb1rMB6+fDpeK8WJiNfDxAAhSUD95M2kwB29Ojznr/3MIb1n6NfuowQT1 UVawQnybtk1BF3bifKxZNLTTb3KNBj3YmnKF7W6H2DqgXr4rjZTDpQONoGjAuR0806Eg ML0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date; bh=V6sEgywP+y9yheTpj3XS7gZeAORICObdhjMK1hQwQH0=; b=iLi+2fUJ8LkoIXTsxWmMYJ1JEiE1sj85U10qoMN+ONszlxVAVOoswtgZalfToeS/2B /qHW+rW7a3fzUrnOlrEY96aiYXSbT82tK/i69ZD/YckC6GbFWIvGXgQhY3a8FaMhJgQf nYrXJ/aCGdJakRVJE3uixDhhEUwirn/rd2xQn29a4DplfCdedwUHnFp8YgkEFuXxnGAs Ynop1MPUvpzO9+x7FNRz0RMuuM1/iDPd1eqDHIM5OWcRq3fmNtstP3oBVlSuhjD5CcHn t5rvFGarLh/Vz7qDFiycWSkcwKRiDDrxAdtl6zkKDYH7c978FT65JZpBCVnBaUlkekq/ gksA== X-Gm-Message-State: ACrzQf1Dq90kZRS0TXxt4/doHChz7lUzRoQi3ERWz+uiKYBfvZTbxKu7 DCT1wfDJ1tjdnLmaDPMoJpau3w== X-Google-Smtp-Source: AMsMyM4ho12Cev8om81o/z1uFofHRvXYNrtiG4XKAx2U7h4k6KiGEb/Mts1jmpPcuEmcIqxebc+qmg== X-Received: by 2002:a05:6000:697:b0:22a:f737:b10f with SMTP id bo23-20020a056000069700b0022af737b10fmr12965233wrb.222.1664814256298; Mon, 03 Oct 2022 09:24:16 -0700 (PDT) Received: from sagittarius-a.chello.ie (188-141-3-169.dynamic.upc.ie. [188.141.3.169]) by smtp.gmail.com with ESMTPSA id j24-20020a05600c1c1800b003b95ed78275sm4989013wms.20.2022.10.03.09.24.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 03 Oct 2022 09:24:15 -0700 (PDT) From: Bryan O'Donoghue To: corbet@lwn.net, linux@leemhuis.info, konstantin@linuxfoundation.org, krzysztof.kozlowski@linaro.org, linux-doc@vger.kernel.org, joe@perches.com, akiyks@gmail.com Cc: linux-kernel@vger.kernel.org, Bryan O'Donoghue Subject: [PATCH RESEND v4 2/2] Documentation/process: Be more explicit about who to mail on patch submission Date: Mon, 3 Oct 2022 17:24:11 +0100 Message-Id: <20221003162411.431774-3-bryan.odonoghue@linaro.org> X-Mailer: git-send-email 2.37.3 In-Reply-To: <20221003162411.431774-1-bryan.odonoghue@linaro.org> References: <20221003162411.431774-1-bryan.odonoghue@linaro.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Recently when submitting a yaml change I found that I had omitted the maintainer whose tree the change needed to go through. The reason for that is the path in MAINTAINERS is marked as Supported not Maintained. Reading MAINTAINERS we see quote: Supported: Someone is actually paid to look after this. Maintained: Someone actually looks after it. The current submitting-patches.rst only says to mail maintainers though not supporters. Discussing further on the list the suggestion was made to state that the following are the right addresses to mail: - Maintainers - Supporters - Reviewers - Dedicated lists - LKML as a fallback when there is no dedicated list Add in a two sentences to capture that statement. Signed-off-by: Bryan O'Donoghue --- Documentation/process/submitting-patches.rst | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst index be49d8f2601b4..90fda3367a405 100644 --- a/Documentation/process/submitting-patches.rst +++ b/Documentation/process/submitting-patches.rst @@ -227,8 +227,11 @@ You should always copy the appropriate subsystem maintainer(s) on any patch to code that they maintain; look through the MAINTAINERS file and the source code revision history to see who those maintainers are. The script scripts/get_maintainer.pl can be very useful at this step (pass paths to -your patches as arguments to scripts/get_maintainer.pl). If you cannot find a -maintainer for the subsystem you are working on, Andrew Morton +your patches as arguments to scripts/get_maintainer.pl). In the output of +get_maintainer.pl the recommendation is to mail every maintainer, supporter, +reviewer and dedicated mailing list. If get_maintainer doesn't indicate a +dedicated mailing list linux-kernel@vger.kernel.org should be included. If you +cannot find a maintainer for the subsystem you are working on, Andrew Morton (akpm@linux-foundation.org) serves as a maintainer of last resort. You should also normally choose at least one mailing list to receive a copy -- 2.37.3