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: Thu, 22 Dec 2022 13:54:35 -0700 [thread overview]
Message-ID: <87zgbfma5w.fsf@meer.lwn.net> (raw)
In-Reply-To: <20221222160920.GA10193@lst.de>
Christoph Hellwig <hch@lst.de> writes:
> On Wed, Dec 21, 2022 at 06:45:32AM -0700, Jonathan Corbet wrote:
>> 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 ?
>
> What about the following? This moves the file to a new
> Documentation/nvme/ directory and then links it form
> Documentation/maintainer/maintainer-entry-profile.rst:
I'm not really a fan of adding more top-level directories; one of these
years I'd like to try to move things in the opposite direction. That is
a battle for another day, though; for now let's just go with this and
get the document merged.
That said, I suspect you'll add a build warning about the new document
not being included in any toctree. Fixing that would involve adding a
basic index.rst to the new directory and adding that to a file like
Documentation/subsystem-apis.rst.
Thanks,
jon
next prev parent reply other threads:[~2022-12-22 20:54 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
2022-12-22 16:09 ` Christoph Hellwig
2022-12-22 20:54 ` Jonathan Corbet [this message]
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=87zgbfma5w.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.