public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Cinege <dcinege@psychosis.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@transmeta.com>
Subject: [PATCH] Remove arbitrary md= boot device limit
Date: Mon, 29 Jan 2001 06:51:44 -0500	[thread overview]
Message-ID: <3A755950.9C730B80@psychosis.com> (raw)

linux-2.4.1p11-1/drivers/md/md.c
line 3643
-#define MAX_MD_BOOT_DEVS     8
+#define MAX_MD_BOOT_DEVS     MAX_MD_DEVS

-------------------------------------------------------
To:  Dave Cinege <dcinege@psychosis.com>

On Mon, 29 Jan 2001, Dave Cinege wrote:

> -#define MAX_MD_BOOT_DEVS     8
> +#define MAX_MD_BOOT_DEVS     MAX_MD_DEVS

sure this is fine.

        Ingo
-------------------------------------------------------
To:	Ingo Molnar <mingo@redhat.com>

Devices above md8 will not be initialized when speced with md=.
Error ("md: Minor device number too high.\n");

The limitation is imposed by
        #define MAX_MD_BOOT_DEVS        8
However it appears arbitray to me. Doesn't make much sence since you can create
/dev/md100 and it may well be the only md device you have...

Is there any reason the next 2.4.1 prepatch should not include this?

-#define MAX_MD_BOOT_DEVS       8
+#define MAX_MD_BOOT_DEVS       MAX_MD_DEVS

(If not I assume you will be submitting this to Linus...)

-- 
"Nobody will ever be safe until the last cop is dead."
		NH Rep. Tom Alciere - (My new Hero)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2001-01-29 11:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-29 11:51 Dave Cinege [this message]
2001-01-29 20:26 ` [PATCH] Remove arbitrary md= boot device limit Neil Brown
2001-01-29 20:53   ` [patch] raid-B1, 2.4.1-pre11, fixes, cleanups Ingo Molnar

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=3A755950.9C730B80@psychosis.com \
    --to=dcinege@psychosis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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