public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2.5.59] sim710: cleanup/remove most cli()'s
Date: 06 Feb 2003 10:35:45 -0600	[thread overview]
Message-ID: <1044549347.2331.58.camel@mulgrave> (raw)
In-Reply-To: <200302051603.48510@bilbo.math.uni-mannheim.de>

On Wed, 2003-02-05 at 09:03, Rolf Eike Beer wrote:
> Hi again,
> 
> I'm now looking for the best way to port this to use 53c700.c. This will 
> surely take a while, should I fix my fix and resend it or better leave this 
> unfixed until I find time to port it?

Do you actually have one of these (and is it EISA or MCA)?

I've got a MCA 710 in an old NCR3430 I can use.  I think the conversion
will only take a few days, I can try it out

> For today this fix should be enough. The second one is unneeded because 
> mca_register_driver does it.
> 
> Eike
> 
> Note: Please CC me, I'm not ...
> 
> --- linux-2.5.59-test/drivers/scsi/53c700.c     Fri Jan 17 03:21:40 2003
> +++ linux-2.5.59/drivers/scsi/53c700.c  Wed Feb  5 15:47:00 2003
> @@ -1769,7 +1769,7 @@
>         NCR_700_set_depth(SCp->device, NCR_700_get_depth(SCp->device) + 1);
> 
>         /* begin the command here */
> -       /* no need to check for NULL, test for command_slot_cound above
> +       /* no need to check for NULL, test for command_slot_count above
>          * ensures a slot is free */
>         slot = find_empty_slot(hostdata);
> 
> --- linux-2.5.59-test/drivers/scsi/NCR_D700.c   Fri Jan 17 03:21:39 2003
> +++ linux-2.5.59/drivers/scsi/NCR_D700.c        Wed Feb  5 15:47:02 2003
> @@ -340,7 +340,6 @@
>         .id_table = NCR_D700_id_table,
>         .driver = {
>                 .name = "NCR_D700",
> -               .bus = &mca_bus_type,
>                 .probe = NCR_D700_probe,
>         },

This is actually required by convention.  Just in case we ever move to a
unified driver registration model, it would use the bus type to test on.

James



  reply	other threads:[~2003-02-06 16:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04 10:23 [PATCH 2.5.59] sim710: cleanup/remove most cli()'s Rolf Eike Beer
2003-02-04 11:34 ` Christoph Hellwig
2003-02-04 23:11 ` James Bottomley
2003-02-05 15:03 ` Rolf Eike Beer
2003-02-06 16:35   ` James Bottomley [this message]
2003-02-07  7:26   ` Rolf Eike Beer
2003-02-08  3:57     ` James Bottomley
2003-02-11 10:55       ` Rolf Eike Beer
2003-02-11 18:30         ` 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=1044549347.2331.58.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=eike-kernel@sf-tec.de \
    --cc=linux-scsi@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