[PATCH] Staging: rtl8192 Clean up function definition

2015-03-25 Thread Eddie Kovsky
Change function definition to match its prototype declaration. This fixes the following warning generated by sparse: drivers/staging/rtl8192u/r8192U_core.c:1970:6: warning: symbol 'rtl8192_update_ratr_table' was not declared. Should it be static? Signed-off-by: Eddie Kovsky --- drivers/staging/

[PATCH v2 07/10] staging/lustre/ptlrpc: fix import state during replay

2015-03-25 Thread green
From: Andriy Skulysh Client doesn't restore import state correctly on reconnect during replay. It resends lock replay when final ping was queued by server. Server fails with "target_queue_recovery_request()) ASSERTION( req->rq_export->exp_lock_replay_needed ) failed" Add imp_replay_state to stor

[PATCH v2 01/10] staging/lustre/osc: shorten IO calling path

2015-03-25 Thread green
From: Bobi Jam By using osc_io_unplug_aync() for osc_queue_sync_pages() to shorten the IO calling path, to reduce the chance of stack overflow. Signed-off-by: Bobi Jam Signed-off-by: Bob Glossman Reviewed-on: http://review.whamcloud.com/11612 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU

[PATCH 07/10] staging/lustre/ptlrpc: fix import state during replay

2015-03-25 Thread green
From: Andriy Skulysh Client doesn't restore import state correctly on reconnect during replay. It resends lock replay when final ping was queued by server. Server fails with "target_queue_recovery_request()) ASSERTION( req->rq_export->exp_lock_replay_needed ) failed" Add imp_replay_state to stor

[PATCH 09/10] staging/lustre: update timestamps after buiding rpc

2015-03-25 Thread green
From: Niu Yawei The mtime/atime/ctime in the write RPC has to be updated after the RPC is built (where xid is generated), otherwise, it could race with the setattr and updating wrong timestamps on OST side. Seems this regression was introduced when landing clio code. Signed-off-by: Niu Yawei R

[PATCH 06/10] staging/lustre/lov: don't crash accessing LOV object with FID{0, 0}

2015-03-25 Thread green
From: Yang Sheng Some object maybe has a corrupted LOV EA or a hole in LOV EA. We should not crash client in such case. Signed-off-by: Fan Yong Signed-off-by: Yang Sheng Reviewed-on: http://review.whamcloud.com/12740 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4958 Reviewed-by: Jian Yu

[PATCH 10/10] staging/lustre/xattr: xattr data may be gone with lock held

2015-03-25 Thread green
From: Lai Siyao Xattr cached data may be gone, but lock still held, in this case, refetch xattr from server, otherwise client will return error. Signed-off-by: Lai Siyao Reviewed-on: http://review.whamcloud.com/12952 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3544 Reviewed-by: Bobi Jam

[PATCH 08/10] staging/lustre/llite: glimpse the inode before doing fiemap

2015-03-25 Thread green
From: Li Dongyang For a new inode, the i_size is 0 until a stat, which will yield an empty fiemap result. Fix the issue by glimpsing the size before doing fiemap. Signed-off-by: Li Dongyang Signed-off-by: Bob Glossman Reviewed-by: Andreas Dilger Reviewed-by: Jinshan Xiong Reviewed-on: http:/

[PATCH 05/10] staging/lustre/mgc: detach MGC dev on error

2015-03-25 Thread green
From: Bobi Jam lustre_start_mgc() creates MGC device, if error happens later on ll_fill_super(), this device is still attached, and later mount fails by keep complaining that the MGC device's already in the client node. It turns out that the device was referenced by mgc config llog data which is

[PATCH 03/10] staging/lustre/ptlrpc: false alarm in AT network latency measuring

2015-03-25 Thread green
From: Liang Zhen If early reply of client RPC is lost and client RPC is expired and resent, server will drop the resent RPC because it's already in processing, server may also send reply or early reply to client, which can still match reply buffer of the original request. In this case, client is

[PATCH 04/10] staging/lustre/mgc: check the import stat for lprocfs

2015-03-25 Thread green
From: Hongchao Zhang in lprocfs_mgc_rd_ir_state, the import state should be checked the validity before doing further work. Signed-off-by: Hongchao Zhang Reviewed-on: http://review.whamcloud.com/12896 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-5650 Reviewed-by: Fan Yong Reviewed-by: N

[PATCH 01/10] staging/lustre/osc: shorten IO calling path

2015-03-25 Thread green
From: Bobi Jam By using osc_io_unplug_aync() for osc_queue_sync_pages() to shorten the IO calling path, to reduce the chance of stack overflow. Signed-off-by: Bobi Jam Signed-off-by: Bob Glossman http://review.whamcloud.com/11612 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3188 Reviewed

[PATCH 00/10] Lustre fixes

2015-03-25 Thread green
From: Oleg Drokin A number of lustre fixes. Andriy Skulysh (1): staging/lustre/ptlrpc: fix import state during replay Bobi Jam (2): staging/lustre/osc: shorten IO calling path staging/lustre/mgc: detach MGC dev on error Christopher J. Morrone (1): staging/lustre/mdc: Handle empty but n

[PATCH 02/10] staging/lustre/mdc: Handle empty but non-zero acl xattr

2015-03-25 Thread green
From: "Christopher J. Morrone" We have found that posix_acl_access can have a value of \002\000\000\000. In that case body->aclsize is non-zero, but the there are no actuall acls stored in the xattr. In mdc_unpack_acl(), it only checks IS_ERR() on the pointer returned by posix_acl_from_xattr(),

