Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp3995005pxj; Tue, 15 Jun 2021 13:03:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz7DUJk1hOsLN7lY+JVwIm4UGEEiLRT/ZSl38IyVuClRLbrtO6No5Nifok99Yu55dPimB+M X-Received: by 2002:a05:6402:1e8b:: with SMTP id f11mr1625587edf.86.1623787397930; Tue, 15 Jun 2021 13:03:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623787397; cv=none; d=google.com; s=arc-20160816; b=DCWmDgJdNgAeYnRyVDdrwnFb8/nsDuu/yyeySD0o+Ty/z7Ko9YSUrc3Wm3jBpH/mo0 uSYvzYcvlR5E1Nl3owLtgWEJNYBPUa/2dy5SuU2Uc7clavNTGQbUW1NOtUWTnABTB37y NSb/nqbxmrq94c2q3KnX8DFx/yfLV3yhV5zL2YA92If5Kxhj/7BXbfCjv99PFmjVn8nw fZqcxB9F9wTw6QaCD5DdLsAMDTVLAf4wie5SARPeggHHMI3zUcIZOqxchlPWspgQkJwX aoNtsEiVH6ErRCzJ+AURZK5IGQamuVUVk56pJRhccxAr7Ed5xaiWVDacduKNchJ2mVfM PmmA== 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:dkim-signature; bh=7ualycgfS9SsVG5r3CGGFNY9Eyg7pdelPCnID2r514o=; b=kSvKsLIbi7ck786Zgs2iAkHn+x1YExfvqKM8xRpLKGcEFJ/vtGdFD0b+LzNpiJ3xVw 4RVPFzOIvDZ61C7dxKbBPF/jXmEncE4r9A96CUXrDmhTn6X3N4Xm7tXFdKxZbieuMMrk 7Qvus6YM6BrraacOVwcoNwMrz5RXx0myHGd9uUOH2RuZOsJMO6WtKBHuO1I9VepIRjr/ dNzU6iY5aM7sv1q52Mn5kAc5TPTMmWSO8J2w1R9FdT135NZz1bQ9mutiJ0Omf1ljwUHK rBmOUPH8w6sZIycQtYofWqxe4BZYXAV3PLvniOyiY2PwCE2zOKJuDkUTJcezehuW2B21 HoLw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@pbarker.dev header.s=fm1 header.b=vbcXakdn; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=HwX78l9x; 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 j6si14970989edq.137.2021.06.15.13.02.55; Tue, 15 Jun 2021 13:03:17 -0700 (PDT) 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=@pbarker.dev header.s=fm1 header.b=vbcXakdn; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=HwX78l9x; 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 S230082AbhFOUDx (ORCPT + 99 others); Tue, 15 Jun 2021 16:03:53 -0400 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]:48151 "EHLO wout2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229898AbhFOUDx (ORCPT ); Tue, 15 Jun 2021 16:03:53 -0400 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 01D77E09; Tue, 15 Jun 2021 16:01:47 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Tue, 15 Jun 2021 16:01:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pbarker.dev; h= from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; s=fm1; bh=7ualycgfS9SsVG5r3CGGFNY9Ey g7pdelPCnID2r514o=; b=vbcXakdn0TjjxcVQ1c7qEky0OKHiGTaTm1ZahtfEpW QhEJfUZKw8orHFkp9XoZcy34X1loX1+z0e1QAbl1bz9vRGtq2pdPedehkQyzJGtx 10vQW6SZase4LY22ek03udwyWMZ5D/fK50mzHOJ+z5pbFmJkmi7Wby26KBNp0dAH GCYGcuT0bElNkjS+21NwMeZnuVXJnluna/jdCLALZCEZOm1Npfcu+34GqoSubM4z NVQOP4PSfzeRRbLnl9KSudE0/F8N6yxjQmS6QoNHiaNl+XZzDz0TfL5YjoPDK0wR dwaOyVQkBaGA8sITh3u9ohNJywJPcTu8Q0gNL0sE9bOQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:date:from :message-id:mime-version:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=7ualycgfS9SsVG5r3 CGGFNY9Eyg7pdelPCnID2r514o=; b=HwX78l9xpHpZ2cBHBPutnvYuQay4FnfAg ctQksHFDhHyoYrPUHOFFd9rVS5HZ86SyhIZFjeHyWBTs1oJHPw7ua9lksU6Bu7Xl L7VMRJLAvKhzOPFGFw7QIEGb6w9euholQJor1OATxjGvRha4WCiEmHF7u9+muXpx ezMldHBNas3eaFlFzFrLjQkYjth0j1nuSgiN1Kg5kJX+LvJWHORbIRwjR/zaFWip pLzPZ5t1L2IEFcyXX36r28OcsQwDHOe1+IyDy9yEVmdQ9Fzse3Y8LuwcK8WwnCZl AZftHH5X/S1tc9QjAxwZBGjvD6XbHHBlCAyln/zmR+Po7mrDZaNiw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedvjedgudeghecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvffufffkofgggfestdekredtredttdenucfhrhhomheprfgruhhluceu rghrkhgvrhcuoehprghulhesphgsrghrkhgvrhdruggvvheqnecuggftrfgrthhtvghrnh epgfdvgeevgffhjedtkedtfeffteeftdejfeejveetveevtedtfeelieeuteekledtnecu ffhomhgrihhnpehkvghrnhgvlhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurf grrhgrmhepmhgrihhlfhhrohhmpehprghulhesphgsrghrkhgvrhdruggvvh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 15 Jun 2021 16:01:45 -0400 (EDT) From: Paul Barker To: Jonathan Corbet , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Paul Barker Subject: [RFC PATCH] MAINTAINERS: Add note on patches to MAINTAINERS itself Date: Tue, 15 Jun 2021 21:01:41 +0100 Message-Id: <20210615200141.8573-1-paul@pbarker.dev> X-Mailer: git-send-email 2.32.0 MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=1975; h=from:subject; bh=CQdGsYdn7Jszdx1S122LNT1PZKXWpsAGlZ2LHEujeLs=; b=owGbwMvMwCG2OjnkzdxdX/IYT6slMSScZFeyNtp3S51FvqegsfdlCeveNxKuSkxGvkU+kTzpjzNT WS93lLIwiHEwyIopsmzu+Xr/aa8jb0bILQWYOaxMIEMYuDgFYCIivxkZZljJP1AxMJFzUPM/XXzqMv t777kzhO/c+uWuwCH3bsPS84wM70X/Lbl2cIla9/Q1CV7qUc5b5e7F97XuXuwskalZW8/BBQA= X-Developer-Key: i=paul@pbarker.dev; a=openpgp; fpr=98B2AAC100AC3F82BB5D546774975C81B7E66BAC Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Since there is no entry in the maintainers list for the MAINTAINERS file itself, we should add a short note on how to handle patches to this file. Signed-off-by: Paul Barker --- I'm in the process of updating device tree files as part of $JOB and would like to add relevant entries to the MAINTAINERS file. I've searched through the maintainer list, read what I can find in the docs and ran scripts/get_maintainer.pl but I can't see a clear statement of where to send patches which modify MAINTAINERS. Looking at a couple of examples of previous patches which modified MAINTAINERS and looking up the relevant emails on lore.kernel.org I've made my best guess on how these changes should be handled. This patch adds that best guess as a note to the MAINTAINERS list so it's easy for folks to find in the future. This is an RFC as others probably know the correct way to handle patches to the MAINTAINERS file. Even if this "best guess" is wrong I hope it highlights that such a note would be useful. I've treated this patch as a docs patch, please let me know if it should be sent to different maintainers/lists. MAINTAINERS | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index bc0ceef87b73..b7873dad9997 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -143,6 +143,12 @@ Maintainers List first. When adding to this list, please keep the entries in alphabetical order. +.. note:: There is no entry in this list for the MAINTAINERS file itself. + Patches which modify existing MAINTAINERS entries should be sent to + all other maintainers in the relevant entry. When adding new + MAINTAINERS entries please use ``scripts/get_maintainer.pl`` to find + other maintainers with overlapping entries in this list. + 3C59X NETWORK DRIVER M: Steffen Klassert L: netdev@vger.kernel.org -- 2.32.0