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 17:43:25 +0100	[thread overview]
Message-ID: <3C3B21AD.6080600@evision-ventures.com> (raw)
In-Reply-To: <45B36A38D959B44CB032DA427A6E1064012812AD@cceexc18.americas.cpqcorp.net>

Cameron, Steve wrote:

>Martin Dalecki (dalecki@evision-ventures.com) wrote:
>
>[...]
>
>>--- linux-old/drivers/scsi/scsi.c	Sat May  4 09:11:44 2002
>>+++ linux/drivers/scsi/scsi.c	Sat May  4 07:49:19 2002
>>@@ -139,25 +139,7 @@
>>  */
>> unsigned int scsi_logging_level;
>> 
>>-const char *const scsi_device_types[MAX_SCSI_DEVICE_CODE] =
>>-{
>>-	"Direct-Access    ",
>>-	"Sequential-Access",
>>-	"Printer          ",
>>-	"Processor        ",
>>-	"WORM             ",
>>-	"CD-ROM           ",
>>-	"Scanner          ",
>>
>[...etc...]
>
>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 ;-).


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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-08 16:15 PATCH 2.5.2-pre9 scsi cleanup Cameron, Steve
2002-01-08 16: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 17:19 Cameron, Steve
2002-01-08 18: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=3C3B21AD.6080600@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