From: Jonathan Corbet <corbet@lwn.net>
To: Christoph Hellwig <hch@lst.de>,
axboe@meta.com, sagi@grimberg.me, kbusch@kernel.org
Cc: 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, 15 Dec 2022 06:08:44 -0700 [thread overview]
Message-ID: <87zgboddb7.fsf@meer.lwn.net> (raw)
In-Reply-To: <20221215125130.261098-1-hch@lst.de>
Christoph Hellwig <hch@lst.de> writes:
> This adds a document about what specification features are supported by
> the Linux NVMe driver, and what qualifies for a quirk if an implementation
> has problems following the specification.
>
> Signed-off-by: Jens Axboe <axboe@kernel.dk>
> Signed-off-by: Keith Busch <kbusch@kernel.org>
> Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> Documentation/process/index.rst | 1 +
> .../process/nvme-feature-and-quirk-policy.rst | 77 +++++++++++++++++++
> MAINTAINERS | 1 +
> 3 files changed, 79 insertions(+)
> create mode 100644 Documentation/process/nvme-feature-and-quirk-policy.rst
The document looks fine, but I do wonder if it wouldn't be better placed
with the other maintainer entries in Documentation/maintainer?
Thanks,
jon
next prev parent reply other threads:[~2022-12-15 13:08 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 [this message]
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
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=87zgboddb7.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).