From: Shivam Chaudhary <cvam0000@gmail.com>
To: kbusch@kernel.org, axboe@kernel.dk
Cc: hch@lst.de, sagi@grimberg.me, corbet@lwn.net,
linux-nvme@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, cvam <cvam0000@gmail.com>
Subject: [PATCH v2] Remove duplicate "and" in 'Linux NVMe docs.
Date: Tue, 10 Sep 2024 10:57:37 +0530 [thread overview]
Message-ID: <20240910052737.30579-1-cvam0000@gmail.com> (raw)
In-Reply-To: <8734m8h9ce.fsf@trenco.lwn.net>
From: cvam <cvam0000@gmail.com>
Remove duplicate occurrence of 'and' in
'Linux NVMe Feature and Quirk Policy' title heading.
tested: Not breaking anything.
Signed-off-by: Shivam Chaudhary <cvam0000@gmail.com>
---
Documentation/nvme/feature-and-quirk-policy.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/nvme/feature-and-quirk-policy.rst b/Documentation/nvme/feature-and-quirk-policy.rst
index c01d836d8e41..e21966bf20a8 100644
--- a/Documentation/nvme/feature-and-quirk-policy.rst
+++ b/Documentation/nvme/feature-and-quirk-policy.rst
@@ -1,8 +1,8 @@
.. SPDX-License-Identifier: GPL-2.0
-=======================================
-Linux NVMe feature and and quirk policy
-=======================================
+===================================
+Linux NVMe feature and quirk policy
+===================================
This file explains the policy used to decide what is supported by the
Linux NVMe driver and what is not.
--
2.34.1
next prev parent reply other threads:[~2024-09-10 5:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 20:02 [PATCH] Typo in the file 'feature-and-quirk-policy.rst' cvam
2024-09-09 20:15 ` Jonathan Corbet
2024-09-09 20:30 ` Matthew Wilcox
2024-09-10 2:02 ` Bagas Sanjaya
2024-09-10 5:27 ` Shivam Chaudhary [this message]
2024-09-10 21:45 ` [PATCH v2] Remove duplicate "and" in 'Linux NVMe docs Jonathan Corbet
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=20240910052737.30579-1-cvam0000@gmail.com \
--to=cvam0000@gmail.com \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--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