From: Felix Fietkau <nbd@openwrt.org>
To: Sujith Manoharan <sujith@msujith.org>,
John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 07/10] ath9k: Remove ath9k_hw_gettsf32()
Date: Wed, 18 Dec 2013 12:25:28 +0100 [thread overview]
Message-ID: <52B18628.1080607@openwrt.org> (raw)
In-Reply-To: <1387340607-20045-8-git-send-email-sujith@msujith.org>
On 2013-12-18 05:23, Sujith Manoharan wrote:
> From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
>
> It is unnecessary and the value is just a simple,
> direct register read.
>
> Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
I'm using this function in my work-in-progress patches for p2p
multichannel.
Should I switch to using REG_READ in the driver or would you prefer to
drop this patch instead?
- Felix
next prev parent reply other threads:[~2013-12-18 11:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 4:23 [PATCH v2 00/10] ath9k patches Sujith Manoharan
2013-12-18 4:23 ` [PATCH v2 01/10] ath9k: Cleanup spectral scan code Sujith Manoharan
2013-12-18 4:23 ` [PATCH v2 02/10] ath9k: Cleanup ath9k.h Sujith Manoharan
2013-12-18 4:23 ` [PATCH v2 03/10] ath9k: Remove unneeded ref. count initialization Sujith Manoharan
2013-12-18 4:23 ` [PATCH v2 04/10] ath9k: Initialize "switchcomspdt" eeprom field explicitly Sujith Manoharan
2013-12-18 4:23 ` [PATCH v2 05/10] ath9k: Update BaseExtension_1 eeprom structure Sujith Manoharan
2013-12-18 4:23 ` [PATCH v2 06/10] ath9k: Fix regulatory compliance Sujith Manoharan
2013-12-18 4:23 ` [PATCH v2 07/10] ath9k: Remove ath9k_hw_gettsf32() Sujith Manoharan
2013-12-18 11:25 ` Felix Fietkau [this message]
2013-12-18 11:26 ` Sujith Manoharan
2013-12-18 4:23 ` [PATCH v2 08/10] ath9k: Add a delay between RTC reset/clear for AR9003 Sujith Manoharan
2013-12-18 4:23 ` [PATCH v2 09/10] ath9k: Fix RTC reset delay Sujith Manoharan
2013-12-18 4:23 ` [PATCH v2 10/10] ath9k: Use a subroutine for the AR9330 reset WAR 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=52B18628.1080607@openwrt.org \
--to=nbd@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sujith@msujith.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.