public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Andrew Morton <akpm@osdl.org>, "Randy.Dunlap" <rddunlap@osdl.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: buslogic-update.patch
Date: Mon, 29 Dec 2003 15:23:10 +0000	[thread overview]
Message-ID: <20031229152310.A28993@infradead.org> (raw)
In-Reply-To: <1072710934.2123.3.camel@mulgrave>; from James.Bottomley@steeleye.com on Mon, Dec 29, 2003 at 09:15:33AM -0600

On Mon, Dec 29, 2003 at 09:15:33AM -0600, James Bottomley wrote:
> On Mon, 2003-12-29 at 05:57, Christoph Hellwig wrote:
> > On Mon, Dec 29, 2003 at 03:35:15AM -0800, Andrew Morton wrote:
> > > James, can I unload this on you?   Thanks.
> > 
> > The patch needs rework anyway as I outlined to Randy in a previous mail.
> 
> I seem to remember the version I have was reworked (too long ago for
> precise memory, though).  Could you check the BK tree to make sure,
> please?

The patch looks the same to the one in your tree.  The particular missing
bits are:  implementing the eh_abort method based on the old EH code, and
removing all the old EH code so the driver continues to compile when
scsi_obsolete.h is gone (you can check that by commenting it out in scsi.h).


  reply	other threads:[~2003-12-29 15:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-29 11:35 buslogic-update.patch Andrew Morton
2003-12-29 11:57 ` buslogic-update.patch Christoph Hellwig
2003-12-29 15:15   ` buslogic-update.patch James Bottomley
2003-12-29 15:23     ` Christoph Hellwig [this message]
2003-12-29 18:09   ` buslogic-update.patch Randy.Dunlap
2003-12-29 15:14 ` buslogic-update.patch James Bottomley

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=20031229152310.A28993@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rddunlap@osdl.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