From: Patrick Mansfield <patmans@us.ibm.com>
To: Christoph Hellwig <hch@lst.de>
Cc: James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] cleanup code for /proc add/remove single device
Date: Thu, 21 Nov 2002 10:10:09 -0800 [thread overview]
Message-ID: <20021121101009.A18201@eng2.beaverton.ibm.com> (raw)
In-Reply-To: <20021121185548.A15559@lst.de>; from hch@lst.de on Thu, Nov 21, 2002 at 06:55:48PM +0100
On Thu, Nov 21, 2002 at 06:55:48PM +0100, Christoph Hellwig wrote:
> On Thu, Nov 21, 2002 at 09:21:15AM -0800, Patrick Mansfield wrote:
> > current scsi-misc-2.5) to get the add to work correctly. Otherwise, this
> > worked fine.
>
> Duh! thanks for the fix. The other patch also looks okay, although I
> wonder why you need hardirq.h.
For the in_atomic check in scsi_init_io.
-- Patrick Mansfield
prev parent reply other threads:[~2002-11-21 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 1:23 [PATCH] cleanup code for /proc add/remove single device Christoph Hellwig
2002-11-21 17:21 ` Patrick Mansfield
2002-11-21 17:55 ` Christoph Hellwig
2002-11-21 18:10 ` Patrick Mansfield [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=20021121101009.A18201@eng2.beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=hch@lst.de \
--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