Re: [PATCH 4/5] staging: wilc1000: wilc_msgqueue.c: use kmalloc with GFP_ATOMIC

2015-09-07 Thread Greg KH
On Tue, Sep 08, 2015 at 11:23:07AM +0900, Tony Cho wrote: > > > On 2015년 09월 08일 00:36, Chaehyun Lim wrote: > >This patch use kmalloc with GFP_ATOMIC instead of WILC_MALLOC. > >It is inside the spin lock region. > > > >Signed-off-by: Chaehyun Lim > >--- > > drivers/staging/wilc1000/wilc_msgqueu

Re: [PATCH 4/5] staging: wilc1000: wilc_msgqueue.c: use kmalloc with GFP_ATOMIC

2015-09-07 Thread Tony Cho
On 2015년 09월 08일 00:36, Chaehyun Lim wrote: This patch use kmalloc with GFP_ATOMIC instead of WILC_MALLOC. It is inside the spin lock region. Signed-off-by: Chaehyun Lim --- drivers/staging/wilc1000/wilc_msgqueue.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers

[PATCH] staging: lustre: ptlrpc: include ptlrpc_internal.h

2015-09-07 Thread Anders Fridlund
Remove sparse warning "symbol 'sptlrpc_plain_init' was not declared" by including ptlrpc_internal.h, which includes sptlrpc_plain_init. Signed-off-by: Anders Fridlund --- drivers/staging/lustre/lustre/ptlrpc/sec_plain.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/staging/lustre/l

Administrador do sistema

2015-09-07 Thread ADMIN
Sua caixa de correio excedeu o limite de armazenamento, que é de 20 GB como conjunto pelo administrador, você está atualmente em execução no 20,9 GB, você pode não ser capaz de Enviar ou receber novas mensagens até que você re-validar sua caixa de correio. Para Revalide sua caixa de corr

Administrador do sistema

2015-09-07 Thread ADMIN
Sua caixa de correio excedeu o limite de armazenamento, que é de 20 GB como conjunto pelo administrador, você está atualmente em execução no 20,9 GB, você pode não ser capaz de Enviar ou receber novas mensagens até que você re-validar sua caixa de correio. Para Revalide sua caixa de corr

[PATCH 4/5] staging: wilc1000: wilc_msgqueue.c: use kmalloc with GFP_ATOMIC

2015-09-07 Thread Chaehyun Lim
This patch use kmalloc with GFP_ATOMIC instead of WILC_MALLOC. It is inside the spin lock region. Signed-off-by: Chaehyun Lim --- drivers/staging/wilc1000/wilc_msgqueue.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/wilc1000/wilc_msgqueue.c b/drivers/stagi

[PATCH 5/5] staging: wilc1000: host_interface.c: fix build warning

2015-09-07 Thread Chaehyun Lim
This patch remove build build warning from Handle_SetOperationMode function. Host interface operation mode has one of 4 types from AP_MODE, STATION_MODE, GO_MODE and CLIENT_MODE. This values are range from 0x01 to 0x04 if mode is set correctly. If value of host interface operation is 0, it is not i

[PATCH 2/5] staging: wilc1000: linux_wlan.c: add kzalloc error check

2015-09-07 Thread Chaehyun Lim
This patch adds error check if kzalloc is failed. Signed-off-by: Chaehyun Lim --- drivers/staging/wilc1000/linux_wlan.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/staging/wilc1000/linux_wlan.c b/drivers/staging/wilc1000/linux_wlan.c index f7dda75..76c48a4 100644 --- a/drivers

[PATCH 3/5] staging: wilc1000: remove commented codes

2015-09-07 Thread Chaehyun Lim
This patch removes commented codes. Signed-off-by: Chaehyun Lim --- drivers/staging/wilc1000/coreconfigurator.c | 7 --- drivers/staging/wilc1000/host_interface.c | 88 - drivers/staging/wilc1000/linux_mon.c| 61 drivers/staging/wilc100

[PATCH 1/5] staging: wilc1000: linux_wlan.c: use kzalloc instead of WILC_MALLOC

2015-09-07 Thread Chaehyun Lim
This patch replaces WILC_MALLOC with kzalloc. Signed-off-by: Chaehyun Lim --- drivers/staging/wilc1000/linux_wlan.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/staging/wilc1000/linux_wlan.c b/drivers/staging/wilc1000/linux_wlan.c index afd6702..f7dda75 100644 -

[PATCH 2/4] hv: fcopy: use wrapper to propate state

2015-09-07 Thread Olaf Hering
The .state is used by several threads of execution. Propagate the state to make changes visible. Also propagate context change in hv_fcopy_onchannelcallback. Without this change fcopy may hang at random points. Signed-off-by: Olaf Hering --- drivers/hv/hv_fcopy.c | 36 ---

[PATCH 1/4] hv: add helpers to handle hv_util device state

2015-09-07 Thread Olaf Hering
The callbacks in kvp, vss and fcopy code are called the main thread and also from interrupt context. If a state change is done by the main thread it is not immediately seen by the interrupt. As a result the state machine gets out of sync. Force propagation of state changes via get/set helpers with

[PATCH 4/4] hv: vss: use wrapper to propate state

2015-09-07 Thread Olaf Hering
The .state is used by several threads of execution. Propagate the state to make changes visible. Also propagate context change in vss_on_msg. Signed-off-by: Olaf Hering --- drivers/hv/hv_snapshot.c | 37 - 1 file changed, 20 insertions(+), 17 deletions(-) dif

[PATCH 3/4] hv: kvp: use wrapper to propate state

