mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "J.E.J. Bottomley" <James.Bottomley@steeleye.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: Christoph Hellwig <hch@lst.de>,
	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 13:25:29 -0600	[thread overview]
Message-ID: <200211201925.gAKJPTx03466@localhost.localdomain> (raw)
In-Reply-To: Message from Patrick Mansfield <patmans@us.ibm.com>  of "Wed, 20 Nov 2002 11:10:16 PST." <20021120111016.A20388@eng2.beaverton.ibm.com>

patmans@us.ibm.com said:
> It is in hardirq.h, arch specific, 11 of the 20 hardirq.h files would
> need the change (they reference kernel_locked) to include smp_lock.h.

> 665 files include smp_lock.h 89  files include hardirq.h 32  files
> include both

> So, should I change the arch hardirq.h files to include smp_lock.h, or
> just add smp_lock.h to scsi_lib.c? 

That magnitude of change needs to go in through the header files project.  
I'll just apply the smp_lock.h in scsi_lib fix to the scsi tree for now.  They 
can always take it out again for the proper fix.

James



      reply	other threads:[~2002-11-20 19:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021117235449.B9824@lst.de>
     [not found] ` <20021120084709.A18453@eng2.beaverton.ibm.com>
2002-11-20 17:50   ` Christoph Hellwig
2002-11-20 19:10     ` Patrick Mansfield
2002-11-20 19:25       ` J.E.J. Bottomley [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=200211201925.gAKJPTx03466@localhost.localdomain \
    --to=james.bottomley@steeleye.com \
    --cc=hch@lst.de \
    --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 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®