From: NeilBrown <neilb@suse.com>
Date: Sun, 7 May 2017 23:40:09 +0000 (+1000)
Subject: Mention "endian" in documentation for --update=byte-order
X-Git-Tag: mdadm-4.1-rc1~149
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=4224685fe9baf1df4c42bcb950c9a593efa0585f;p=thirdparty%2Fmdadm.git

Mention "endian" in documentation for --update=byte-order

This makes it easier to find as "endian" is a commonly used term.

Reported-by: Trevor Cordes <trevor@tecnopolis.ca>
Signed-off-by: NeilBrown <neilb@suse.com>
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
---

diff --git a/mdadm.8.in b/mdadm.8.in
index fb99a5cd..388e0edb 100644
--- a/mdadm.8.in
+++ b/mdadm.8.in
@@ -1264,7 +1264,8 @@ is correct.
 The
 .B byteorder
 option allows arrays to be moved between machines with different
-byte-order.
+byte-order, such as from a big-endian machine like a Sparc or some
+MIPS machines, to a little-endian x86_64 machine.
 When assembling such an array for the first time after a move, giving
 .B "\-\-update=byteorder"
 will cause