From: kbusch@kernel.org (Keith Busch)
Subject: [PATCH v2] nvme-cli: fix typo, removing the duplicate 'are'
Date: Mon, 15 Apr 2019 09:13:14 -0600 [thread overview]
Message-ID: <20190415151314.GC7312@localhost.localdomain> (raw)
In-Reply-To: <20190411092316.5479-1-sschricker@suse.de>
On Thu, Apr 11, 2019@11:23:16AM +0200, Simon Schricker wrote:
> Signed-off-by: Simon Schricker <sschricker at suse.de>
> ---
> Documentation/nvme-netapp-ontapdevices.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/nvme-netapp-ontapdevices.txt b/Documentation/nvme-netapp-ontapdevices.txt
> index 8eaa73f..c292758 100644
> --- a/Documentation/nvme-netapp-ontapdevices.txt
> +++ b/Documentation/nvme-netapp-ontapdevices.txt
> @@ -13,7 +13,7 @@ SYNOPSIS
> DESCRIPTION
> -----------
> Display information about ONTAP devices on the host. The ONTAP devices are
> -are identified using the Identify Controller data.
> +identified using the Identify Controller data.
>
> OPTIONS
> -------
Applied, thank you.
prev parent reply other threads:[~2019-04-15 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190411092619epcas5p1a46c545239ce6f387137cf97ae02600a@epcms2p4>
2019-04-11 9:23 ` [PATCH v2] nvme-cli: fix typo, removing the duplicate 'are' Simon Schricker
2019-04-11 11:21 ` Minwoo Im
2019-04-11 22:46 ` Chaitanya Kulkarni
2019-04-15 15:13 ` Keith Busch [this message]
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=20190415151314.GC7312@localhost.localdomain \
--to=kbusch@kernel.org \
/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