Hello Everybody,
With the 4.8-rc3 I use a couple of usb wireless interfaces with
atheros chipset in them. With each of them I don't see all wireles
packets when I put them in monitor mode. The onboard wireless
interface doesnt have this problem.
I did try it with three different wireless usb
As reported by David Binderman, this test is useless as of
if (a < 3) {
/* ... */
} else if (a >= 3) {
/* ... */
}
so this patch removes the second check.
Matthias Beyer (1):
drivers: staging: rtl8723au: hal: Remove pointless test
This patch removes the pointless `else if` test.
Signed-off-by: Matthias Beyer
Reported-by: David Binderman
---
drivers/staging/rtl8723au/hal/rtl8723a_bt-coexist.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 08/23/2016 11:48 AM, Kalle Valo wrote:
QCA9884 is a new chip supported by ath10k. Firmware version is 10.4-3.2-00072.
Typo in the '9884' string I think. Should be 9984?
Thanks,
Ben
--
Ben Greear
Candela Technologies Inc http://www.candelatech.com
Hi,
here's a bigger ath10k firmware update. Support for four new hardware
and smaller updates for existing hardware.
Kalle
---
Kalle Valo (6):
ath10k: QCA4019 hw1.0: add firmware and board files
ath10k: QCA9887 hw1.0: add firmware and board files
ath10k: QCA9888 hw2.0: add
Adding support for new QCA6174 board types.
Signed-off-by: Kalle Valo
---
ath10k/QCA6174/hw2.1/board-2.bin | Bin
ath10k/QCA6174/hw3.0/board-2.bin | Bin
2 files changed, 0 insertions(+), 0 deletions(-)
diff --git a/ath10k/QCA6174/hw2.1/board-2.bin
Commit 97f2645f358b ("tree-wide: replace config_enabled() with
IS_ENABLED()") mostly did away with config_enabled().
This is one of the postponed TODO items as config_enabled() is used
for a tristate option here. Theoretically, config_enabled() is
equivalent to IS_BUILTIN(), but I guess
On 22 August 2016 at 05:40, Wright Feng wrote:
> This message and any attachments may contain Cypress (or its subsidiaries)
> confidential information. If it has been received in error, please advise the
> sender and immediately delete this message.
You are aware you're
On Tue, 23 Aug 2016, SF Markus Elfring wrote:
> > Use get_maintainer to check the status of individual files.
> > If "obsolete", suggest leaving the files alone.
>
> Will another software system like the "kbuild test robot"
> need any more fine-tuning for this change?
It only works on files in
From: Maharaja Kennadyrajan
For 10.4 fw versions, dbglog module id has been extended from u32
to u64, hence this patch fixes the same in the ath10k driver side.
This patch doesn't break the older 10.4 releases. The FW change
is already present in the older FWs.
The struct cfg80211_pmksa defines its bssid field as:
const u8 *bssid;
contrary to struct brcmf_pmksa, which uses:
u8 bssid[ETH_ALEN];
Therefore in brcmf_cfg80211_del_pmksa(), >bssid takes the address
of this field (of type u8**), not the one of its content (which would be
u8*).
On 22/08/16 21:38, Arend Van Spriel wrote:
> On 22-8-2016 15:03, Nicolas Iooss wrote:
>> On 05/08/16 22:34, Nicolas Iooss wrote:
[...]
>>> Fixes: 6c404f34f2bd ("brcmfmac: Cleanup pmksa cache handling code")
>>> Cc: sta...@ger.kernel.org
>
> Ah, so you did something wrong after all :-p. The email
On Mon, Aug 22, 2016 at 18:56:01, Kalle Valo wrote:
> Subject: Re: [PATCH] wlcore: mesh: add zone time sync support
>
> "Mishol, Guy" writes:
>
> > Kalle/Thomas,
> > Thanks for your feedback.
>
> Please don't top most, it makes using patchwork difficult and is
> annoying to the
On 23-08-16 08:59, Kalle Valo wrote:
> Toke Høiland-Jørgensen writes:
>
> This is great work but due to the regressions I'm not sure if this
> will be ready for 4.9. To get more testing time I wonder if we should
> wait for 4.10? IMHO applying this in the end of the
> Use get_maintainer to check the status of individual files.
> If "obsolete", suggest leaving the files alone.
Will another software system like the "kbuild test robot"
need any more fine-tuning for this change?
Regards,
Markus
Toke Høiland-Jørgensen writes:
This is great work but due to the regressions I'm not sure if this
will be ready for 4.9. To get more testing time I wonder if we should
wait for 4.10? IMHO applying this in the end of the cycle is too risky
and we should try to
16 matches
Mail list logo