From: Torben Mathiasen <torben.mathiasen@hp.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Torben Mathiasen <torben.mathiasen@hp.com>,
David Woodhouse <dwmw2@infradead.org>,
"Cagle, John" <john.cagle@hp.com>,
Christian Borntraeger <linux-kernel@borntraeger.net>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Torben Mathiasen <device@lanana.org>,
linux-mtd@lists.infradead.org
Subject: Re: [Patch][RFC] conflicting device major numbers in devices.txt
Date: Tue, 21 Sep 2004 18:49:38 +0200 [thread overview]
Message-ID: <20040921164938.GQ4055@linux> (raw)
In-Reply-To: <200409211703.47188.arnd@arndb.de>
On Tue, Sep 21 2004, Arnd Bergmann wrote:
> On Dienstag, 21. September 2004 11:23, Torben Mathiasen wrote:
> > s/390 dasd moved to major 94.
> > s/390 VM/ESA moved to major 95.
> > INFTL moved to major 96.
>
> Actually, major 95 has never been used for VM minidisks or any other
> s390 block device in any 2.4 or 2.6 based distribution, because that
> driver was integrated into the dasd driver (it just uses a different
> access method on the same devices). You might want to document that
> this number is currently unused, even if it doesn't get assigned to
> any other driver.
>
So, what you're saying is that Major 95 is not used at all in real life? Then
I'll remove it from from the list completely during the my next push. Let me
know if there's a point in keeping it assigned even if its obsolete.
Torben
next prev parent reply other threads:[~2004-09-21 16:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-18 23:14 [Patch][RFC] conflicting device major numbers in devices.txt Cagle, John
2004-09-19 7:50 ` David Woodhouse
2004-09-21 9:23 ` Torben Mathiasen
2004-09-21 15:03 ` Arnd Bergmann
2004-09-21 16:49 ` Torben Mathiasen [this message]
2004-09-21 17:03 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2004-09-18 22:03 Christian Borntraeger
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=20040921164938.GQ4055@linux \
--to=torben.mathiasen@hp.com \
--cc=akpm@osdl.org \
--cc=arnd@arndb.de \
--cc=device@lanana.org \
--cc=dwmw2@infradead.org \
--cc=john.cagle@hp.com \
--cc=linux-kernel@borntraeger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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