From: Adrian Bunk <bunk@stusta.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.6 patch] SCSI: misc possible cleanups
Date: Mon, 15 Nov 2004 06:02:32 +0100 [thread overview]
Message-ID: <20041115050232.GB2235@stusta.de> (raw)
In-Reply-To: <1100494253.24811.9.camel@mulgrave>
On Sun, Nov 14, 2004 at 10:50:46PM -0600, James Bottomley wrote:
> On Sun, 2004-11-14 at 20:04, Adrian Bunk wrote:
> > This patch below does:
> > - remove unused code
>
> Erm, some of the code you're trying to remove was recently added as
> enablers for fibre channel drivers, like this:
>
> [...]
>
> > drivers/scsi/scsi_transport_fc.c | 202 ------------------------------
>
> It's really not safe to remove code without understanding why it's there
> in the first place.
That's exactly why I wrote:
<-- snip -->
It is meant for review and not for being applied immediately.
It should simply demonstrate with users are possible with the current
in-kernel users today.
<-- snip -->
OK, the last wasn't a correct sentence.
I wanted to say:
It should simply demonstrate with changes are possible with the current
in-kernel users.
> James
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-11-15 5:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 2:04 [2.6 patch] SCSI: misc possible cleanups Adrian Bunk
2004-11-15 4:50 ` James Bottomley
2004-11-15 5:02 ` Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-15 13:57 James.Smart
2004-11-15 13:57 ` James.Smart
2004-11-15 16:22 ` Adrian Bunk
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=20041115050232.GB2235@stusta.de \
--to=bunk@stusta.de \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.