linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes.Sorensen@redhat.com
To: neilb@suse.de
Cc: dledford@redhat.com, joe.lawrence@stratus.com,
	linux-raid@vger.kernel.org
Subject: [PATCH 0/2] Solve problem adding internal bitmaps to 1.0 arrays
Date: Thu, 26 Apr 2012 17:12:55 +0200	[thread overview]
Message-ID: <1335453177-8515-1-git-send-email-Jes.Sorensen@redhat.com> (raw)

From: Jes Sorensen <Jes.Sorensen@redhat.com>

Hi,

This set solves the problem with adding internal bitmaps to 1.0
arrays. Basically there were two problems, one the sign extension from
u32 to long was done incorrectly, and second we also tried to convert
it to an 'unsigned long long' when passing it to the kernel.

With these two applied I can succesfully add bitmaps to 1.0 arrays.

Please hollor if you see any problems with this patchset.

Cheers,
Jes

Jes Sorensen (2):
  Fix sign extension of bitmap_offset in super1.c
  Introduce sysfs_set_num_signed() and use it to set bitmap/offset

 Grow.c   |    4 ++--
 mdadm.h  |    2 ++
 super1.c |    4 ++--
 sysfs.c  |    8 ++++++++
 4 files changed, 14 insertions(+), 4 deletions(-)

-- 
1.7.7.6


             reply	other threads:[~2012-04-26 15:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 15:12 Jes.Sorensen [this message]
2012-04-26 15:12 ` [PATCH 1/2] Fix sign extension of bitmap_offset in super1.c Jes.Sorensen
2012-04-26 15:18   ` Doug Ledford
2012-04-26 15:21     ` Jes Sorensen
2012-04-26 15:25       ` Jes Sorensen
2012-04-26 15:32         ` Richard Henderson
2012-04-26 15:35           ` Doug Ledford
2012-04-26 15:36           ` Jes Sorensen
2012-04-29 23:55       ` NeilBrown
2012-04-26 15:12 ` [PATCH 2/2] Introduce sysfs_set_num_signed() and use it to set bitmap/offset 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=1335453177-8515-1-git-send-email-Jes.Sorensen@redhat.com \
    --to=jes.sorensen@redhat.com \
    --cc=dledford@redhat.com \
    --cc=joe.lawrence@stratus.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).