mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Andre Hedrick <andre@linux-ide.org>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	Anton Altaparmakov <aia21@cantab.net>,
	linux-kernel@vger.kernel.org, sullivan@austin.ibm.com
Subject: Re: [BUG-2.5.24-BK] DriverFS panics on boot!
Date: Thu, 04 Jul 2002 18:59:39 -0400	[thread overview]
Message-ID: <200207042259.g64MxdH03605@localhost.localdomain> (raw)
In-Reply-To: Message from Andre Hedrick <andre@linux-ide.org>  of "Thu, 04 Jul 2002 15:20:10 PDT." <Pine.LNX.4.10.10207041517530.19028-100000@master.linux-ide.org>

andre@linux-ide.org said:
> The whole reason for my replacement was to add driverfs to IDE and
> remove devfs and ultimately "de-gooch" the kernel.  So we are nearly
> 100 patches in and the primary reason for ousting is still a failure,
> NICE! 

Well, perhaps we have slightly different agendas.  I think driverfs will solve 
a whole series of enumeration and mapping problems that occur in the SCSI 
mid-layer and which get especially tortuous with Fibre Channel.  I also think 
it will help us bring the SCSI and IDE views closer together.

I persuaded Linus to put the SCSI driverfs patches in the kernel even though I 
knew they touched more than SCSI (the partitions code) and were not as modular 
as I would have liked.  The reason is that we need to get as much visibility 
on this as possible before the code freeze.  I'm fully prepared to sort out 
any problems with this as they arise (and indeed the panic is already fixed).

I believe it's a variation of a principle attributable to a wise Australian:  
get the right solution in, even if not quite the right implementation.  That 
way, everyone will be extrememly motivated to help produce the right 
implementation.

James



  reply	other threads:[~2002-07-04 22:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-04 15:41 James Bottomley
2002-07-04 15:55 ` Anton Altaparmakov
2002-07-04 22:20 ` Andre Hedrick
2002-07-04 22:59   ` James Bottomley [this message]
2002-07-05  2:15     ` Andre Hedrick
2002-07-05  6:34       ` Jens Axboe
2002-07-05  6:51         ` Andre Hedrick
2002-07-05  7:38           ` Jens Axboe
2002-07-05 22:43             ` Andre Hedrick
  -- strict thread matches above, loose matches on Subject: below --
2002-07-04 11:28 Anton Altaparmakov

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=200207042259.g64MxdH03605@localhost.localdomain \
    --to=james.bottomley@steeleye.com \
    --cc=aia21@cantab.net \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sullivan@austin.ibm.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

all inboxes | Powered by JetHome®