From: sschricker@suse.de (Simon Schricker)
Subject: [PATCH] nvme-cli: fix typo, removing duplicate 'are'
Date: Thu, 11 Apr 2019 11:00:14 +0200 [thread overview]
Message-ID: <1554973214.7741.0.camel@suse.de> (raw)
In-Reply-To: <20190411084140.29946-1-sschricker@suse.de>
Sorry, I fixed the wrong file, I will resend the patch. Embarrasing.
Simon
--
6DFE EAC6 CB38 1F78 5FDA 91F3 AC64 34A6 41FC 10F5
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20190411/1a19b156/attachment.sig>
prev parent reply other threads:[~2019-04-11 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 8:41 [PATCH] nvme-cli: fix typo, removing duplicate 'are' Simon Schricker
2019-04-11 9:00 ` Simon Schricker [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=1554973214.7741.0.camel@suse.de \
--to=sschricker@suse.de \
/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.