From: "Mike Miller (OS Dev)" <mikem@beardog.cca.cpqcorp.net>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/8] cciss: version number change
Date: Thu, 2 Nov 2006 08:46:23 -0600 [thread overview]
Message-ID: <20061102144623.GC16430@beardog.cca.cpqcorp.net> (raw)
In-Reply-To: <20061102141045.GH13555@kernel.dk>
On Thu, Nov 02, 2006 at 03:10:45PM +0100, Jens Axboe wrote:
> On Wed, Nov 01 2006, Mike Miller (OS Dev) wrote:
> >
> > PATCH 1/8
> >
> > This patch changes the cciss version number to 3.6.14 to reflect the following
> > functionality changes added by the rest of the set. They include:
>
> Mike, only some of your patches appeared to go out, both in personal
> mail and on the list.
I ran into some last minute issues so I stopped at 5. Still re-testing
the others.
This snippet seems to tbe the culprit.
+ if (blk_queue_stopped(h->gendisk[curr_queue]->queue) ||
+ blk_queue_plugged(h->gendisk[curr_queue]->queue))
+ blk_start_queue(h->gendisk[curr_queue]->queue);
We're testing to see if the queue is stopped or plugged so we don't
try to start am already running queue. Without the blk_queue_plugged
test it hangs every time. We added blk_queue_plugged and the first tests
seem to run ok. Then at the last minute something broke. Does this look
ok to you?
>
> Comment on this patch - normally you'd change the version number last,
> not as the first patch.
Yep, put the cart before horse I suppose. Maybe I shouldn't have a
version number at all. :)
mikem
next prev parent reply other threads:[~2006-11-02 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 21:49 Mike Miller (OS Dev)
2006-11-02 14:10 ` Jens Axboe
2006-11-02 14:46 ` Mike Miller (OS Dev) [this message]
2006-11-02 15:05 ` Arjan van de Ven
2006-11-02 15:17 ` Mike Miller (OS Dev)
2006-11-02 15:45 ` Jens Axboe
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=20061102144623.GC16430@beardog.cca.cpqcorp.net \
--to=mikem@beardog.cca.cpqcorp.net \
--cc=akpm@osdl.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®