[PATCH] hv_vmbus: Add gradually increased delay for retries in vmbus_post_msg()

2015-03-25 Thread Haiyang Zhang
Most of the retries can be done within a millisecond successfully, so we sleep 1ms before the first retry, then gradually increase the retry interval to 2^n with max value of 2048ms. Doing so, we will have shorter overall delay time, because most of the cases succeed within 1-2 attempts. Signed-of

[PATCH 0/2] staging: rts5208: Remove hidden flow control macros

2015-03-25 Thread Joe Perches
Macros with hidden flow control are poor form. Joe Perches (2): staging: rts5208: Remove TRACE_RET and TRACE_GOTO macros staging: rts5208: Remove RTSX_READ_REG and RTSX_WRITE_REG macros drivers/staging/rts5208/Makefile |2 +- drivers/staging/rts5208/ms.c | 1654 ++

[PATCH 2/2] staging: rts5208: Remove RTSX_READ_REG and RTSX_WRITE_REG macros

2015-03-25 Thread Joe Perches
Macros with hidden flow control are bad form as the code path taken can be unexpected for the reader. Expand these in-place and remove the macros. Done with coccinelle script: @@ expression chip; expression arg1; expression arg2; expression arg3; @@ - RTSX_WRITE_REG(chip, arg1, arg2, arg3

RE: [PATCH 0/1] Drivers: hv: hv_balloon: do not online pages in offline blocks

2015-03-25 Thread KY Srinivasan
> -Original Message- > From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com] > Sent: Wednesday, March 25, 2015 11:02 AM > To: KY Srinivasan > Cc: Haiyang Zhang; de...@linuxdriverproject.org; linux- > ker...@vger.kernel.org; Dexuan Cui > Subject: [PATCH 0/1] Drivers: hv: hv_balloon: do not o

[PATCH 0/1] Drivers: hv: hv_balloon: do not online pages in offline blocks

2015-03-25 Thread Vitaly Kuznetsov
Patch 1/1 is rather a hackaround. The root cause of the issue is the fact that we're adding not fully backed memory blocks and allow to online them. It is relatively easy to forbid that and add only fully backed 128Mb regions. The whole driver code will be much simpler: hv_bring_pgs_online() and

[PATCH 1/1] Drivers: hv: hv_balloon: do not online pages in offline blocks

2015-03-25 Thread Vitaly Kuznetsov
Currently we add memory in 128Mb blocks but the request from host can be aligned differently. In such case we add a partially backed block and when this block goes online we skip onlining pages which are not backed (hv_online_page() callback serves this purpose). When we receive next request for th

Re: [PATCH] staging: rts5208: Remove TRACE_RET and TRACE_GOTO macros

2015-03-25 Thread Joe Perches
On Tue, 2015-03-24 at 21:28 -0700, Joe Perches wrote: > Remove these flow hiding macros. Apologies, this won't compile properly as I neglected to "git add trace.c" prior to the git commit. I'll resend later. ___ devel mailing list de...@linuxdriverproj

RE: [PATCH V2 1/1] X86: hyperv: Enable MSR based APIC access

2015-03-25 Thread KY Srinivasan
> -Original Message- > From: Ingo Molnar [mailto:mingo.kernel@gmail.com] On Behalf Of Ingo > Molnar > Sent: Wednesday, March 25, 2015 5:15 AM > To: KY Srinivasan > Cc: x...@kernel.org; gre...@linuxfoundation.org; linux- > ker...@vger.kernel.org; de...@linuxdriverproject.org; o...@aepf

Re: [PATCH] staging: octeon-usb: Made octeon_usb_match const

2015-03-25 Thread Mateusz Kulikowski
On 24.03.2015 05:31, Greg KH wrote: On Mon, Mar 09, 2015 at 11:09:03PM +0100, Mateusz Kulikowski wrote: (...) Sorry, someone else sent this patch, and I saw their patch first before yours, and applied it, which was my fault :( No problem, it was tiny patch, easy to miss. I'll focus on rtl819

Re: [PATCH V2 1/1] X86: hyperv: Enable MSR based APIC access

2015-03-25 Thread Ingo Molnar
* K. Y. Srinivasan wrote: > If the hypervisor supports MSR based access to the APIC registers > (EOI, TPR and ICR), implement the MSR based access. > > Signed-off-by: K. Y. Srinivasan > --- > Changes from V1: Addressed comments from Ingo Molnar > You didn't address my primary feedback: >

Re: [PATCH] staging: sm750fb: Fixed no space warnings

2015-03-25 Thread Sudip Mukherjee
On Wed, Mar 25, 2015 at 12:29:22PM +0100, Greg KH wrote: > On Fri, Mar 20, 2015 at 08:36:33AM -0700, Ragavendra wrote: > > I sent the patch with the below subject line is the latest one. Please > > refer to > > it, as I missed putting the patch versions on these. Good day! > > > > > > [PATCH v5]

Re: [PATCH] staging: sm750fb: Fixed no space warnings

2015-03-25 Thread Greg KH
On Fri, Mar 20, 2015 at 08:36:33AM -0700, Ragavendra wrote: > I sent the patch with the below subject line is the latest one. Please refer > to > it, as I missed putting the patch versions on these. Good day! > > > [PATCH v5] staging: sm750fb: Fixed no space and indent warns I have no idea what