mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: scameron@beardog.cca.cpqcorp.net
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	scameron@beardog.cca.cpqcorp.net, mike.miller@hp.com
Subject: Re: HP (Compaq) Smart Array 5xxx controller SCSI driver
Date: Thu, 24 Jul 2008 08:30:12 -0500	[thread overview]
Message-ID: <20080724133012.GH8833@beardog.cca.cpqcorp.net> (raw)
In-Reply-To: <20080724101953R.fujita.tomonori@lab.ntt.co.jp>

On Thu, Jul 24, 2008 at 10:32:45AM +0900, FUJITA Tomonori wrote:
> CC'ed linux-scsi, why did you drop it?

You mean my SCSI cciss driver?  For a few reasons:

At the time, it was just kind of a learning exercise, and I
didn't see it as supplanting the existing driver.  I didn't know
enough about udev to know that a smooth transition process
was perhaps possible, and it seemed very disruptive.  And,
seeing as how I work for HP, it isn't exactly within my
authority to just decide by myself the course the driver
development should take.  Paradoxically, if a person works
for a company that has nothing to do with the driver, one
has more freedom to do whatever one wants with the code.

With help from udev it is less disruptive, but I'm still unsure
about how smoothly such a change will fit in with the installation 
process of various distributions.

I will see if management here will let me send you the patches 
from when I last looked at this, which was a little over a year ago.
(2.6.20 timeframe), not necessarily to use as is, but in case
maybe it helps to see how somebody else proceeded. 

As for the patches I mentioned which were previously ignored
for improving how the current cciss SCSI code handled hot 
plogging, if you're curious about that, check here:

http://marc.info/?l=linux-scsi&m=120213565000426&w=4

A change like that becomes more important if logical drives
are exposed through the scsi layer.

-- steve


  reply	other threads:[~2008-07-24 13:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22 17:57 scameron
2008-07-24  1:32 ` FUJITA Tomonori
2008-07-24 13:30   ` scameron [this message]
2008-07-24 13:44     ` FUJITA Tomonori
2008-07-24 13:54       ` scameron
2008-07-24 15:00       ` Miller, Mike (OS Dev)
2008-07-24 15:06         ` FUJITA Tomonori
2008-08-07 19:04           ` Miller, Mike (OS Dev)
2008-08-08  1:07             ` FUJITA Tomonori
2008-08-08 15:32               ` Miller, Mike (OS Dev)
2008-07-24 17:47         ` Andrew Patterson
2008-07-24 16:02       ` scameron
     [not found] <20080722175537.GB8833@beardog.cca.cpqcorp.net>
2008-07-23 15:50 ` scameron
2008-07-24  1:32   ` FUJITA Tomonori

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=20080724133012.GH8833@beardog.cca.cpqcorp.net \
    --to=scameron@beardog.cca.cpqcorp.net \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mike.miller@hp.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®