From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: dcinege@psychosis.com
Cc: linux-raid <linux-raid@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: md.c - devfs naming fix.
Date: Tue, 31 Jul 2001 15:39:27 -0600 [thread overview]
Message-ID: <200107312139.f6VLdRp00491@mobilix.ras.ucalgary.ca> (raw)
In-Reply-To: <3B1AF531.C31CB45C@psychosis.com>
In-Reply-To: <3B1AF531.C31CB45C@psychosis.com>
Dave Cinege writes:
> This is a multi-part message in MIME format.
Yuk! MIME!
> Changes:
> Cleaned a few printk's
>
> Removed a meaningless ifndef.
>
> Moved md= name_to_ kdev_t() processing from md_setup() to
> md_setup_drive. Rewrote it and added devfs_find_handle() call
> to support devfs names for md=.
>
> The devfs_find_handle() code is now redundant in my patch and
> fs/super.c::mount_root(). It probably should be moved directly into
> name_to_kdev_t(), no? If this was done the md= code would have
> worked as is, except for the devfs code choking on the trailing ','
> in the device_names list. (Richard, want to check for this in the
> future?)
What is this patch trying to fix? I've been running devfs with MD
devices for a long time and have no problems. My raidtab lists devfs
device names (in fact, the /dev/sd/* variants created by devfsd) and
it seems to work fine.
> This diff is against md.c in 2.4.4.
> Comments/testing please.
Have you received any other comments? I've not tracked this.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2001-07-31 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 2:40 Dave Cinege
2001-07-31 21:39 ` Richard Gooch [this message]
2001-08-03 6:53 ` Neil Brown
2001-08-03 15:30 ` Richard Gooch
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=200107312139.f6VLdRp00491@mobilix.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=dcinege@psychosis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@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
all inboxes | Powered by JetHome®