From: David Miller <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.
Date: Sun, 21 Sep 2008 16:48:29 -0700 (PDT) [thread overview]
Message-ID: <20080921.164829.156985548.davem@davemloft.net> (raw)
In-Reply-To: <20080921234403.GA17946@2ka.mipt.ru>
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.
next prev parent reply other threads:[~2008-09-21 23:48 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 17:23 Evgeniy Polyakov
2008-09-21 17:36 ` Michael Buesch
2008-09-21 17:38 ` Evgeniy Polyakov
2008-09-21 18:04 ` Arjan van de Ven
2008-09-21 18:28 ` Evgeniy Polyakov
2008-09-21 18:35 ` Arjan van de Ven
2008-09-21 18:52 ` Wei Weng
2008-09-21 19:20 ` Arjan van de Ven
2008-09-21 19:00 ` Evgeniy Polyakov
2008-09-21 19:14 ` Johannes Berg
2008-09-21 19:38 ` Evgeniy Polyakov
2008-09-21 19:43 ` Arjan van de Ven
2008-09-21 20:20 ` Evgeniy Polyakov
2008-09-21 20:27 ` Arjan van de Ven
2008-09-21 20:57 ` Evgeniy Polyakov
2008-09-21 21:02 ` Arjan van de Ven
2008-09-21 21:05 ` Evgeniy Polyakov
2008-09-21 21:14 ` Arjan van de Ven
2008-09-21 21:43 ` Denys Fedoryshchenko
2008-09-21 22:07 ` Evgeniy Polyakov
2008-09-21 22:15 ` Denys Fedoryshchenko
2008-09-21 23:46 ` Evgeniy Polyakov
2008-09-21 23:27 ` Marcel Holtmann
2008-09-22 0:00 ` Evgeniy Polyakov
2008-09-21 22:38 ` Alan Cox
2008-09-21 23:44 ` Evgeniy Polyakov
2008-09-21 23:48 ` David Miller [this message]
2008-09-22 0:18 ` Evgeniy Polyakov
2008-09-22 14:22 ` Bill Davidsen
2008-09-21 20:05 ` Cyrill Gorcunov
2008-09-21 20:26 ` Evgeniy Polyakov
2008-09-21 20:35 ` Cyrill Gorcunov
2008-09-21 21:06 ` Evgeniy Polyakov
2008-09-21 19:57 ` Alan Cox
2008-09-21 21:10 ` Evgeniy Polyakov
2008-09-26 5:56 ` Evgeniy Polyakov
2008-09-21 19:35 ` Marcel Holtmann
2008-09-21 21:12 ` Evgeniy Polyakov
2008-09-21 22:45 ` Matthew Garrett
2008-09-21 22:42 ` Matthew Garrett
2008-09-21 23:45 ` Evgeniy Polyakov
2008-09-22 16:21 ` [Ipw2100-devel] " Kenneth Crudup
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=20080921.164829.156985548.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=ipw2100-devel@lists.sourceforge.net \
--cc=jgarzik@pobox.com \
--cc=johannes@sipsolutions.net \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=yi.zhu@intel.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
all inboxes | Powered by JetHome®