[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080921140203.4698a2ee@infradead.org>
Date: Sun, 21 Sep 2008 14:02:03 -0700
From: Arjan van de Ven <arjan@...radead.org>
To: Evgeniy Polyakov <johnpol@....mipt.ru>
Cc: Johannes Berg <johannes@...solutions.net>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, ipw2100-devel@...ts.sourceforge.net,
linux-wireless@...r.kernel.org, yi.zhu@...el.com,
reinette.chatre@...el.com, jgarzik@...ox.com,
linville@...driver.com, davem@...emloft.net
Subject: Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling firmware
restart.
On Mon, 22 Sep 2008 00:57:06 +0400
Evgeniy Polyakov <johnpol@....mipt.ru> wrote:
> > > Consider for inclusing for the upcoming kernel to get wider
> > > notifications. Yes, it is not a bugfix, I know.
> >
> > still more complex than needed; a WARN_ON_ONCE() will be enough.
>
> That allows to dump whatever number of warnings you want. The more we
> have, the louder will be customers scream.
artificially increasing numbers isn't going to do that; it just shows
you're more interested in making a stink than in getting something
improved ;(
>
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists