From: Levente Kurusa <levex@linux.com>
To: John Schmidt <johnschmidt4@gmail.com>,
linux-raid <linux-raid@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mdadm.8.in
Date: Tue, 29 Oct 2013 18:59:39 +0100 [thread overview]
Message-ID: <526FF78B.10708@linux.com> (raw)
In-Reply-To: <CACcY5Uxc2f6HOxLHt5DY5E71EvFbo0dNmtqUtH=FRwTitE=+zw@mail.gmail.com>
2013-10-29 18:16 keltezéssel, John Schmidt írta:
> I found a small bug in the documentation of mdadm. I fixed it in my
> local git clone of git://neil.brown.name/mdadm Here is the change:
>
> git diff mdadm.8.in
> diff --git a/mdadm.8.in b/mdadm.8.in
> index 09aff81..006ae59 100644
> --- a/mdadm.8.in
> +++ b/mdadm.8.in
> @@ -529,7 +529,7 @@ amount of available space is.
> .BR \-c ", " \-\-chunk=
> Specify chunk size of kibibytes. The default when creating an
> array is 512KB. To ensure compatibility with earlier versions, the
> -default when Building and array with no persistent metadata is 64KB.
> +default when building an array with no persistent metadata is 64KB.
> This is only meaningful for RAID0, RAID4, RAID5, RAID6, and RAID10.
>
> RAID4, RAID5, RAID6, and RAID10 require the chunk size to be a power
>
> Let me know if there are other things I need to do to get this patch submitted.
Hi,
I don't think this belongs to LKML.
I am not familiar with linux-raid but I think that the following guidelines
do apply there as well.
https://www.kernel.org/doc/Documentation/SubmittingPatches
Other than this, the patch is a legitimate one, I am sure it will be accepted.
--
Regards,
Levente Kurusa
next prev parent reply other threads:[~2013-10-29 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 17:16 [PATCH] mdadm.8.in John Schmidt
2013-10-29 17:59 ` Levente Kurusa [this message]
2013-10-29 21:34 ` NeilBrown
2013-10-29 21:37 ` John Schmidt
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=526FF78B.10708@linux.com \
--to=levex@linux.com \
--cc=johnschmidt4@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.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;
as well as URLs for NNTP newsgroup(s).