public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: jim owens <jowens@hp.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] don't OOPs when we are not raid56
Date: Tue, 08 Sep 2009 10:15:29 +0100	[thread overview]
Message-ID: <1252401329.4483.579.camel@macbook.infradead.org> (raw)
In-Reply-To: <4A9E9E00.5080608@hp.com>

On Wed, 2009-09-02 at 12:32 -0400, jim owens wrote:
> @@ -2895,7 +2895,7 @@ again:
>                 multi->num_stripes = num_stripes;
>                 multi->max_errors = max_errors;
>         }
> -       if (raid_map_ret) {
> +       if (raid_map) {
>                 sort_parity_stripes(multi, raid_map);
>                 *raid_map_ret = raid_map;
>         }

Applied (manually, because I think your mail was whitespace-damaged).
Thanks.

Chris, where do we stand with getting this merged? You were going to
sort out the upper layers to handle the minimum write size, weren't you?

I'm also going to do RAID50/60 support, and with hpa's help I'll extend
it to do RAID7/70 too -- but you're not waiting for that, are you?
 
-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@intel.com                              Intel Corporation


  reply	other threads:[~2009-09-08  9:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06 10:17 RAID[56] status David Woodhouse
2009-08-07  9:43 ` Roy Sigurd Karlsbakk
2009-08-07 15:22   ` David Woodhouse
2009-09-02 16:32     ` [PATCH] don't OOPs when we are not raid56 jim owens
2009-09-08  9:15       ` David Woodhouse [this message]
2009-09-08 13:48         ` Chris Mason
2009-11-10 19:51 ` RAID[56] status Dan Williams
2009-11-10 20:05   ` Tomasz Torcz
2009-11-10 20:11   ` Chris Mason
2009-11-10 21:06   ` tsuraan
2009-11-10 21:20     ` Gregory Maxwell

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=1252401329.4483.579.camel@macbook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=jowens@hp.com \
    --cc=linux-btrfs@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