From: Matthew Wilcox <matthew@wil.cx>
To: Luben Tuikov <ltuikov@yahoo.com>,
James Bottomley <James.Bottomley@SteelEye.com>,
Luben Tuikov <luben_tuikov@adaptec.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2.6.13 14/14] sas-class: SCSI Host glue
Date: Mon, 12 Sep 2005 10:08:05 -0600 [thread overview]
Message-ID: <20050912160805.GC32395@parisc-linux.org> (raw)
In-Reply-To: <20050911093847.GA5429@infradead.org>
On Sun, Sep 11, 2005 at 10:38:47AM +0100, Christoph Hellwig wrote:
> On Fri, Sep 09, 2005 at 09:12:18PM -0700, Luben Tuikov wrote:
> > I long for the days of the previous maintainer. Had it not been
> > for him and Andi, we may have never had scsi commands from a slab,
> > scsi_done queue, done_q softirq processing, scsi timer hook, etc.
> > Of course back then Splentec wasn't your payrol company, but there
> > was some common sense present in linux-scsi.
>
> Could you please stop this bullshit spreading now, thanks?
I meant to reply to Luben's original, but I deleted it in disgust.
As the person who converted SCSI from the old bottom-half completion
processing first to a tasklet and then to a softirq, I'd like to refute
at least part of this allegation. I didn't do it in order to improve
SCSI particularly, satisfy Splentec (who are they?), or prove a point.
I did it because I wanted to remove the old bottom-half mechanism and
SCSI was one of the remaining users. That required me to learn a bit
about the SCSI stack and I got sucked in. BTW, I believe at that time,
James had alreeady taken over maintenance. I'm not actually sure who
the previous maintainer was -- was it Eric Biederman?
A colleague asked me to summarise the current dispute. I said that
Luben's point was that nobody else understood SCSI. Everybody else's
point was that Luben doesn't understand Linux kernel development. Luben,
I think you need to shut up, accept advice, stop trying to do everything
in your own driver, and stop trying to have private conversations.
Just discuss things on linux-scsi dispassionately. There's no hidden
agenda to get you or your company. But you are pissing people off,
and very soon there *will* be because of your behaviour.
next prev parent reply other threads:[~2005-09-12 16:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 19:42 [PATCH 2.6.13 14/14] sas-class: SCSI Host glue Luben Tuikov
2005-09-09 23:35 ` James Bottomley
2005-09-10 4:12 ` Luben Tuikov
2005-09-10 13:08 ` Arjan van de Ven
2005-09-12 13:55 ` Luben Tuikov
2005-09-12 14:13 ` Jörn Engel
2005-09-12 18:46 ` Luben Tuikov
2005-09-12 18:46 ` Luben Tuikov
2005-09-10 14:30 ` Rik van Riel
2005-09-10 20:20 ` Alan Cox
2005-09-11 9:40 ` Christoph Hellwig
2005-09-13 12:41 ` Luben Tuikov
2005-09-11 3:56 ` ak
2005-09-11 13:41 ` James Bottomley
2005-09-12 17:12 ` Luben Tuikov
2005-09-12 17:55 ` Alan Cox
2005-09-12 13:56 ` Luben Tuikov
2005-09-11 9:38 ` Christoph Hellwig
2005-09-12 16:08 ` Matthew Wilcox [this message]
2005-09-12 19:07 ` Luben Tuikov
2005-09-12 19:55 ` Matthew Wilcox
2005-09-12 23:51 ` Stefan Richter
2005-09-12 22:00 ` Luben Tuikov
2005-09-13 15:40 ` Matthew Wilcox
2005-09-14 5:56 ` Sergey Panov
2005-09-14 10:37 ` Christoph Hellwig
2005-09-14 10:53 ` Jeff Garzik
2005-09-14 12:59 ` Luben Tuikov
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=20050912160805.GC32395@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ltuikov@yahoo.com \
--cc=luben_tuikov@adaptec.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;
as well as URLs for NNTP newsgroup(s).