From: Douglas Gilbert <dougg@torque.net>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH 2.5.2-pre9 scsi cleanup
Date: Wed, 09 Jan 2002 00:01:46 -0500 [thread overview]
Message-ID: <3C3BCEB9.B14D20FD@torque.net> (raw)
Martin Dalecki <dalecki@evision-ventures.com>
> The attached patch does the following.
>
> 1. Clean up some ifdef confusion in do_mount
>
> 2. Clean up the scsi code to make ppa.c work.
>
> 3. Clean up some unneccessary unneeded globals from scsi code.
>
> 4. Make a bit more sure, that the minor() and friends end up in
> unsigned int's.
<snip/>
Martin,
Please don't post a omnibus SCSI subsystem patch like this.
Most of the code you are changing is actively maintained.
For example:
- scsi mid-level + sr [Jens Axboe]
- ppa [Tim Waugh]
- sg [me]
Some of us have grown attached to the way 'cat /proc/scsi/scsi'
looks. More importantly, many distributions have scripts that
parse it. GOTO Masanori's <gotom@debian.or.jp> suggestion of
of an exported scsi_device_types() seems a better option.
Also there are 32 SCSI device types (0 to 31) and perhaps
the "unknown"s and those that are missing could be replaced
by scsi_dev_<n> .
Also there is an appropriate newsgroup for this sort of
proposal and it is called: linux-scsi@vger.kernel.org
Doug Gilbert
next reply other threads:[~2002-01-09 5:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 5:01 Douglas Gilbert [this message]
2002-01-09 9:28 ` PATCH 2.5.2-pre9 scsi cleanup Martin Dalecki
-- strict thread matches above, loose matches on Subject: below --
2002-01-08 17:19 Cameron, Steve
2002-01-08 18:43 ` 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=3C3BCEB9.B14D20FD@torque.net \
--to=dougg@torque.net \
--cc=dalecki@evision-ventures.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