On Tue, Feb 11, 2020 at 03:12:19PM -0600, Gustavo A. R. Silva wrote:
> The current codebase makes use of the zero-length array language
> extension to the C90 standard, but the preferred mechanism to declare
> variable-length types such as these ones is a flexible array member[1][2],
> introduced i
Warren Buffett Foundation picked you for a $1 500,000 donation. For more
details reply
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
randconfig-a001-20200210
h8300randconfig-a001-20200210
nios2randconfig-a001-20200210
microblaze randconfig-a001-20200210
sparc64 randconfig-a001-20200210
c6x randconfig-a001-20200210
c6x randconfig-a001-20200211
h8300
-a001-20200211
x86_64 randconfig-a002-20200211
x86_64 randconfig-a003-20200211
i386 randconfig-a001-20200211
i386 randconfig-a002-20200211
i386 randconfig-a003-20200211
alpharandconfig-a001-20200210
m68k
On Mon, 2020-01-27 at 14:55 +0300, Dan Carpenter wrote:
> On Mon, Jan 27, 2020 at 03:43:28PM +0530, Pragat Pandya wrote:
> > Change all the occurrences of "MilliSecond" to "milli_second" in exfat.
> >
> > Signed-off-by: Pragat Pandya
> > ---
> > drivers/staging/exfat/exfat.h | 2 +-
> > d
On 2/11/20 4:47 PM, Gustavo A. R. Silva wrote:
>
>
> On 2/11/20 16:15, Alex Elder wrote:
>> On 2/11/20 3:12 PM, Gustavo A. R. Silva wrote:
>>> The current codebase makes use of the zero-length array language
>>> extension to the C90 standard, but the preferred mechanism to declare
>>> variable-le
On 2/11/20 16:15, Alex Elder wrote:
> On 2/11/20 3:12 PM, Gustavo A. R. Silva wrote:
>> The current codebase makes use of the zero-length array language
>> extension to the C90 standard, but the preferred mechanism to declare
>> variable-length types such as these ones is a flexible array member
On 2/11/20 3:12 PM, Gustavo A. R. Silva wrote:
> The current codebase makes use of the zero-length array language
> extension to the C90 standard, but the preferred mechanism to declare
> variable-length types such as these ones is a flexible array member[1][2],
> introduced in C99:
>
> struct foo
The current codebase makes use of the zero-length array language
extension to the C90 standard, but the preferred mechanism to declare
variable-length types such as these ones is a flexible array member[1][2],
introduced in C99:
struct foo {
int stuff;
struct boo array[];
};
By ma
The current codebase makes use of the zero-length array language
extension to the C90 standard, but the preferred mechanism to declare
variable-length types such as these ones is a flexible array member[1][2],
introduced in C99:
struct foo {
int stuff;
struct boo array[];
};
By ma
On Tue, Feb 11, 2020 at 12:05:39AM +0530, Pragat Pandya wrote:
> This patchset renames following nineteen variables in exfat.h
> Fix checkpatch warning: Avoid CamelCase
> -Year->year
> -Day->day
> -Hour->hour
> -Minute->minute
> -Second->second
> -Millisecond->millisecond
> -FatType->fat_typ
On Tue, Feb 11, 2020 at 09:57:10AM +, ajay.kat...@microchip.com wrote:
> From: Ajay Singh
>
> Refactor handling of P2P specific action frames. Make use of 'struct' to
> handle the P2P frames instead of manipulating using 'buf' pointer.
>
> Signed-off-by: Ajay Singh
> ---
> v2: corrected 'w
On Tuesday 11 February 2020 16:21:41 CET Jérôme Pouiller wrote:
> On Tuesday 11 February 2020 15:03:34 CET YueHaibing wrote:
> > drivers/staging/wfx/queue.c: In function wfx_tx_queues_get:
> > drivers/staging/wfx/queue.c:484:28: warning: variable tx_priv set but not
> > used [-Wunused-but-set-vari
On Tuesday 11 February 2020 15:03:34 CET YueHaibing wrote:
> drivers/staging/wfx/queue.c: In function wfx_tx_queues_get:
> drivers/staging/wfx/queue.c:484:28: warning: variable tx_priv set but not
> used [-Wunused-but-set-variable]
>
> commit 2e57865e79cf ("staging: wfx: pspoll_mask make no sense
On Tuesday 11 February 2020 13:49:22 CET Michał Mirosław wrote:
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
>
>
> On Tue, Feb 11, 2020 at 11:19:18AM +, Jérôme Poui
drivers/staging/wfx/queue.c: In function wfx_tx_queues_get:
drivers/staging/wfx/queue.c:484:28: warning: variable tx_priv set but not used
[-Wunused-but-set-variable]
commit 2e57865e79cf ("staging: wfx: pspoll_mask make no sense")
left behind this unused variable.
Reported-by: Hulk Robot
Signed
On 2020/2/11 22:24, Dan Carpenter wrote:
> On Tue, Feb 11, 2020 at 09:43:56PM +0800, YueHaibing wrote:
>> drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c: In function
>> vchiq_use_internal:
>> drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c:2346:16:
>> warning: variabl
On Tue, Feb 11, 2020 at 09:43:56PM +0800, YueHaibing wrote:
> drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c: In function
> vchiq_use_internal:
> drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c:2346:16:
> warning: variable local_entity_uc set but not used
> [-Wunused
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.5.2, v5.4.18, v4.19.102, v4.14.170,
v4.9.213, v4.4.213.
v5.5.2: Build OK!
v4.19
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c: In function
vchiq_use_internal:
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c:2346:16:
warning: variable local_entity_uc set but not used [-Wunused-but-set-variable]
commit bd8aa2850f00 ("staging: vc04_services: Get o
On Tue, Feb 11, 2020 at 11:39:31AM +0100, Michał Mirosław wrote:
> On Tue, Feb 11, 2020 at 12:23:54PM +0300, Dan Carpenter wrote:
> > On Tue, Feb 11, 2020 at 09:46:54AM +0100, Michał Mirosław wrote:
> > > @@ -234,8 +234,8 @@ static void wfx_sdio_remove(struct sdio_func *func)
> > > struct wfx_sdi
On Tue, Feb 11, 2020 at 11:19:18AM +, Jérôme Pouiller wrote:
> On Tuesday 11 February 2020 11:35:01 CET Michał Mirosław wrote:
> > Current code races in init/exit with interrupt handlers. This is noticed
> > by the warning below. Fix it by using devres for ordering allocations and
> > IRQ de/re
It's been over 6 months, and no one has noticed that these drivers are
deleted, probably because no one actually has this hardware. As no one
has volunteered to maintain the code, let's drop it for good.
Signed-off-by: Greg Kroah-Hartman
---
[resending and deleting the actual diffs as the patch
On Tuesday 11 February 2020 11:35:01 CET Michał Mirosław wrote:
> Current code races in init/exit with interrupt handlers. This is noticed
> by the warning below. Fix it by using devres for ordering allocations and
> IRQ de/registration.
>
> WARNING: CPU: 0 PID: 827 at drivers/staging/wfx/bus_spi.
Dear : Winner
We are pleased to inform you that as a result of our recent DRAWS held on the
8th of February,2020.You have officially Won $1.700.000,00 USD , Kindly Contact
Mrs.Maria Lucento ,for claims with the following details
1. Full Name:2.Gender/Age--- 3.Address-:4.Mobile--- 5.Occu
On Tuesday 11 February 2020 09:46:56 CET Michał Mirosław wrote:
>
> Replace udelay() with usleep_range() as all uses are in a sleepable context.
>
> Signed-off-by: Michał Mirosław
> ---
> drivers/staging/wfx/bh.c | 2 +-
> drivers/staging/wfx/bus_spi.c | 4 ++--
> drivers/staging/wfx/hwio.c
On Tuesday 11 February 2020 09:46:55 CET Michał Mirosław wrote:
> Driver calls GPIO get/set only from non-atomic context and so can use any
> GPIOs.
>
> Signed-off-by: Michał Mirosław
> ---
> drivers/staging/wfx/bh.c | 6 +++---
> drivers/staging/wfx/bus_spi.c | 4 ++--
> drivers/staging/wf
On Tue, Feb 11, 2020 at 12:23:54PM +0300, Dan Carpenter wrote:
> On Tue, Feb 11, 2020 at 09:46:54AM +0100, Michał Mirosław wrote:
> > @@ -234,8 +234,8 @@ static void wfx_sdio_remove(struct sdio_func *func)
> > struct wfx_sdio_priv *bus = sdio_get_drvdata(func);
> >
> > wfx_release(bus->co
Replace udelay() with usleep_range() as all uses are in a sleepable context.
Signed-off-by: Michał Mirosław
---
drivers/staging/wfx/bh.c | 2 +-
drivers/staging/wfx/bus_spi.c | 4 ++--
drivers/staging/wfx/hwio.c| 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drive
Driver calls GPIO get/set only from non-atomic context and so can use any
GPIOs.
Signed-off-by: Michał Mirosław
---
drivers/staging/wfx/bh.c | 6 +++---
drivers/staging/wfx/bus_spi.c | 4 ++--
drivers/staging/wfx/main.c| 2 +-
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git
As for SPI, follow "vendor,chip" format 'compatible' string also for
SDIO bus.
Fixes: 0096214a59a7 ("staging: wfx: add support for I/O access")
Signed-off-by: Michał Mirosław
---
.../devicetree/bindings/net/wireless/siliabs,wfx.txt | 4 ++--
drivers/staging/wfx/bus_sdio.c
On Tuesday 11 February 2020 09:46:55 CET Michał Mirosław wrote:
> Lockdep is complaining about recursive locking, because it can't make
> a difference between locked skb_queues. Annotate nested locks and avoid
> double bh_disable/enable.
>
> [...]
> insmod/815 is trying to acquire lock:
> cb7d6418
Add "compatible" string matching "vendor,chip" template and proper
GPIO flags handling. Keep support for old name and reset polarity
for older devicetrees.
Cc: sta...@vger.kernel.org # d3a5bcb4a17f ("gpio: add
gpiod_toggle_active_low()")
Cc: sta...@vger.kernel.org
Fixes: 0096214a59a7 ("staging:
A set of fixes for WF200 WiFi module driver. Three are bug fixes,
all the rest: cleanups and optimizations.
v2:
use devres for fixing init/interrupt race, as suggested by Dan Carpenter
add Fixes: tags dropped by accident
remove 8-bit SPI fall-back patch
Michał Mirosław (6):
staging: wfx:
Current code races in init/exit with interrupt handlers. This is noticed
by the warning below. Fix it by using devres for ordering allocations and
IRQ de/registration.
WARNING: CPU: 0 PID: 827 at drivers/staging/wfx/bus_spi.c:142
wfx_spi_irq_handler+0x5c/0x64 [wfx]
race condition in driver init/d
Lockdep is complaining about recursive locking, because it can't make
a difference between locked skb_queues. Annotate nested locks and avoid
double bh_disable/enable.
[...]
insmod/815 is trying to acquire lock:
cb7d6418 (&(&list->lock)->rlock){+...}, at: wfx_tx_queues_clear+0xfc/0x198 [wfx]
but
This patch fixes "WARNING: Missing a blank line after
declarations" generated from checkpatch.pl by adding
a blank line after declarations.
Signed-off-by: Mohana Datta Yelugoti
---
drivers/staging/qlge/qlge_main.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/staging
From: Ajay Singh
Refactor handling of P2P specific action frames. Make use of 'struct' to
handle the P2P frames instead of manipulating using 'buf' pointer.
Signed-off-by: Ajay Singh
---
v2: corrected 'while' condition by adding 'struct' size as suggested by Dan.
drivers/staging/wilc1000/cfg
From: Ajay Singh
The 'priv' handler is already present in 'vif' struct so directly fetch
its value from vif handler in wilc_handle_roc_expired().
Signed-off-by: Ajay Singh
---
v2: No change
drivers/staging/wilc1000/hif.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/d
From: Ajay Singh
Remove the use of vendor specific IE parameter to decide
p2p_GO/p2p_Client roles between two 'wilc' device. Previously p2p group
formation between two 'wilc' device make use of vendor IE for roles
decision. The role is decided based on the 'go_intent' value.
Signed-off-by: Ajay
Hi Dan,
On 11/02/20 12:21 pm, Dan Carpenter wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> On Mon, Feb 10, 2020 at 06:36:01PM +, ajay.kat...@microchip.com wrote:
>> + if (sta_ch == WILC_INVALID_CHANNEL)
>> + return;
>
On Tue, Feb 11, 2020 at 09:46:54AM +0100, Michał Mirosław wrote:
> @@ -218,9 +218,9 @@ static int wfx_sdio_probe(struct sdio_func *func,
> return 0;
>
> err3:
> - wfx_free_common(bus->core);
> + wfx_sdio_irq_unsubscribe(bus);
> err2:
> - wfx_sdio_irq_unsubscribe(bus);
> +
Lockdep is complaining about recursive locking, because it can't make
a difference between locked skb_queues. Annotate nested locks and avoid
double bh_disable/enable.
[...]
insmod/815 is trying to acquire lock:
cb7d6418 (&(&list->lock)->rlock){+...}, at: wfx_tx_queues_clear+0xfc/0x198 [wfx]
but
A set of fixes for WF200 WiFi module driver. Three are bug fixes,
all the rest: cleanups and optimizations.
Michał Mirosław (7):
staging: wfx: add proper "compatible" string
staging: wfx: follow compatible = vendor,chip format
staging: wfx: fix init/remove vs IRQ race
staging: wfx: annotat
Driver calls GPIO get/set only from non-atomic context and so can use any
GPIOs.
Signed-off-by: Michał Mirosław
---
drivers/staging/wfx/bh.c | 6 +++---
drivers/staging/wfx/bus_spi.c | 4 ++--
drivers/staging/wfx/main.c| 2 +-
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git
As for SPI, follow "vendor,chip" format 'compatible' string also for
SDIO bus.
Signed-off-by: Michał Mirosław
---
.../devicetree/bindings/net/wireless/siliabs,wfx.txt | 4 ++--
drivers/staging/wfx/bus_sdio.c| 1 +
2 files changed, 3 insertions(+), 2 delet
Add "compatible" string matching "vendor,chip" template and proper
GPIO flags handling. Keep support for old name and reset polarity
for older devicetrees.
Cc: sta...@vger.kernel.org # d3a5bcb4a17f ("gpio: add
gpiod_toggle_active_low()")
Cc: sta...@vger.kernel.org
Signed-off-by: Michał Mirosław
Move interrupt request and free so to avoid following WARN on probe
and possible use-after-free on remove.
WARNING: CPU: 0 PID: 827 at drivers/staging/wfx/bus_spi.c:142
wfx_spi_irq_handler+0x5c/0x64 [wfx]
race condition in driver init/deinit
Cc: sta...@vger.kernel.org
Signed-off-by: Michał Miros
Replace udelay() with usleep_range() as all uses are in a sleepable context.
Signed-off-by: Michał Mirosław
---
drivers/staging/wfx/bh.c | 2 +-
drivers/staging/wfx/bus_spi.c | 4 ++--
drivers/staging/wfx/hwio.c| 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drive
WF200 chip works with 16-bit words over SPI, so use that word
size if available. This avoids a bounce buffer usage for
little-endian hosts.
Signed-off-by: Michał Mirosław
---
drivers/staging/wfx/bus_spi.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/
50 matches
Mail list logo
