From: Christoph Hellwig <hch@caldera.de>
To: Andrew Clausen <clausen@gnu.org>
Cc: Kevin Corry <corryk@us.ibm.com>,
evms-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: gendisk list access (was: [Evms-devel] Unresolved symbols)
Date: Sat, 15 Dec 2001 11:58:00 +0100 [thread overview]
Message-ID: <20011215115800.D6187@caldera.de> (raw)
In-Reply-To: <OFCE7B6713.9A6E1AF1-ON85256B02.004FB1C4@raleigh.ibm.com> <20011112173217.A3404@caldera.de> <01120514525902.13647@boiler> <20011205225346.A7313@caldera.de> <20011211233618.B982@gnu.org>
In-Reply-To: <20011211233618.B982@gnu.org>; from clausen@gnu.org on Tue, Dec 11, 2001 at 11:36:18PM +1100
On Tue, Dec 11, 2001 at 11:36:18PM +1100, Andrew Clausen wrote:
> On Wed, Dec 05, 2001 at 10:53:46PM +0100, Christoph Hellwig wrote:
> > - each block queue gets a pointer to be used for partitioning, this will
> > be opaque to the drivers.
>
> Yuck!
>
> Why do you want a reference to partitions?
I don't want - that't the point.
The whole block layer and the drivers should not know at all about
specific partitions and volume managers.
If we want to still support the current partition APIs it will not
be entirely possible to reach this goal, but Al convienced me in a
long discussion that 2.6 is to early to get rid of those yet.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
prev parent reply other threads:[~2001-12-15 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OFCE7B6713.9A6E1AF1-ON85256B02.004FB1C4@raleigh.ibm.com>
[not found] ` <20011112173217.A3404@caldera.de>
2001-12-05 20:52 ` gendisk list access (was: [Evms-devel] Unresolved symbols) Kevin Corry
2001-12-05 21:53 ` Christoph Hellwig
2001-12-05 22:18 ` Kevin Corry
2001-12-05 22:38 ` Christoph Hellwig
2001-12-11 12:36 ` Andrew Clausen
2001-12-15 10:58 ` Christoph Hellwig [this message]
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=20011215115800.D6187@caldera.de \
--to=hch@caldera.de \
--cc=clausen@gnu.org \
--cc=corryk@us.ibm.com \
--cc=evms-devel@lists.sourceforge.net \
--cc=linux-kernel@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