All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: 494501-forwarded@bugs.debian.org
Subject: Re: [PATCH] Split of raid scan code
Date: Sun, 10 Aug 2008 14:13:24 +0200	[thread overview]
Message-ID: <1218370404.7284.7.camel@fz.local> (raw)
In-Reply-To: <ca0f59980808100452u505cdc67x9a377929d96f3894@mail.gmail.com>

Am Sonntag, den 10.08.2008, 19:52 +0800 schrieb Bean:
> Hi,
> 
> This patch seperate the scan code from raid.c, and move it to
> mdraid.c. raid.c only contain generic raid handling code now. This
> make it much easier to extend to other raid layout, like various
> fakeraids.
> 

Really great that you work now on the RAID Code.

Today morning (for me) there just came another bugreport on Debian BTS
in about RAID [0]

This should probable go into lenny and so I probable have to make a
change for this anyway.

It's just the same as with these invalid BSD disklabels/partitions.
The return grub_error should be better changed to an grub_dprintf() +
return 0; for unknown RAID Levels.

Unknown RAID levels should be better just ignored, i.e. just not added
to the RAID array list instead of whole GRUB dropping to rescue mode.

[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494501




  reply	other threads:[~2008-08-10 12:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-10 11:52 [PATCH] Split of raid scan code Bean
2008-08-10 12:13 ` Felix Zielcke [this message]
2008-08-10 14:29 ` Robert Millan
2008-08-10 14:45   ` Bean
2008-08-10 15:49     ` Bean
2008-08-11 18:45       ` Bean
2008-08-11 20:13         ` Bean
2008-08-11 20:24           ` Bean
2008-08-11 20:30             ` Robert Millan
2008-08-12 11:49               ` Bean
2008-08-12 12:24                 ` Felix Zielcke
2008-08-12 13:32                 ` Robert Millan
2008-08-13 10:05                 ` Marco Gerards
2008-08-13 18:43                   ` Bean
2008-08-13 20:01                     ` Bean
2008-08-16  9:07                       ` Bean
2008-08-16 12:16                         ` Robert Millan
2008-08-16 15:20                           ` Bean
2008-08-17 14:19                             ` Bean
2008-08-17 14:52                             ` Robert Millan
2008-08-17 15:08                               ` Bean
2008-08-17 15:23                                 ` Robert Millan
2008-08-18 17:20                                   ` Bean
2008-08-23 14:51                                     ` Bean

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=1218370404.7284.7.camel@fz.local \
    --to=fzielcke@z-51.de \
    --cc=494501-forwarded@bugs.debian.org \
    --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.