File 0119-Mention-endian-in-documentation-for-update-byte-orde.patch of Package mdadm.7989

From 4224685fe9baf1df4c42bcb950c9a593efa0585f Mon Sep 17 00:00:00 2001
From: NeilBrown <>
Date: Mon, 8 May 2017 09:40:09 +1000
Subject: [PATCH] Mention "endian" in documentation for --update=byte-order
Git-commit: 4224685fe9baf1df4c42bcb950c9a593efa0585f
Patch-mainline: mdadm-4.0+
References: bsc#1069165, bsc#1069167, bsc#1068030

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

Reported-by: Trevor Cordes <>
Signed-off-by: NeilBrown <>
Signed-off-by: Jes Sorensen <>
Signed-off-by: Coly Li <>

--- | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/ b/
index fb99a5c..388e0ed 100644
--- a/
+++ b/
@@ -1264,7 +1264,8 @@ is correct.
 .B byteorder
 option allows arrays to be moved between machines with different
+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
openSUSE Build Service is sponsored by