Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp1463956ybx; Thu, 7 Nov 2019 12:14:16 -0800 (PST) X-Google-Smtp-Source: APXvYqwCIzTpSsPI/QTvETGTEMRGbhSLAuKiCP0xb/vOyxfrd+nRErvrLSSuC2y/EJUKwTOO5kss X-Received: by 2002:a50:959a:: with SMTP id w26mr5915373eda.214.1573157656567; Thu, 07 Nov 2019 12:14:16 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573157656; cv=none; d=google.com; s=arc-20160816; b=j0LsR1wtNeEydy6IuyYTYdGHkRo1jjAUcRYJjwB59D4Z+avKawuUi4xNi53ZqANTLK 0d2U4yYl6W9X2o/7vbs8T1bSENZkIdQbMUuWKr5BrAYM2qcLBvmqoUQvy77bHjSHxeUW 9ZO0NFVQ9x4A3+chtHQ69L4VYRKg5TbjnrUFa0IFlzNjKd6U9y4ag4Hb+vXqIGb7grve zvta0DtjC9InU7GLDq70XxoZ6GxYX+Fc8qY3e2MKcH6Nyqe9B8UDpTGmZKUoabcpnAnQ WuYN2izHMHp9wJ8NhuD2tuXG6Tu4ijKTJe+DhEeO6//pAao2Lvj28N3PQES1IPBusc7w j+zA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=PYfRu7WQF58F/soLrky2cuLvZVvkunHB6RjDkHAQJMI=; b=ZsvUtLcj8NgSzWNR+ntklwRbz+7xizcm6W/5NcgBcNX/HpuJet+9KCF3f5XJQXJZx3 VUfOxBFBSOjTMWkPz+jccQrqP/nsqOgg9ivco5QUdyip69vkFN9i6qMYVapKisgzWD9p 9Vsf8sI0nz8ccq6wIjv/ua7ZOdsbkNG5xpszt7jXXrNGsOzKrgQRxsrw1QR9TzlW1PM2 vj1zuTBL7+oHNQeRpdbVTHgv1DAWRB4MrPVl3xf7vAF/0O+drP04i4fJMg4y+L2D0F5b PiST2vNfPrfEefJdKghgVd5tGqRNhnnM1Vz0273zjvf1Adkh3pGpT4oq65XKoWbBDglq rAJQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c17si2221995edc.384.2019.11.07.12.13.52; Thu, 07 Nov 2019 12:14:16 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725995AbfKGUNQ (ORCPT + 99 others); Thu, 7 Nov 2019 15:13:16 -0500 Received: from ms.lwn.net ([45.79.88.28]:39490 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725870AbfKGUNQ (ORCPT ); Thu, 7 Nov 2019 15:13:16 -0500 Received: from lwn.net (localhost [127.0.0.1]) (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 ED69F6EC; Thu, 7 Nov 2019 20:13:14 +0000 (UTC) Date: Thu, 7 Nov 2019 13:13:13 -0700 From: Jonathan Corbet To: Dan Williams Cc: linux-kernel@vger.kernel.org, Thomas Gleixner , Mauro Carvalho Chehab , Steve French , Greg Kroah-Hartman , Linus Torvalds , "Tobin C. Harding" , Olof Johansson , "Martin K. Petersen" , Daniel Vetter , Joe Perches , Dmitry Vyukov , Alexandre Belloni , vishal.l.verma@intel.com, linux-nvdimm@lists.01.org, ksummit-discuss@lists.linuxfoundation.org Subject: Re: [PATCH v2 2/3] Maintainer Handbook: Maintainer Entry Profile Message-ID: <20191107131313.26b2d2cc@lwn.net> In-Reply-To: <20191001075559.629eb059@lwn.net> References: <156821692280.2951081.18036584954940423225.stgit@dwillia2-desk3.amr.corp.intel.com> <156821693396.2951081.7340292149329436920.stgit@dwillia2-desk3.amr.corp.intel.com> <20191001075559.629eb059@lwn.net> Organization: LWN.net MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Dan, A month or so ago I wrote... > > See Documentation/maintainer/maintainer-entry-profile.rst for more details, > > and a follow-on example profile for the libnvdimm subsystem. > > Thus far, the maintainer guide is focused on how to *be* a maintainer. > This document, instead, is more about how to deal with specific > maintainers. So I suspect that Documentation/maintainer might be the > wrong place for it. > > Should we maybe place it instead under Documentation/process, or even > create a new top-level "book" for this information? Unless I missed it, I've not heard back from you on this. I'd like to get this stuff pulled in for 5.5 if possible... would you object if I were to apply your patches, then tack on a move over to the process guide? Thanks, jon