RE: [PATCH v4 1/2] mmc: API for accessing host supported maximum segment count and size

Hi Ulf, > From: Amitkumar Karwar [mailto:akar...@marvell.com] > Sent: Thursday, June 16, 2016 2:53 PM > To: linux-wireless@vger.kernel.org > Cc: Nishant Sarmukadam; Wei-Ning Huang; linux-...@vger.kernel.org; > Cathy Luo; Xinming Hu; Amitkumar Karwar > Subject: [PATCH v4 1/2] mmc: API for accessing

Re: [PATCH 2/2] net: wireless: fix to uses struct

On 21-12-2016 23:23, Ozgur Karatas wrote: > > The patch fixed to struct uses in reg.c, I think doesn't need to be use to > "struct". > There is dataype not have to logical link and each is different definitons. > > I'm undecided on this patch. I compiled and didn't to errors. There must be s

Question: Packet drop criterion

Hello everyone, I would like to modify the retry threshold for dropping a packet using mesh mode. I tried with iw iw phy set retry [short ] [long ] with short and long limits equal to 10 first and later 5, but I couldn't tell any effect. I'm checking by adding a printk in `status.c` and man

pull-request: wireless-drivers 2016-12-22

Hi Dave, before the holidays a really small pull request for 4.10. I just want to have the regressions in rtlwifi and ath9k fixed quickly so I send this earlier than I normally would. Please let me know if there are any problems. Kalle The following changes since commit ad688cdbb076833ba17fc655

Re: [PATCH] ath10k: merge extended peer info data with existing peers info

Hi Christian, once again sorry for the delay > > On Monday, December 19, 2016 10:19:57 PM CET Mohammed Shafi Shajakhan wrote: > > On Sat, Dec 17, 2016 at 06:46:34PM +0100, Christian Lamparter wrote: > > > The 10.4 firmware adds extended peer information to the > > > firmware's statistics payload

Re: pull-request: wireless-drivers 2016-12-22

From: Kalle Valo Date: Thu, 22 Dec 2016 17:11:27 +0200 > before the holidays a really small pull request for 4.10. I just want to > have the regressions in rtlwifi and ath9k fixed quickly so I send this > earlier than I normally would. > > Please let me know if there are any problems. Pulled, t

Re: [PATCH] ath10k: merge extended peer info data with existing peers info

Hello Shafi, On Thursday, December 22, 2016 9:18:01 PM CET Mohammed Shafi Shajakhan wrote: > > On Monday, December 19, 2016 10:19:57 PM CET Mohammed Shafi Shajakhan wrote: > > > On Sat, Dec 17, 2016 at 06:46:34PM +0100, Christian Lamparter wrote: > > > > The 10.4 firmware adds extended peer inform

Re: [PATCH 1/3] NFC: trf7970a: add device tree option for 27MHz clock

On Mon, Dec 19, 2016 at 5:23 PM, Geoff Lansberry wrote: > I can make that change, however, I worry that it may be a bit > misleading, since there are only two supported clock frequencies, but > a number like that to me implies that it could be set to any number > you want. I'm new at this, and s

Re: Question: Packet drop criterion

Am 22.12.2016 um 13:34 schrieb Ferran Quer i Guerrero: > Hello everyone, > > I would like to modify the retry threshold for dropping a packet using > mesh mode. I tried with iw > > iw phy set retry [short ] [long ] > > with short and long limits equal to 10 first and later 5, but I couldn't

[PATCH] ath10k: recal the txpower when removing interface

From: Ryan Hsu The txpower is being recalculated when adding interface to make sure txpower won't overshoot the spec, and when removing the interface, the txpower should again to be recalculated to restore the correct value from the active interface list. Following is one of the scenario

Re: [PATCH v3 1/3] NFC: trf7970a: add device tree option for 27MHz clock

On Wed, Dec 21, 2016 at 11:18:32PM -0500, Geoff Lansberry wrote: > The TRF7970A has configuration options to support hardware designs > which use a 27.12MHz clock. This commit adds a device tree option > 'clock-frequency' to support configuring the this chip for default > 13.56MHz clock or the opti

Re: [PATCH v3 2/3] NFC: trf7970a: Add device tree option of 1.8 Volt IO voltage

On Wed, Dec 21, 2016 at 11:18:33PM -0500, Geoff Lansberry wrote: > The TRF7970A has configuration options for supporting hardware designs > with 1.8 Volt or 3.3 Volt IO. This commit adds a device tree option, > using a fixed regulator binding, for setting the io voltage to match > the hardware co

[PATCH] ath10k: ignore configuring the incorrect board_id

From: Ryan Hsu With command to get board_id from otp, in the case of following boot get otp board id result 0x board_id 0 chip_id 0 boot using board name 'bus=pci,bmi-chip-id=0,bmi-board-id=0" ... failed to fetch board data for bus=pci,bmi-chip-id=0,bmi-board-id=0 from ath10k/Q

[PATCH] brcmfmac: fix spelling mistakes on "Ivalid"

From: Colin Ian King Trivial fixes to spelling mistake "Ivalid" to "Invalid" in brcmf_err error messages. Signed-off-by: Colin Ian King --- drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/wireless/b

Re: ath10k mesh error 80MHz channel

On Wednesday 21 December 2016 08:51 PM, Matteo Grandi wrote: > Hi all again, just an update to the previous message: > > looking at iw list I found this situation: > > Frequencies: > * 5180 MHz [36] (20.0 dBm) > * 5200 MHz [40] (20.0 dBm) > * 5220 MHz

Копия: Аll-Nаturаl Joint Рain Relief fоr Y0ur Рet

Это копия сообщения, которое вы отправили Контакты через ООО Авалон Это письмо отправлено с сайта http://avalon-tuapse.ru/ от: KoLMissotrolo Our реts can't sреаk for thеmsеlvеs, but yоu саn tell whеn yоur fаmily friеnd is hurting. Pеrhарs they'rе hаving a bit of a difficult timе getting uр aftе