From: Christoph Hellwig <hch@lst.de>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove unused includes and misleading comments from scsi_lib.c
Date: Wed, 20 Nov 2002 18:50:48 +0100 [thread overview]
Message-ID: <20021120185048.A4886@lst.de> (raw)
In-Reply-To: <20021120084709.A18453@eng2.beaverton.ibm.com>; from patmans@us.ibm.com on Wed, Nov 20, 2002 at 08:47:09AM -0800
On Wed, Nov 20, 2002 at 08:47:09AM -0800, Patrick Mansfield wrote:
> I had to add back the smp_lock.h include to compile with CONFIG_PREEMPT,
> as kernel_locked was not defined and is used by in_atomic().
Bah. Any chance you could fix the header declaring in_atomic() to pull
in smp_lock.h by itself instead?
next prev parent reply other threads:[~2002-11-20 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-17 22:54 [PATCH] remove unused includes and misleading comments from scsi_lib.c Christoph Hellwig
2002-11-20 16:47 ` Patrick Mansfield
2002-11-20 17:50 ` Christoph Hellwig [this message]
2002-11-20 19:10 ` Patrick Mansfield
2002-11-20 19:25 ` J.E.J. Bottomley
2002-11-20 19:25 ` J.E.J. 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=20021120185048.A4886@lst.de \
--to=hch@lst.de \
--cc=James.Bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.