From: Paul Clements <paul.clements@steeleye.com>
To: neilb@suse.de
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH/BUG] mdadm: write behind value does not have endian conversion
Date: Fri, 06 Oct 2006 15:03:42 -0400 [thread overview]
Message-ID: <4526A88E.9000005@steeleye.com> (raw)
In-Reply-To: <45269835.2020801@steeleye.com>
Paul Clements wrote:
> --- mdadm-2.5.1/bitmap.c.orig Fri Oct 6 13:40:35 2006
> +++ mdadm-2.5.1/bitmap.c Fri Oct 6 13:40:53 2006
> @@ -33,6 +33,7 @@ inline void sb_le_to_cpu(bitmap_super_t
> sb->chunksize = __le32_to_cpu(sb->chunksize);
> sb->daemon_sleep = __le32_to_cpu(sb->daemon_sleep);
> sb->sync_size = __le64_to_cpu(sb->sync_size);
> + sb->write_behind = __le32_to_cpu(sb->sync_size);
Obviously, sync_size should be write_behind in the above line.
next prev parent reply other threads:[~2006-10-06 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 17:53 [PATCH/BUG] mdadm: write behind value does not have endian conversion Paul Clements
2006-10-06 19:03 ` Paul Clements [this message]
2006-10-09 1:20 ` Neil Brown
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=4526A88E.9000005@steeleye.com \
--to=paul.clements@steeleye.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).