From: James Bottomley <James.Bottomley@SteelEye.com>
To: Greg KH <greg@kroah.com>
Cc: Patrick Mochel <mochel@osdl.org>,
Linus Torvalds <torvalds@transmeta.com>,
James Bottomley <James.Bottomley@SteelEye.com>,
linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] PCI reorg fix
Date: Thu, 09 May 2002 14:26:31 -0400 [thread overview]
Message-ID: <200205091826.g49IQV503155@localhost.localdomain> (raw)
In-Reply-To: Message from Greg KH <greg@kroah.com> of "Thu, 09 May 2002 10:15:22 PDT." <20020509171522.GB17627@kroah.com>
mochel@osdl.org said:
> Implementing the generic code is ~5 minutes work. However, it will
> break everything. OTOH, it would be the best motivation for
> modernizing these drivers...
greg@kroah.com said:
> Eeek, the scsi drivers? They haven't even started moving to the > 2
> years old pci interface yet! :)
It took several years to eliminate the old error handler, too...
If something's already broken, does it really matter how many pieces it's in?
There a siesmic changes coming to the scsi layer anyway, particularly if we
want to implement the new tag queuing code. The consistent alloc is virtually
a simple conversion recipe, so it shouldn't be too difficult to tack this
small change on to a set of much bigger ones.
James
next prev parent reply other threads:[~2002-05-09 18:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-08 23:11 Problems with 2.5.14 PCI reorg and non-PCI architectures James Bottomley
2002-05-09 8:44 ` Greg KH
2002-05-09 13:00 ` James Bottomley
2002-05-09 15:23 ` Greg KH
2002-05-09 16:47 ` James Bottomley
2002-05-09 16:52 ` [BK PATCH] PCI reorg fix Greg KH
2002-05-09 18:06 ` Patrick Mochel
2002-05-09 17:15 ` Greg KH
2002-05-09 18:26 ` James Bottomley [this message]
2002-05-09 18:23 ` Kai Germaschewski
2002-05-09 18:26 ` Patrick Mochel
2002-05-09 18:46 ` Kai Germaschewski
2002-05-09 19:45 ` Martin Dalecki
2002-05-09 21:34 ` James Bottomley
2002-05-09 20:51 ` Martin Dalecki
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=200205091826.g49IQV503155@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=torvalds@transmeta.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®