From: Andreas Dilger <adilger@turbolabs.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Denis Zaitsev <zzz@cd-club.ru>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] init/main.c/root_dev_names - another one #ifdef
Date: Tue, 30 Oct 2001 18:28:10 -0700 [thread overview]
Message-ID: <20011030182810.B800@lynx.no> (raw)
In-Reply-To: <E15yj2E-0001o7-00@the-village.bc.nu> <Pine.LNX.4.33.0110301610460.1336-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0110301610460.1336-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Tue, Oct 30, 2001 at 04:12:36PM -0800
On Oct 30, 2001 16:12 -0800, Linus Torvalds wrote:
> On Wed, 31 Oct 2001, Alan Cox wrote:
> > It took that out deliberately a few months back. The ifdefs in fact
> > break stuff
> >
> > Firstly the array is __init so is discarded on boot
>
> I think that array really is broken. We should get the name association
> from the array that "register_blkdev()" maintains, I'm sure. That way
> random stupid driver X doesn't need to touch a common init/main.c file,
> which I find personally offensive.
I have a patch from way back (not mine) which allows the name to be
generated by the block device driver code. Let me know if you are
interested. This also fixes the ugly "lvma" "lvmb" devices that are
in /proc/partitions.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-10-31 1:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 23:53 [PATCH] init/main.c/root_dev_names - another one #ifdef Denis Zaitsev
2001-10-31 0:15 ` Alan Cox
2001-10-31 0:12 ` Linus Torvalds
2001-10-31 0:28 ` Alan Cox
2001-10-31 1:28 ` Andreas Dilger [this message]
2001-10-31 17:28 ` Christoph Hellwig
2001-10-31 18:20 ` Andreas Dilger
2001-10-31 18:31 ` Christoph Hellwig
2001-10-31 19:08 ` Andreas Dilger
2001-11-01 2:05 ` Denis Zaitsev
2001-10-31 1:36 ` Denis Zaitsev
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=20011030182810.B800@lynx.no \
--to=adilger@turbolabs.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=zzz@cd-club.ru \
/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