Date: Sun, 21 Sep 2008 16:48:29 -0700 (PDT)
Message-Id: <20080921.164829.156985548.davem@davemloft.net>
To: johnpol@2ka.mipt.ru
Cc: alan@lxorguk.ukuu.org.uk, arjan@infradead.org,
	johannes@sipsolutions.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, ipw2100-devel@lists.sourceforge.net,
	linux-wireless@vger.kernel.org, yi.zhu@intel.com,
	reinette.chatre@intel.com, jgarzik@pobox.com,
	linville@tuxdriver.com
Subject: Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling firmware
 restart.
From: David Miller <davem@davemloft.net>
In-Reply-To: <20080921234403.GA17946@2ka.mipt.ru>
References: <20080921205706.GA24545@2ka.mipt.ru>
	<20080921233819.32714483@lxorguk.ukuu.org.uk>
	<20080921234403.GA17946@2ka.mipt.ru>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Sender: linux-wireless-owner@vger.kernel.org


Evgeniy, you're bordering on being an asshole, if not actually
being one.

If you behaved this way for a bug I was responsible for, I would
absolutely ignore you until you settled down and started to behave
more reasonably.

You're acting like a bomb which is about to explode, which is probably
why the actual Intel maintainers for this driver don't want to touch
you with a ten foot pole.  You're being volatile and extremely
unpleasant to interact with about this issue.

The Intel folks replying to you right now are general Intel linux
folks who are trying to help you, not the driver maintainers who can
look into the firmware and attack that angle.  So give them A FUCKING
BREAK!

Getting the OOPS to kerneloops.org is the way forward and will help
your cause, whether you believe it or not.