Re: [PATCH 6/6] staging: wilc1000: fix line over 80 chars in wilc_spi_clear_int_ext()

On Fri, 16 Feb 2018 20:16:02 +0200 Claudiu Beznea wrote: > Or you could use: > unsigned long expected_irqs, unexpected_irqs; > > expected_irqs = val & GENMASK(g_spi.int - 1, 0); > unexpected_irq = val & GENMASK(MAX_NUM_INT - 1, g_spi.int); > >

Re: [PATCH 10/13] mac80211: agg-rx: Accept ADDBA request update if timeout did not change

Hi Ilan, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on mac80211-next/master] [also build test WARNING on v4.16-rc2 next-20180216] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 4/6] staging: wilc1000: fix line over 80 characters in wilc_spi_init()

On Fri, 16 Feb 2018 15:30:22 +0100 Greg KH wrote: > > diff --git a/drivers/staging/wilc1000/wilc_spi.c > > b/drivers/staging/wilc1000/wilc_spi.c > > index 30a9a61..fddc0db 100644 > > --- a/drivers/staging/wilc1000/wilc_spi.c > > +++

Re: [PATCH 12/13] mac80211: limit wmm params to comply with ETSI requirements

On Mon, 2018-02-19 at 07:54 +0200, Kalle Valo wrote: > Luca Coelho writes: > > > From: Haim Dreyfuss > > > > ETSI has recently restricted the WMM parameters values for > > 5GHz frequencies. There are two scenarios which may cause > > to violate ETSI

Re: Max clients on wifi access point with 7265

Steve deRosier writes: > On Wed, Feb 14, 2018 at 2:04 PM, Samuel Sieb wrote: >> On 02/14/2018 03:30 AM, Johannes Berg wrote: >>> >>> On Wed, 2018-02-14 at 10:55 +, Mickaël PANNEQUIN wrote: >>> Do you know the limit of the number of users

Re: [PATCH] mt7601u: Fix system freeze after resuming from hibernation

On Sat, 17 Feb 2018 13:23:29 +0200, cantabile wrote: > > Thanks for the info. Would it be cleaner to EXPORT fw_add_devm_name() > > and just call that in case driver sees FW is already loaded? That > > should inform the fw subsystem that we want the image around in case of > > hibernation, but

Re: [PATCH 12/13] mac80211: limit wmm params to comply with ETSI requirements

Luca Coelho writes: > From: Haim Dreyfuss > > ETSI has recently restricted the WMM parameters values for > 5GHz frequencies. There are two scenarios which may cause > to violate ETSI requirements. > 1. Using mac80211 default values. > 2. Userspace entity

Re: [PATCH] v4 ath10k: add LED and GPIO controlling support for various chipsets

Hi Sebastian, Thank you for the patch! Yet something to improve: [auto build test ERROR on v4.16-rc2] [also build test ERROR on next-20180216] [cannot apply to ath6kl/ath-next] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] wcn36xx: reduce verbosity of drivers messages

On Sat 17 Feb 12:25 PST 2018, Ramon Fried wrote: > Whenever the WLAN interface is started the FW > version and caps are printed, this info should appear as > debug info. > > Signed-off-by: Ramon Fried Looks reasonable, Acked-by: Bjorn Andersson

Send your prices

-- Dear Sir/Madam, We need your product and price list catalog. We are urgently in need of your item . It is meant for purchase in large quantity by our government of Ecowas Procurement Inquiry. Terms of Payment: 80% down payment through T.T while remaining 20% by L/C will be paid before

[PATCH] v6 ath10k: add LED and GPIO controlling support for various chipsets

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

Re: [PATCH] v5 ath10k: add LED and GPIO controlling support for various chipsets

Am 18.02.2018 um 15:33 schrieb Bo YU: Hi, I am just wondering about something.I am a newbies. On Sun, Feb 18, 2018 at 01:03:00PM +0100, s.gottsch...@dd-wrt.com wrote: +#ifdef CONFIG_GPIOLIB + +static int ath10k_gpio_pin_cfg_input(struct gpio_chip *chip, unsigned offset) +{ +    struct

Re: [PATCH] v5 ath10k: add LED and GPIO controlling support for various chipsets

Hi, I am just wondering about something.I am a newbies. On Sun, Feb 18, 2018 at 01:03:00PM +0100, s.gottsch...@dd-wrt.com wrote: From: Sebastian Gottschall Adds LED and GPIO Control support for 988x, 9887, 9888, 99x0, 9984 based chipsets with on chipset

[PATCH] v5 ath10k: add LED and GPIO controlling support for various chipsets

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

Re: [PATCH] [PATCH 1/1] ath10k: add LED and GPIO controlling support for various chipsets

improve the system] url: https://github.com/0day-ci/linux/commits/s-gottschall-dd-wrt-com/ath10k-add-LED-and-GPIO-controlling-support-for-various-chipsets/20180218-141132 base: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git master config: openrisc-allyesconfig