From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH] segfault in grub-probe when spare or faulty disks are found
Date: Mon, 25 Oct 2010 13:11:13 +0200 [thread overview]
Message-ID: <4CC565D1.9030001@gmail.com> (raw)
In-Reply-To: <4CC564E9.5020109@mur.at>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
On 10/25/2010 01:07 PM, Martin Schitter wrote:
> Am 2010-09-28 22:24, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
>> I didn't respond to the patch because it's not correct: it only
>> propagates the restriction instead of removing it. Thanks for reporting
>> the issue. I'll fix it tomorrow (hopefully)
>
> the problem with version 1.x raid spare disks still exists (see also:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593652).
> could you please come up with a better solution for this problem or
> correct my patch.
>
Sorry for the delay, I had very busy period. I'll do this this evening
> thanks
> martin
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2010-10-25 11:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 20:32 [PATCH] segfault in grub-probe when spare or faulty disks are found Martin Schitter
2010-09-28 20:24 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-29 12:16 ` Martin Schitter
2010-10-25 11:07 ` Martin Schitter
2010-10-25 11:11 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-10-26 8:58 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-10-26 15:29 ` Martin Schitter
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=4CC565D1.9030001@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.