From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath: Remove EEPROM dump functions
Date: Mon, 23 Jul 2012 10:50:54 +0200 [thread overview]
Message-ID: <500D106E.50500@openwrt.org> (raw)
In-Reply-To: <20492.53472.318382.889445@gargle.gargle.HOWL>
On 2012-07-23 6:19 AM, Sujith Manoharan wrote:
> This can be done from userspace.
>
> Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
I think we should keep this code until we have a proper user space
replacement, I've been using it for debugging a number of times.
The qca-swiss-army-knife patch that you posted is missing quite a bit of
stuff (AR9003 support, HTC support).
- Felix
WARNING: multiple messages have this Message-ID (diff)
From: Felix Fietkau <nbd@openwrt.org>
To: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Cc: linville@tuxdriver.com, ath9k-devel@lists.ath9k.org,
linux-wireless@vger.kernel.org
Subject: Re: [ath9k-devel] [PATCH] ath: Remove EEPROM dump functions
Date: Mon, 23 Jul 2012 10:50:54 +0200 [thread overview]
Message-ID: <500D106E.50500@openwrt.org> (raw)
In-Reply-To: <20492.53472.318382.889445@gargle.gargle.HOWL>
On 2012-07-23 6:19 AM, Sujith Manoharan wrote:
> This can be done from userspace.
>
> Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
I think we should keep this code until we have a proper user space
replacement, I've been using it for debugging a number of times.
The qca-swiss-army-knife patch that you posted is missing quite a bit of
stuff (AR9003 support, HTC support).
- Felix
next prev parent reply other threads:[~2012-07-23 8:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 4:19 [ath9k-devel] [PATCH] ath: Remove EEPROM dump functions Sujith Manoharan
2012-07-23 4:19 ` Sujith Manoharan
2012-07-23 8:50 ` Felix Fietkau [this message]
2012-07-23 8:50 ` [ath9k-devel] " Felix Fietkau
2012-07-23 8:54 ` Sujith Manoharan
2012-07-23 8:54 ` Sujith Manoharan
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=500D106E.50500@openwrt.org \
--to=nbd@openwrt.org \
--cc=ath9k-devel@lists.ath9k.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.