On Thu, Feb 22, 2018 at 02:28:59PM -0600, Larry Finger wrote:
> In commit c713fb071edc ("rtlwifi: rtl8821ae: Fix connection lost problem
> correctly") a problem in rtl8821ae that caused loss of signal was fixed.
> That same problem has now been reported for rtl8723be. Accordingly,
> the ASPM L1 lat
Hi Sebastian,
On Thu, Feb 22, 2018 at 6:09 PM, Sebastian Gottschall
wrote:
> Am 22.02.2018 um 23:17 schrieb Steve deRosier:
>>
>> On Thu, Feb 22, 2018 at 3:15 AM, wrote:
>>>
>>> From: Sebastian Gottschall
>>>
>>> Adds LED and GPIO Control support for 988x, 9887, 9888, 99x0, 9984 based
>>> chip
Am 22.02.2018 um 23:17 schrieb Steve deRosier:
On Thu, Feb 22, 2018 at 3:15 AM, wrote:
From: Sebastian Gottschall
Adds LED and GPIO Control support for 988x, 9887, 9888, 99x0, 9984 based
chipsets with on chipset connected led's
using WMI Firmware API.
The LED device will get available named
On Thu, Feb 22, 2018 at 3:15 AM, wrote:
> From: Sebastian Gottschall
>
> Adds LED and GPIO Control support for 988x, 9887, 9888, 99x0, 9984 based
> chipsets with on chipset connected led's
> using WMI Firmware API.
> The LED device will get available named as "ath10k-phyX" at sysfs and can be
In commit c713fb071edc ("rtlwifi: rtl8821ae: Fix connection lost problem
correctly") a problem in rtl8821ae that caused loss of signal was fixed.
That same problem has now been reported for rtl8723be. Accordingly,
the ASPM L1 latency has been increased from 0 to 7 to fix the instability.
Signed-of
On Thu, 2018-02-22 at 15:19 -0500, David Miller wrote:
> From: Johannes Berg
> Date: Thu, 22 Feb 2018 21:16:18 +0100
>
> > Wireless is slow ... but we're preparing for HE (802.11ax),
> > so I guess soon we'll have a big chunk of work coming :-)
>
> I wondered where you guys have been hiding :-)
From: Johannes Berg
Date: Thu, 22 Feb 2018 21:16:18 +0100
> Wireless is slow ... but we're preparing for HE (802.11ax),
> so I guess soon we'll have a big chunk of work coming :-)
I wondered where you guys have been hiding :-)
> Please pull and let me know if there's any problem.
Pulled, thank
From: Johannes Berg
Date: Thu, 22 Feb 2018 21:08:39 +0100
> A bunch of fixes, including the nla_put_string() issue
> just in from Kees. Otherwise nothing really super urgent
> or interesting.
>
> Please pull and let me know if there's any problem.
Pulled.
Thanks for taking care of that NLA_STR
Hi Dave,
Wireless is slow ... but we're preparing for HE (802.11ax),
so I guess soon we'll have a big chunk of work coming :-)
Please pull and let me know if there's any problem.
Thanks,
johannes
The following changes since commit 91e6dd8284256ef62b43b78da6e7684e4f06ac2f:
ipmr: Fix ptrdiff
Hi Dave,
A bunch of fixes, including the nla_put_string() issue
just in from Kees. Otherwise nothing really super urgent
or interesting.
Please pull and let me know if there's any problem.
Thanks,
johannes
The following changes since commit ba804bb4b72e57374b5f567b783aa0298fba0ce6:
Merge g
From: Johannes Berg
Similar to the ancient commit a5fe8e7695dc ("regulatory: add NUL
to alpha2"), add another byte to alpha2 in the request struct so
that when we use nla_put_string(), we don't overrun anything.
Fixes: 73d54c9e74c4 ("cfg80211: add regulatory netlink multicast group")
Reported-by
Hi Arend,
On Thu, Feb 22, 2018 at 01:17:56PM +0100, Arend van Spriel wrote:
> On 2/21/2018 11:59 PM, Brian Norris wrote:
> > On Wed, Feb 21, 2018 at 11:50:19AM +0100, Arend van Spriel wrote:
> > > Since commit 3c47d19ff4dc ("drivers: base: add coredump driver ops")
> > > it is possible to initiate
Hi all,
I have slotted a 300 Mbps Wireless N PCI Express Adapter into my
PowerMac G5, and it failed
to initialize the driver with an error complaining about the EEPROM.
I disabled the line reading ah->ah_flags |= AH_NO_EEP_SWAP; in
ath9k_of_init(), and this made my card show up and start work
Please ignore this patch series, I will work on review comments and submit
another version later.
Regards,
Ajay
On 2/21/2018 11:59 PM, Brian Norris wrote:
On Wed, Feb 21, 2018 at 11:50:19AM +0100, Arend van Spriel wrote:
Since commit 3c47d19ff4dc ("drivers: base: add coredump driver ops")
it is possible to initiate a device coredump from user-space. This
patch adds support for it adding the .coredump() dr
On Thu, Feb 22, 2018 at 5:44 AM, Kalle Valo wrote:
> Hi linux-firmware maintainers,
>
> here's a pull request for updating ath10k firmwares. Earlier I have been
> submitting these as patches but as the patches got pretty big I decided
> to try using pull requests instead.
Pull requests are easier
From: Sebastian Gottschall
Adds LED and GPIO Control support for 988x, 9887, 9888, 99x0, 9984 based
chipsets with on chipset connected led's
using WMI Firmware API.
The LED device will get available named as "ath10k-phyX" at sysfs and can be
controlled with various triggers.
adds also debugfs i
on 9984 i see these messages with this firmware from time to time
[272972.950788] ath10k_pci :01:00.0: Unknown eventid: 36925
[272982.868922] ath10k_pci :01:00.0: Unknown eventid: 36925
[335550.123780] ath10k_pci :01:00.0: Unknown eventid: 36925
[335550.156332] ath10k_pci :01:00.0
Hi linux-firmware maintainers,
here's a pull request for updating ath10k firmwares. Earlier I have been
submitting these as patches but as the patches got pretty big I decided
to try using pull requests instead.
Please let me know if there are any problems.
Kalle
The following changes since com
This adds printing of TXQ statistics for stations and interfaces when
supplied by the kernel. For stations, another section is added when verbose
mode is enabled; for interfaces, the multicast queue information is always
printed when available.
This is the information also available through debugf
Arend van Spriel writes:
>>> So can we expect some manual in which is described what parameter
>>> should be tweaked based on the retrieved statistics.
>>
>> Heh, not sure I'll promise a whole manual, but I am happy to write a
>> blog post (or wiki page if that's better) explaining what these val
On 22.02.2018 11:23, Claudiu Beznea wrote:
> Hi Dan,
Sorry, I intended to be address this to Ajay,
>
> On 22.02.2018 09:37, Dan Carpenter wrote:
>> On Wed, Feb 21, 2018 at 09:42:10PM +0530, Ajay Singh wrote:
>>> Use existing macro GENMASK to get the bitmask value. Moved the code to
>>> get the b
Hi Dan,
On 22.02.2018 09:37, Dan Carpenter wrote:
> On Wed, Feb 21, 2018 at 09:42:10PM +0530, Ajay Singh wrote:
>> Use existing macro GENMASK to get the bitmask value. Moved the code to
>> get the bitmask value outside the loop, as its only required one time.
>>
>> Signed-off-by: Ajay Singh
>> --
From: Dmitry Lebed
Add wiphy EXT_FEATURE flag to indicate that HW or driver does
all DFS actions by itself.
User-space functionality already implemented in hostapd using
vendor-specific (QCA) OUI to advertise DFS offload support.
Need to introduce generic flag to inform about DFS offload support.
On Thu, Feb 22, 2018 at 02:09:01PM +0530, Ajay Singh wrote:
> Hi Dan,
>
> On Thu, 22 Feb 2018 10:20:58 +0300
> Dan Carpenter wrote:
>
> > On Wed, Feb 21, 2018 at 09:42:09PM +0530, Ajay Singh wrote:
> > > Modified wilc_spi_read_int() by removing unnecessary use of "happened"
> > > variable.
> > >
Hi Dan,
On Thu, 22 Feb 2018 10:20:58 +0300
Dan Carpenter wrote:
> On Wed, Feb 21, 2018 at 09:42:09PM +0530, Ajay Singh wrote:
> > Modified wilc_spi_read_int() by removing unnecessary use of "happened"
> > variable.
> >
> > Signed-off-by: Ajay Singh
> > ---
> > drivers/staging/wilc1000/wilc_sp
Hello Kalle,
> > Friendly advice: you may want to avoid using this footer in emails on
> > the kernel.org mailing lists.
>
> Indeed. Most of the time I don't even reply to mails with such
> disclaimers and patches containing that will be automatically dropped.
Based on our previous experience we
27 matches
Mail list logo