linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: James Bottomley <James.Bottomley@steeleye.com>,
	axboe@suse.dk, linux-scsi@vger.kernel.org
Subject: Re: [PATCH][RFC] get rid of global array and ->init in sd.c and sr.c
Date: Wed, 23 Oct 2002 17:11:31 +0200	[thread overview]
Message-ID: <20021023171131.A17312@lst.de> (raw)
In-Reply-To: <20021023082853.GA9341@beaverton.ibm.com>; from andmike@us.ibm.com on Wed, Oct 23, 2002 at 01:28:53AM -0700

On Wed, Oct 23, 2002 at 01:28:53AM -0700, Mike Anderson wrote:
> Looks good. I ran it on a system with ips, aic, scsi_debug and qla2x00
> as a module. 
> 
> When I applied the patch I got a quite a few rejects on sd.c and sr.c. I
> fixed up sd.c, but did not run sr.c. My view is based off James
> scsi-misc-2.5.
> 
> I noticed the patch seems to include some of your driver_register
> removals (preiously posted) in init_sd and exit_sd, but there are no
> adds to scsi_register_device or scsi_unregister_device.

The patch is again 2.5.44 + my previous two patch (devicefs stuff
and ->finish removal).

> 
> Christoph Hellwig [hch@lst.de] wrote:
> > +	list_for_each(p, &sd_devlist) {
> > +		sdkp = list_entry(p, struct scsi_disk, list);
> >  		sdp = sdkp->device;
> >  		if (sdp && (sdp->host == shp) && (sdp->id == scsi_id)) {
> >  			retval = MKDEV_SD(dsk_nr);
> >  			break;
> 
> Might consider using list_for_each_entry since you always do both.

Yupp.

> I received a compile failures on sector_t until I put back the scsi.h
> include.

Umm, rhigh.  There are far to many users of sd.h to do such a change.
I'll submt a patch to get rid of all those sd.h users in some time.


  reply	other threads:[~2002-10-23 15:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22 19:07 [PATCH][RFC] get rid of global array and ->init in sd.c and sr.c Christoph Hellwig
2002-10-23  8:28 ` Mike Anderson
2002-10-23 15:11   ` Christoph Hellwig [this message]
2002-10-23 17:17     ` Mike Anderson
2002-10-24  0:50       ` Christoph Hellwig

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=20021023171131.A17312@lst.de \
    --to=hch@lst.de \
    --cc=James.Bottomley@steeleye.com \
    --cc=axboe@suse.dk \
    --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;
as well as URLs for NNTP newsgroup(s).