public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: "Cameron, Steve" <Steve.Cameron@compaq.com>
Cc: linux-kernel@vger.kernel.org, "White,
	Charles" <Charles.White@compaq.com>
Subject: Re: PATCH 2.5.2-pre9 scsi cleanup
Date: Tue, 08 Jan 2002 19:43:08 +0100	[thread overview]
Message-ID: <3C3B3DBC.9070801@evision-ventures.com> (raw)
In-Reply-To: <45B36A38D959B44CB032DA427A6E10640167CF1C@cceexc18.americas.cpqcorp.net>

Cameron, Steve wrote:

>Martin Dalecki [mailto:dalecki@evision-ventures.com] wrote,
>regarding removal of scsi_device_types[] from drivers/scsi/scsi.c
>
>>Cameron, Steve wrote:
>>
>[...]
>
>>>Hmmm, I was using that.... (In, for example, 
>>>the cciss patch here: http://www.geocities.com/smcameron 
>>>It's not any big deal, though.)
>>>
>>Precisely this "not any big deal" is the point: It was the wrong 
>>approach to a trivial problem ;-).
>>
>
>So what's the right approach?  I can invent my own easily enough, 
>but each driver doing its own thing doesn't seem right.  I assumed 
>that it was in scsi.c foi common usage, so each driver that wanted 
>to say, use these device type strings in diagnostic messages or 
>some such wouldn't have to reinvent this wheel, and so all the 
>drivers would consistently use the same names.  Will it be 
>replaced with something else?
>
>Just want to know so I don't waste (even more :-) time 
>doing something dumb.
>

Please just case in the ->type enum. And if you wan't to provide special 
messages, well
then please do it yourself, the removal showed, that nearly no one 
driver used the generic
stuff, so it wasn't trully generic at all. (It should be handled by some 
userlevel stuff anyway...)



  reply	other threads:[~2002-01-08 18:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-08 17:19 PATCH 2.5.2-pre9 scsi cleanup Cameron, Steve
2002-01-08 18:43 ` Martin Dalecki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-09  5:01 Douglas Gilbert
2002-01-09  9:28 ` Martin Dalecki
2002-01-08 16:15 Cameron, Steve
2002-01-08 16:43 ` Martin Dalecki
2002-01-01 22:15 NFS "dev_t" issues Linus Torvalds
2002-01-08  9:29 ` PATCH 2.5.2-pre9 scsi cleanup Martin Dalecki
2002-01-09  4:05   ` GOTO Masanori

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=3C3B3DBC.9070801@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=Charles.White@compaq.com \
    --cc=Steve.Cameron@compaq.com \
    --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