Home
last modified time | relevance | path

Searched hist:"435 c1610f46dc4d86a6633adb037b18109e6ffdc" (Results 1 – 12 of 12) sorted by relevance

/openbmc/linux/drivers/net/wireless/ath/ath9k/
H A Dar9002_calib.cdiff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering

Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after
REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that
makes keeping those ops separate rather pointless, as it only increases
code size and line number counts.

Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
H A Dar9002_phy.cdiff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering

Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after
REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that
makes keeping those ops separate rather pointless, as it only increases
code size and line number counts.

Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
H A Deeprom_4k.cdiff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering

Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after
REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that
makes keeping those ops separate rather pointless, as it only increases
code size and line number counts.

Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
H A Dar9002_hw.cdiff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering

Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after
REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that
makes keeping those ops separate rather pointless, as it only increases
code size and line number counts.

Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
H A Dani.cdiff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering

Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after
REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that
makes keeping those ops separate rather pointless, as it only increases
code size and line number counts.

Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
H A Dcalib.cdiff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering

Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after
REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that
makes keeping those ops separate rather pointless, as it only increases
code size and line number counts.

Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
H A Dmac.cdiff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering

Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after
REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that
makes keeping those ops separate rather pointless, as it only increases
code size and line number counts.

Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
H A Dar5008_phy.cdiff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering

Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after
REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that
makes keeping those ops separate rather pointless, as it only increases
code size and line number counts.

Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
H A Dhtc_drv_init.cdiff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering

Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after
REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that
makes keeping those ops separate rather pointless, as it only increases
code size and line number counts.

Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
H A Dhw.hdiff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering

Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after
REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that
makes keeping those ops separate rather pointless, as it only increases
code size and line number counts.

Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
H A Dhw.cdiff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering

Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after
REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that
makes keeping those ops separate rather pointless, as it only increases
code size and line number counts.

Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
/openbmc/linux/drivers/net/wireless/ath/
H A Dath.hdiff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering

Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after
REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that
makes keeping those ops separate rather pointless, as it only increases
code size and line number counts.

Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>