2015-09-07 Thread Olaf Hering
The .state is used by several threads of execution. Propagate the state to make changes visible. Also propagate context change in kvp_on_msg. Signed-off-by: Olaf Hering --- drivers/hv/hv_kvp.c | 38 +- 1 file changed, 21 insertions(+), 17 deletions(-) diff --

[PATCH 0/4] hv: utils: propagate state to interrupt thread

2015-09-07 Thread Olaf Hering
The Copy-VMFile cmdlet on the host may fail because the guest fcopy driver state machine gets out of sync. This happens because the ->state and ->context variables are accessed by the main thread and from interrupt context. If an interrupt happens between fcopy_respond_to_host and hv_poll_channel i

Re: [PATCH 3/5] staging: most: remove driver owner

2015-09-07 Thread Sudip Mukherjee
On Mon, Sep 07, 2015 at 02:13:38PM +0200, Andrey Shvetsov wrote: > On Fri, Sep 04, 2015 at 04:22:04PM +0530, Sudip Mukherjee wrote: > > The platform driver core will set the owner value, we do not need to do > > it in the module. > > > > Signed-off-by: Sudip Mukherjee > > --- > > drivers/staging

[PATCH 1/2] staging: gdm72xx: fix memory leak

2015-09-07 Thread Sudip Mukherjee
We were successfully requesting the firmware but on error it was not being released. Signed-off-by: Sudip Mukherjee --- drivers/staging/gdm72xx/usb_boot.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/staging/gdm72xx/usb_boot.c b/drivers/staging/gdm72xx/usb

[PATCH 2/2] staging: gdm72xx: NULL comparison style

2015-09-07 Thread Sudip Mukherjee
checkpatch complains if NULL comparison is done as if (var == NULL) Signed-off-by: Sudip Mukherjee --- drivers/staging/gdm72xx/gdm_qos.c | 2 +- drivers/staging/gdm72xx/gdm_sdio.c | 20 ++-- drivers/staging/gdm72xx/gdm_usb.c | 16 drivers/staging/gdm72xx/gd

Re: [PATCH 3/5] staging: most: remove driver owner

2015-09-07 Thread Andrey Shvetsov
On Fri, Sep 04, 2015 at 04:22:04PM +0530, Sudip Mukherjee wrote: > The platform driver core will set the owner value, we do not need to do > it in the module. > > Signed-off-by: Sudip Mukherjee > --- > drivers/staging/most/hdm-dim2/dim2_hdm.c | 1 - > 1 file changed, 1 deletion(-) > > diff --gi

Re: [PATCH v2 5/7] staging: board: Add support for devices with complex dependencies

2015-09-07 Thread Geert Uytterhoeven
Hi Ulf, On Mon, Sep 7, 2015 at 1:45 PM, Ulf Hansson wrote: > On 4 September 2015 at 17:03, Geert Uytterhoeven wrote: >> On Fri, 4 Sep 2015, Ulf Hansson wrote: >>> On 3 September 2015 at 15:35, Geert Uytterhoeven >>> wrote: >>> > On Thu, Sep 3, 2015 at 2:53 PM, Ulf Hansson >>> > wrote: >>> >>

Re: [PATCH v2 5/7] staging: board: Add support for devices with complex dependencies

2015-09-07 Thread Ulf Hansson
On 4 September 2015 at 17:03, Geert Uytterhoeven wrote: > Hi Ulf, > > On Fri, 4 Sep 2015, Ulf Hansson wrote: >> On 3 September 2015 at 15:35, Geert Uytterhoeven >> wrote: >> > On Thu, Sep 3, 2015 at 2:53 PM, Ulf Hansson wrote: >> >> On 17 June 2015 at 10:38, Geert Uytterhoeven >> >> w

[PATCH 1/3] staging: wilc1000: remove dead codes

2015-09-07 Thread Tony Cho
This patch removes the preprocessor definition from the codes, as shown in the following, which is not used anymore. - WILC_FULLY_HOSTING_AP Signed-off-by: Tony Cho --- drivers/staging/wilc1000/linux_mon.c | 97 --- drivers/staging/wilc1000/linux_wlan.c

[PATCH 3/3] staging: wilc1000: fix potential memory leak

2015-09-07 Thread Tony Cho
This patch adds kfree(mgmt_tx) when memory allocation of mgmt_tx->buff fails in the second calls of kmalloc() to avoid the memory leak from mgmt_tx first allocated before the second calls of kmalloc(). Signed-off-by: Tony Cho Signed-off-by: Chris Park --- drivers/staging/wilc1000/linux_mon.c

[PATCH 2/3] staging: wilc1000: remove unused preprocessor definition

2015-09-07 Thread Tony Cho
This patch removes a preprocessor definition, SWITCH_LOG_TERMINAL, which is not used. Enabling this definition affects the performance. Signed-off-by: Tony Cho --- drivers/staging/wilc1000/linux_wlan.c| 6 -- drivers/staging/wilc1000/wilc_wlan_cfg.c | 8 2 files changed, 14 dele

Re: [PATCH] Staging: most: MOST and MOSTCORE should depend on HAS_DMA

2015-09-07 Thread Christian Gromm
On Tue, 1 Sep 2015 22:05:58 +0200 Geert Uytterhoeven wrote: > If NO_DMA=y: > > ERROR: "dma_free_coherent" [drivers/staging/most/mostcore/mostcore.ko] > undefined! > ERROR: "dma_alloc_coherent" [drivers/staging/most/mostcore/mostcore.ko] > undefined! > > As all MOST sub drivers use DMA