From: James Bottomley <James.Bottomley@steeleye.com>
To: "Juergen E. Fischer" <fischer@linux-buechse.de>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
fischer@norbit.de
Subject: Re: [PATCH] [v2] aha152x cmnd->device oops
Date: 29 Oct 2003 12:10:17 -0600 [thread overview]
Message-ID: <1067451264.1829.37.camel@mulgrave> (raw)
In-Reply-To: <20031029175621.GB5903@linux-buechse.de>
On Wed, 2003-10-29 at 11:56, Juergen E. Fischer wrote:
> Why not? It's a new command after all and if the initialization is
> done correctly (ie. ->device is setup) it works the way it is now.
The usual reason is that ACA emulation is turned around in interrupt
context, so new memory allocations should be avoided if they can be.
for the aha that could eliminate the check for NULL cmnd.
James
next prev parent reply other threads:[~2003-10-29 18:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 15:57 [PATCH] scsi_device refcounting and list lockdown Christoph Hellwig
2003-10-28 0:01 ` Randy.Dunlap
2003-10-28 9:06 ` Christoph Hellwig
2003-10-28 20:45 ` [PATCH] [v2] aha152x cmnd->device oops Randy.Dunlap
2003-10-28 22:50 ` Mike Christie
2003-10-28 22:50 ` Randy.Dunlap
2003-10-29 0:26 ` Randy.Dunlap
2003-10-29 12:20 ` Juergen E. Fischer
2003-10-29 14:58 ` James Bottomley
2003-10-29 17:56 ` Juergen E. Fischer
2003-10-29 18:10 ` James Bottomley [this message]
2003-10-30 21:19 ` Juergen E. Fischer
2003-10-29 13:42 ` Christoph Hellwig
2003-10-28 2:32 ` [PATCH] scsi_device refcounting and list lockdown Mike Anderson
2003-10-28 9:07 ` Christoph Hellwig
2003-10-28 15:52 ` James Bottomley
2003-10-28 17:37 ` Christoph Hellwig
2003-10-30 22:41 ` James Bottomley
2003-10-31 9:11 ` Christoph Hellwig
2003-11-14 11: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=1067451264.1829.37.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=fischer@linux-buechse.de \
--cc=fischer@norbit.de \
--cc=linux-scsi@vger.kernel.org \
--cc=rddunlap@osdl.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