mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Amol Lad <amol@verismonetworks.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers/scsi/mca_53c9x.c : save_flags()/cli() removal
Date: Wed, 08 Nov 2006 11:06:41 +0530	[thread overview]
Message-ID: <1162964201.22062.178.camel@amol.verismonetworks.com> (raw)
In-Reply-To: <1162945152.3625.2.camel@mulgrave.il.steeleye.com>

On Wed, 2006-11-08 at 09:19 +0900, James Bottomley wrote:
> On Tue, 2006-11-07 at 12:53 -0800, Andrew Morton wrote:
> 
> > hm.  How do we find out if this works?
> 
> I'm not sure anyone has this type of HW anymore.  It was the original
> SCSI chip for the old MCA based IBM PC.  I can dig through my hardware
> bins to see if I have a card, but I don't think so.

The only way I see is the code review. 

Most of the drivers using save_flags()/cli() interfaces are not in use
anymore (such as drivers/char/riscom8.c). There are two possibilities:
1. Remove such drivers from kernel
2. Fix them

This would mean we can remove cli()/sti()/save_flags() interfaces from
the kernel so that any new development does not uses them accidently

> 
> > If it _does_ work then we can now remove the Kconfig BROKEN_ON_SMP dependency
> > for this driver.
> 
> Theoretically, yes ... practically I don't think there was an SMP box
> produced with this chip.
> 
> James
> 
> 
> 


  reply	other threads:[~2006-11-08  5:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 12:42 Amol Lad
2006-11-07 20:53 ` Andrew Morton
2006-11-08  0:19   ` James Bottomley
2006-11-08  5:36     ` Amol Lad [this message]
2006-11-08 15:36     ` Alan Cox
2006-11-07 22:29 ` Christoph Hellwig
2006-11-08  5:26   ` Amol Lad
  -- strict thread matches above, loose matches on Subject: below --
2006-11-07  6:51 Amol Lad
2006-10-16  6:49 [PATCH] drivers/scsi/mca_53c9x.c: " Amol Lad

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=1162964201.22062.178.camel@amol.verismonetworks.com \
    --to=amol@verismonetworks.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®