public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [RFC][PATCH] scsi-misc-2.5 software enqueue when can_queue reached
Date: Sun, 2 Mar 2003 10:15:31 -0800	[thread overview]
Message-ID: <20030302101530.A21052@beaverton.ibm.com> (raw)
In-Reply-To: <20030302085728.A11407@infradead.org>; from hch@infradead.org on Sun, Mar 02, 2003 at 08:57:28AM +0000

On Sun, Mar 02, 2003 at 08:57:28AM +0000, Christoph Hellwig wrote:
> The patch looks fine to me in principle, a few nitpicks are below.
> (btw, any chance you could post a current scsi midlayer multipathing
> patch?  I see there is BK activity.. :))

The last multi-path patch is available here:

http://www-124.ibm.com/storageio/multipath/scsi-multipath/releases/2.5.59-mpath-1.patch.gz

Did you want to see something newer?

Mike was talking about pulling it forward to 2.5.latest, maybe he has
started.

> > +++ edited/drivers/scsi/hosts.c	Thu Feb 27 16:21:09 2003
> > @@ -383,6 +383,7 @@
> >  	scsi_assign_lock(shost, &shost->default_lock);
> >  	INIT_LIST_HEAD(&shost->my_devices);
> >  	INIT_LIST_HEAD(&shost->eh_cmd_q);
> > +	INIT_LIST_HEAD(&shost->pending_queue);
> 
> This isn't consistant, either ew use _q in all new code or _queue.
> (peronally I prefer the latter)

Yes, I also prefer _queue, maybe I should make it pending_cmd, then the
name is not an issue, and the type is not embeded in the name (the _q
implies that it is a queue or list_head)?

> > +void scsi_host_send_pending (struct Scsi_Host *shost)
> 
> codingstyle issue:  no space between function name and opening brace.
> 
> > +{
> > +	struct scsi_cmnd *scmd;
> > +	unsigned long flags;
> > +
> > +	spin_lock_irqsave(shost->host_lock, flags);
> > +	while (!shost->host_self_blocked
> > +	       && !list_empty(&shost->pending_queue)) {
> 
> Linux codingstyle sais the && should be before the line break.

OK thanks.

-- Patrick Mansfield

  reply	other threads:[~2003-03-02 18:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-28 19:19 [RFC][PATCH] scsi-misc-2.5 software enqueue when can_queue reached Patrick Mansfield
2003-03-02  8:57 ` Christoph Hellwig
2003-03-02 18:15   ` Patrick Mansfield [this message]
2003-03-03 15:52   ` Randy.Dunlap
2003-03-03 18:17   ` Luben Tuikov
2003-03-04  1:11     ` Andrew Morton
2003-03-04  4:49       ` Luben Tuikov
2003-03-02 20:57 ` Luben Tuikov
2003-03-02 21:08   ` Luben Tuikov
2003-03-03 20:52   ` Patrick Mansfield
2003-03-03 22:40     ` Luben Tuikov
2003-03-03 23:41       ` Patrick Mansfield
2003-03-04  5:48         ` Luben Tuikov
2003-03-05  3:02 ` James Bottomley
2003-03-05 18:43   ` Patrick Mansfield
2003-03-06 15:57     ` James Bottomley
2003-03-06 17:41       ` Patrick Mansfield
2003-03-06 18:04         ` 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=20030302101530.A21052@beaverton.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=hch@infradead.org \
    --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