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: Fri, 23 Dec 2022 07:16:31 -0700 [thread overview]
Message-ID: <87sfh6mchs.fsf@meer.lwn.net> (raw)
In-Reply-To: <20221223093351.GA8028@lst.de>
Christoph Hellwig <hch@lst.de> writes:
> On Thu, Dec 22, 2022 at 01:54:35PM -0700, Jonathan Corbet wrote:
>> 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.
>
> I though about that, but could not thing of a good subdirectory.
We can paint that shed another day :)
>> 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.
>
> The new document is included in
> Documentation/maintainer/maintainer-entry-profile.rst in this path.
Duh sorry, I'm not quite sure what I was thinking there.
> I also did check for new warnings and did not see any, even if that's
> a little difficult with the rather chatty shpinx output.
Someday we'll get all those warnings gone...I hope...
Meanwhile, if it's useful:
Acked-by: Jonathan Corbet <corbet@lwn.net>
Thanks,
jon
next prev parent reply other threads:[~2022-12-23 14:16 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
2022-12-23 9:33 ` Christoph Hellwig
2022-12-23 14:16 ` Jonathan Corbet [this message]
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=87sfh6mchs.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.