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 19B21C4332F for ; Wed, 21 Dec 2022 13:45:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229612AbiLUNpg (ORCPT ); Wed, 21 Dec 2022 08:45:36 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43962 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229522AbiLUNpf (ORCPT ); Wed, 21 Dec 2022 08:45:35 -0500 Received: from ms.lwn.net (ms.lwn.net [45.79.88.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8E11C1276F; Wed, 21 Dec 2022 05:45:34 -0800 (PST) Received: from localhost (unknown [IPv6:2601:281:8300:73::5f6]) (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 93009377; Wed, 21 Dec 2022 13:45:33 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 ms.lwn.net 93009377 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lwn.net; s=20201203; t=1671630333; bh=beJP4Kkr6h/TSuOC2Qdh8B/D19ZPOqfTigW9Np05uSM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=M/yTZSKLUuE/4gSu73sQpKftAaDPNioV00WJlWxHkM984l79P3miE6ozHL2971BcL sCpK6Vnme6hcPU4TElZkLAV9opZwnlH0NMxxkmoAPRnA+Tb4xdnNCFUsdFOKottDjK YWx9B3VyiZvBTsSnRWzOU7N0e1EZuUodYTJMg9WLS1fK1dJ6e2mxIFbOAUIHXkGIGq W+79MiRh991nxm7gL3piE2D7YszQcFSIYf0M6YA3Wr0/3jhDZZO8pORUvtZV5SDLXl pvOiSYSc14RBoTXd7e5dsj5CG+SeYa87mjkkdDwqnqNNPcKmYznwf5kvHWZaQ0WB6x s59EuAWyoFFZw== From: Jonathan Corbet To: Christoph Hellwig Cc: Christoph Hellwig , axboe@meta.com, sagi@grimberg.me, kbusch@kernel.org, linux-nvme@lists.infradead.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Jens Axboe Subject: Re: [PATCH] docs, nvme: add a feature and quirk policy document In-Reply-To: <20221221083450.GA23903@lst.de> References: <20221215125130.261098-1-hch@lst.de> <87zgboddb7.fsf@meer.lwn.net> <20221215132622.GA21083@lst.de> <20221221083450.GA23903@lst.de> Date: Wed, 21 Dec 2022 06:45:32 -0700 Message-ID: <87mt7g27lv.fsf@meer.lwn.net> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org Christoph Hellwig writes: > On Thu, Dec 15, 2022 at 02:26:22PM +0100, Christoph Hellwig wrote: >> On Thu, Dec 15, 2022 at 06:08:44AM -0700, Jonathan Corbet wrote: >> > The document looks fine, but I do wonder if it wouldn't be better placed >> > with the other maintainer entries in Documentation/maintainer? >> >> Hmm, nothing in there looks very similar to me, while process >> seems to have real policy documents. But we can live with either >> place. > > Any strong arguments for moving it Documentation/maintainer? > > I'd like to merge this with the fixups from Randy through the nvme > tree ASAP, and need to decide on the location. Sorry, the argument is that the subsystem profiles there were created for the very purpose of documenting subsystem-specific patch policies like those found in your document. The hope is that, someday, people will be able to go to one place to learn what special hoops any given subsystem will make them jump through. This isn't something I'm going to dig in my heels on, though. But at a minimum, could you add an entry to Documentation/maintainer/maintainer-entry-profile.rst ? Thanks, jon