From: Jens Axboe <jens.axboe@oracle.com>
To: scameron@beardog.cca.cpqcorp.net
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
akpm@linux-foundation.org, mikem@beardog.cca.cpqcorp.net
Subject: Re: [patch 1/8] cciss: Use schedule_timeout_uninterruptible in SCSI error handling code
Date: Tue, 9 Jun 2009 05:48:06 +0200 [thread overview]
Message-ID: <20090609034805.GV11363@kernel.dk> (raw)
In-Reply-To: <20090608205938.GG23523@beardog.cca.cpqcorp.net>
On Mon, Jun 08 2009, scameron@beardog.cca.cpqcorp.net wrote:
>
>
> Use schedule_timeout_uninterruptible instead of schedule_timeout in the
> scsi error handling code when waiting between TUR polls since we are not
> interested in nor want to be interrupted by signals.
Thanks Steve, applied 1-8.
--
Jens Axboe
prev parent reply other threads:[~2009-06-09 3:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 20:59 [patch 1/8] cciss: Use schedule_timeout_uninterruptible in SCSI error handling code scameron
2009-06-09 3:48 ` Jens Axboe [this message]
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=20090609034805.GV11363@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mikem@beardog.cca.cpqcorp.net \
--cc=scameron@beardog.cca.cpqcorp.net \
/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