Return-path: <linux-wireless-owner@vger.kernel.org>
Received: from mail-iw0-f180.google.com ([209.85.223.180]:47521 "EHLO
	mail-iw0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1758134AbZKDUEk (ORCPT
	<rfc822;linux-wireless@vger.kernel.org>);
	Wed, 4 Nov 2009 15:04:40 -0500
Received: by iwn10 with SMTP id 10so5226716iwn.4
        for <linux-wireless@vger.kernel.org>; Wed, 04 Nov 2009 12:04:45 -0800 (PST)
MIME-Version: 1.0
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
Date: Wed, 4 Nov 2009 12:04:25 -0800
Message-ID: <43e72e890911041204n55b54f8iace79938b40baa32@mail.gmail.com>
Subject: pci_set_mwi() and ath5k
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: ath5k-devel@lists.ath5k.org, Matthew Wilcox <matthew@wil.cx>,
	Stephen Hemminger <shemminger@vyatta.com>
Content-Type: text/plain; charset=UTF-8
Sender: linux-wireless-owner@vger.kernel.org
List-ID: <linux-wireless.vger.kernel.org>

Curious if anyone recalls the issues seen with enabling MWI on ath5k.
I could have sworn there was some discussion on this but for the life
of me I cannot find it.

  Luis