From: Karel Zak <kzak@redhat.com>
To: "John Groves (jgroves)" <jgroves@micron.com>
Cc: Ruediger Meier <ruediger.meier@ga-group.nl>,
"util-linux@vger.kernel.org" <util-linux@vger.kernel.org>
Subject: Re: [EXT] Re: ready for v2.32 ?
Date: Mon, 26 Feb 2018 23:50:06 +0100 [thread overview]
Message-ID: <20180226225006.rslgrlgsmphsyhqh@ws.net.home> (raw)
In-Reply-To: <1519685049171.25700@micron.com>
On Mon, Feb 26, 2018 at 10:44:12PM +0000, John Groves (jgroves) wrote:
> Doh! Mpool stores its metadata as little endian, and rigorously uses
> le32_to_cpu and the like to move on-media structures to & from
> memory.
>
> le32_to_cpu(osd->osb_cksum1) would be the correct way to handle it.
Fixed. Thanks for quick reply!
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2018-02-26 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 21:16 ready for v2.32 ? Ruediger Meier
2018-02-26 22:20 ` Karel Zak
2018-02-26 22:44 ` [EXT] " John Groves (jgroves)
2018-02-26 22:50 ` Karel Zak [this message]
2018-02-26 23:01 ` Ruediger Meier
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=20180226225006.rslgrlgsmphsyhqh@ws.net.home \
--to=kzak@redhat.com \
--cc=jgroves@micron.com \
--cc=ruediger.meier@ga-group.nl \
--cc=util-linux@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).