[RndTbl] [mdadm PATCH] Mention "endian" in documentation for --update=byte-order

[NeilBrown]

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

Reported-by: Trevor Cordes <trevor at tecnopolis.ca>
Signed-off-by: NeilBrown <neilb at suse.com>
---
 mdadm.8.in | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/mdadm.8.in b/mdadm.8.in
index fb99a5cd9159..388e0edbf89a 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
-- 
2.12.2

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://muug.ca/pipermail/roundtable/attachments/20170508/f06cbf1d/attachment.sig>