public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: Jeff Garzik <jeff@garzik.org>
Cc: ltuikov@yahoo.com, James Bottomley <James.Bottomley@SteelEye.com>,
	Alexis Bruemmer <alexisb@us.ibm.com>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] aic94xx: Hotplug ex_change_count race fix
Date: Tue, 03 Oct 2006 22:29:05 -0400	[thread overview]
Message-ID: <45231C71.2060306@torque.net> (raw)
In-Reply-To: <4522D3C0.6060706@garzik.org>

Jeff Garzik wrote:
> Luben Tuikov wrote:
>> You have to make a clarification: "the way event processing works" means
>> the way it works after you removed all of event processing from my
>> code the
>> way I wrote it, and added a very naive "event processing" if it can be
>> called that.
>>
>> Event processing seems to work just fine with my version of my code the
>> way I maintain it, and the way you had it originally on this list.
>>
>> Just clarifying in case someone gets confused reading the code.
> 
> And we were all waiting breathlessly for this clarification too, I
> assure you.
> 
> In the dictionary under the phrase "sore loser", it says "see: Luben"

I work with both drivers and provide feedback to their
maintainers. IMO the loser is "linux".

One handicap the official driver has is the SATL it has
decided to use.

... back to my redmond os for testing ...

Doug Gilbert



  reply	other threads:[~2006-10-04  2:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 22:05 [PATCH] aic94xx: Hotplug ex_change_count race fix Alexis Bruemmer
2006-10-03 14:19 ` James Bottomley
2006-10-03 15:30   ` Alexis Bruemmer
2006-10-04 23:52     ` malahal
2006-10-03 20:52   ` Luben Tuikov
2006-10-03 21:18     ` Jeff Garzik
2006-10-04  2:29       ` Douglas Gilbert [this message]
2006-10-04  7:39       ` 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=45231C71.2060306@torque.net \
    --to=dougg@torque.net \
    --cc=James.Bottomley@SteelEye.com \
    --cc=alexisb@us.ibm.com \
    --cc=jeff@garzik.org \
    --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