Re: [PATCH V4 0/6] Cypress license and firmware update

2018-06-06 Thread Josh Boyer
On Wed, May 30, 2018 at 3:27 AM Chi-Hsien Lin wrote: > > Update Cypress license termination clause and several firmware files. > > Chi-Hsien Lin (6): > Update Cypress license termination clause > brcm: update firmware for bcm43430 sdio > brcm: update firmware for bcm43340 sdio > brcm:

RE: [EXTERNAL] Re: [RFT 3/6] wlcore: Add support for runtime PM

2018-06-06 Thread Reizer, Eyal
> > * Tony Lindgren [180605 04:22]: > > > * Reizer, Eyal [180603 06:07]: > > > > I have noticed the following recovery a couple of times on my setup > > when the board was > > > > just sitting for a long time with just pings > > > > It starts with a firmware recovery started from the interrupt

[PATCH 2/3] wireless-drivers: use BIT_ULL for NL80211_STA_INFO_* attribute types

2018-06-06 Thread Omer Efrat
Since 'filled' member in station_info changed to u64, BIT_ULL macro should be used with NL80211_STA_INFO_* attribute types instead of BIT. The BIT macro uses unsigned long type which some architectures handle as 32bit and this results in compilation warnings such as:

[PATCH 3/3] staging: use BIT_ULL for NL80211_STA_INFO_* attribute types

2018-06-06 Thread Omer Efrat
Since 'filled' member in station_info changed to u64, BIT_ULL macro should be used with NL80211_STA_INFO_* attribute types instead of BIT. The BIT macro uses unsigned long type which some architectures handle as 32bit and this results in compilation warnings such as:

[PATCH 1/3] net: use BIT_ULL for NL80211_STA_INFO_* attribute types

2018-06-06 Thread Omer Efrat
Since 'filled' member in station_info changed to u64, BIT_ULL macro should be used with NL80211_STA_INFO_* attribute types instead of BIT. The BIT macro uses unsigned long type which some architectures handle as 32bit and this results in compilation warnings such as:

proszę, chcę z tobą porozmawiać

2018-06-06 Thread KATIE

Re: How to let devcoredump know data has been read?

2018-06-06 Thread Ben Greear
On 06/05/2018 03:53 PM, Brian Norris wrote: Hi, On Tue, Jun 05, 2018 at 03:27:28PM -0700, Ben Greear wrote: I have been testing ath10k on 4.16, which uses the devcoredump API to notify about dumps. I am able to see the binary crash dump at /sys/class/devcoredump/devcd2/data, for instance, but

Re: How to let devcoredump know data has been read?

2018-06-06 Thread Arend van Spriel
On 6/6/2018 7:04 PM, Ben Greear wrote: On 06/05/2018 03:53 PM, Brian Norris wrote: Hi, On Tue, Jun 05, 2018 at 03:27:28PM -0700, Ben Greear wrote: I have been testing ath10k on 4.16, which uses the devcoredump API to notify about dumps. I am able to see the binary crash dump at

Re: How to let devcoredump know data has been read?

2018-06-06 Thread Arend van Spriel
On 6/6/2018 12:53 AM, Brian Norris wrote: Unfortunately, devcoredump is a bit lacking in documentation. Arend was writing a bit for the new trigger mechanism at least. I did indeed write ABI doc for user-space trigger mechanism and you brought up the need to have ABI doc for devcoredump. I