linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Namhyung Kim <namhyung@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH 1/2] mdmon.8: fix possible typos
Date: Tue, 28 Jun 2011 16:38:00 +1000	[thread overview]
Message-ID: <20110628163800.2ba5aac6@notabene.brown> (raw)
In-Reply-To: <1308889610-8210-1-git-send-email-namhyung@gmail.com>

On Fri, 24 Jun 2011 13:26:49 +0900 Namhyung Kim <namhyung@gmail.com> wrote:

> Signed-off-by: Namhyung Kim <namhyung@gmail.com>
> ---
>  mdmon.8 |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/mdmon.8 b/mdmon.8
> index 7939a99..03b31b8 100644
> --- a/mdmon.8
> +++ b/mdmon.8
> @@ -104,7 +104,7 @@ within those disks.  MD metadata in comparison defines a 1:1
>  relationship between a set of block devices and a raid array.  For
>  example to create 2 arrays at different raid levels on a single
>  set of disks, MD metadata requires the disks be partitioned and then
> -each array can created be created with a subset of those partitions.  The
> +each array can be created with a subset of those partitions.  The
>  supported external formats perform this disk carving internally.
>  .P
>  Container devices simply hold references to all member disks and allow
> @@ -172,7 +172,7 @@ Note that
>  is automatically started by
>  .I mdadm
>  when needed and so does not need to be considered when working with
> -RAID arrays.  The only times it is run other that by
> +RAID arrays.  The only times it is run other than by
>  .I  mdadm
>  is when the boot scripts need to restart it after mounting the new
>  root filesystem.


Thanks.  I've applied both of these.

NeilBrown

      parent reply	other threads:[~2011-06-28  6:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24  4:26 [PATCH 1/2] mdmon.8: fix possible typos Namhyung Kim
2011-06-24  4:26 ` [PATCH 2/2] md.4: " Namhyung Kim
2011-06-28  6:38 ` NeilBrown [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=20110628163800.2ba5aac6@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=namhyung@gmail.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).