public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: wrlk@riede.org
Cc: linux-scsi@vger.kernel.org, andmike@us.ibm.com
Subject: Re: [PATCH] ide-scsi changes for new mid level api and error handling in 2.5.52
Date: Sun, 22 Dec 2002 12:59:05 +1100	[thread overview]
Message-ID: <3E051C69.5000701@torque.net> (raw)
In-Reply-To: 20021221224604.GC7990@linnie.riede.org

Willem Riede wrote:
> Here is my proposal for bringing ide-scsi in line with the current kernel.
> 
> The attached patch does:
> 
> 1. Change from old style initialization to the new hotplug initialization model.
>    It involves declaring both a parent device and bus kernel object, which feels
>    a bit awkward, but hey, it works.
> 
> 2. Make ide-scsi request sense itself when CHECK_CONDITION is asserted. This 
>    change particularly makes ide-scsi run much smoother on my test box.
> 
> 3. Implement eh_abort_handler and eh_device_reset_handler. I have no real way
>    to thoroughly test these new routines, so for this part particularly I ask
>    for peer review.

Willem,
Good work.

I tried it out with an ATAPI cdrom and it worked fine.
Tried a few error conditions (e.g. purposely reading
past the end of the cdrom) and it reacted properly.

The introduction of a new sysfs bus type: "ide-scsi" to
add to scsi_debug's "pseudo" seems a bit messy. It will
do for now; hopefully Mike Anderson will come up with
some coherent sysfs naming scheme for drivers
that bridge to another protocol stack (e.g. ide-scsi,
usb-storage and ieee1394/sbp2).

BTW Willem's patch is against lk 2.5.52 .

Doug Gilbert


  reply	other threads:[~2002-12-22  1:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-21 22:46 [PATCH] ide-scsi changes for new mid level api and error handling in 2.5.52 Willem Riede
2002-12-22  1:59 ` Douglas Gilbert [this message]
2002-12-22 17:14   ` Willem Riede
2002-12-23 19:05     ` Andre Hedrick
2002-12-25 21:30       ` Alan Cox

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=3E051C69.5000701@torque.net \
    --to=dougg@torque.net \
    --cc=andmike@us.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=wrlk@riede.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