From: Sabin Mihai Rapan <sabin.rapan@gmail.com>
To: gregkh@linuxfoundation.org, jsimmons@infradead.org,
andreas.dilger@intel.com, oleg.drokin@intel.com
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Sabin Mihai Rapan <sabin.rapan@gmail.com>
Subject: [PATCH 1/4] staging: lustre: Fix "from from"->"from"
Date: Mon, 21 May 2018 17:34:27 +0000 [thread overview]
Message-ID: <20180521173430.9759-1-sabin.rapan@gmail.com> (raw)
In-Reply-To: <20180520124408.GA10692@kroah.com>
Trivial fix to spelling mistake in README.txt
Signed-off-by: Sabin Mihai Rapan <sabin.rapan@gmail.com>
---
drivers/staging/lustre/README.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/README.txt b/drivers/staging/lustre/README.txt
index 0676243eea9e..783959240490 100644
--- a/drivers/staging/lustre/README.txt
+++ b/drivers/staging/lustre/README.txt
@@ -4,7 +4,7 @@ Lustre Parallel Filesystem Client
The Lustre file system is an open-source, parallel file system
that supports many requirements of leadership class HPC simulation
environments.
-Born from from a research project at Carnegie Mellon University,
+Born from a research project at Carnegie Mellon University,
the Lustre file system is a widely-used option in HPC.
The Lustre file system provides a POSIX compliant file system interface,
can scale to thousands of clients, petabytes of storage and
--
2.17.0
next prev parent reply other threads:[~2018-05-21 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 18:27 [PATCH 2/5] staging: lustre: Fix block comments style Sabin Mihai Rapan
2018-05-20 12:44 ` Greg KH
2018-05-21 17:34 ` Sabin Mihai Rapan [this message]
2018-05-21 17:34 ` [PATCH 2/4] staging: lustre: Fix "Possible intergrate"->"Possibly integrate" Sabin Mihai Rapan
2018-05-21 17:34 ` [PATCH 3/4] staging: lustre: Fix "unsigned"->"unsigned int" Sabin Mihai Rapan
2018-05-21 17:34 ` [PATCH v2 4/4] staging: lustre: Fix block comments style Sabin Mihai Rapan
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=20180521173430.9759-1-sabin.rapan@gmail.com \
--to=sabin.rapan@gmail.com \
--cc=andreas.dilger@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jsimmons@infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg.drokin@intel.com \
/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).