From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: ltuikov@yahoo.com
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] libsas: fix error handling
Date: Thu, 21 Feb 2008 09:33:07 -0600 [thread overview]
Message-ID: <1203607987.3208.9.camel@localhost.localdomain> (raw)
In-Reply-To: <541691.92554.qm@web31804.mail.mud.yahoo.com>
On Wed, 2008-02-20 at 21:51 -0800, Luben Tuikov wrote:
> A similar change went into the SAS/SATL layer I support
> shortly after I posted the version which you forked off.
> The git date of the commit is: Tue Feb 7 22:14:54 2006 -0800.
Look, Luben; I don't mind you making an arse of yourself on the mailing
lists; that's about par for the course nowadays.
However, failing to report serious bugs you knew about in your code, and
have known about for two years, is tantamount to sabotage ... especially
when you've been reading the bug reports on the mailing list. I have to
wonder how many more such bugs you've left in the code for users to
find.
> BTW, the problem you're "debugging" may require a protocol
> trace and a sequencer update by Adaptec.
I think you're fully aware that my test rig consists of a couple of SAS
cards and drives donated by IBM and two expanders donated by LSI, plus a
bit of equipment scavenged from Intel. I have no access to
sophisticated tools like protocol analyzers. However, thanks for the
advice and help.
James
next prev parent reply other threads:[~2008-02-21 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 16:07 [PATCH] libsas: fix error handling James Bottomley
2008-02-21 5:51 ` Luben Tuikov
2008-02-21 15:33 ` James Bottomley [this message]
2008-02-22 19:46 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2008-02-22 12:19 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=1203607987.3208.9.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=ltuikov@yahoo.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