From: NeilBrown <neilb@suse.com>
To: Jes Sorensen <jes.sorensen@gmail.com>,
Trevor Cordes <trevor@tecnopolis.ca>
Cc: Continuation of Round Table discussion <roundtable@muug.ca>,
Adam Thompson <athompso@athompso.net>,
linux-raid@vger.kernel.org
Subject: [mdadm PATCH] Mention "endian" in documentation for --update=byte-order
Date: Mon, 08 May 2017 09:40:09 +1000 [thread overview]
Message-ID: <87a86onsme.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20170506014117.4d3f1689@pog.tecnopolis.ca>
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
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>
---
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-05-07 23:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 21:39 Big-endian RAID5 recovery problem Adam Thompson
2017-05-01 21:59 ` Anthony Youngman
2017-05-01 22:33 ` Adam Thompson
2017-05-02 2:47 ` Phil Turmel
2017-05-02 7:29 ` [RndTbl] " Trevor Cordes
2017-05-02 8:59 ` Roman Mamedov
2017-05-05 19:22 ` [RndTbl] " Adam Thompson
2017-05-06 5:57 ` NeilBrown
2017-05-06 6:41 ` [RndTbl] " Trevor Cordes
2017-05-07 23:40 ` NeilBrown [this message]
2017-05-08 17:42 ` [mdadm PATCH] Mention "endian" in documentation for --update=byte-order Jes Sorensen
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=87a86onsme.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=athompso@athompso.net \
--cc=jes.sorensen@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=roundtable@muug.ca \
--cc=trevor@tecnopolis.ca \
/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).