linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Christoph Hellwig <hch@lst.de>
Cc: Christoph Hellwig <hch@lst.de>,
	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 <axboe@kernel.dk>
Subject: Re: [PATCH] docs, nvme: add a feature and quirk policy document
Date: Wed, 21 Dec 2022 06:45:32 -0700	[thread overview]
Message-ID: <87mt7g27lv.fsf@meer.lwn.net> (raw)
In-Reply-To: <20221221083450.GA23903@lst.de>

Christoph Hellwig <hch@lst.de> 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

  reply	other threads:[~2022-12-21 13:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 12:51 [PATCH] docs, nvme: add a feature and quirk policy document Christoph Hellwig
2022-12-15 13:08 ` Jonathan Corbet
2022-12-15 13:26   ` Christoph Hellwig
2022-12-21  8:34     ` Christoph Hellwig
2022-12-21 13:45       ` Jonathan Corbet [this message]
2022-12-22 16:09         ` Christoph Hellwig
2022-12-22 20:54           ` Jonathan Corbet
2022-12-23  9:33             ` Christoph Hellwig
2022-12-23 14:16               ` Jonathan Corbet
2022-12-15 17:04 ` Randy Dunlap
2022-12-16  7:24   ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mt7g27lv.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=axboe@kernel.dk \
    --cc=axboe@meta.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).