[PATCH] staging: wilc1000: Fix lines ending with parentheses

2017-12-15 Thread Aditya Shankar
This patch fixes the "Lines should not end with a '('" problem reported by checkpatch Signed-off-by: Aditya Shankar --- drivers/staging/wilc1000/linux_mon.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/staging/wilc1000/linux_mon.c b/drivers/staging/wi

[PATCH v2] staging: wilc1000: Fix problems reported by checkpatch

2017-12-15 Thread Aditya Shankar
This commit fixes below style problems in multiple lines Fix checkpatch WARNING: line over 80 characters Signed-off-by: Aditya Shankar --- drivers/staging/wilc1000/linux_mon.c | 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/drivers/staging/wilc1000/linux_m

[PATCH] Staging: ccree: Add blank line after declarations

2017-12-15 Thread Kamal Heib
This patch adds a blank line after declarations to improve code readability. Issue find by checkpatch.pl script. WARNING: Missing a blank line after declarations Signed-off-by: Kamal Heib --- drivers/staging/ccree/ssi_cipher.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/staging/

Re: [GIT PULL] Staging driver fixes for 4.15-rc4

2017-12-15 Thread Greg KH
On Fri, Dec 15, 2017 at 01:03:03PM -0800, Linus Torvalds wrote: > On Fri, Dec 15, 2017 at 11:00 AM, Greg KH wrote: > > > > While there are 4 patches in here, there's really only 2, as one ion > > patch got reverted due to build errors reported by 0-day. > > Since the revert was for the previous c

[PATCH] staging: android: ion: Fix dma direction for dma_sync_sg_for_cpu/device

2017-12-15 Thread Sushmita Susheelendra
Use the direction argument passed into begin_cpu_access and end_cpu_access when calling the dma_sync_sg_for_cpu/device. The actual cache primitive called depends on the direction passed in. Signed-off-by: Sushmita Susheelendra --- drivers/staging/android/ion/ion.c | 4 ++-- 1 file changed, 2 ins

Re: [GIT PULL] Staging driver fixes for 4.15-rc4

2017-12-15 Thread Linus Torvalds
On Fri, Dec 15, 2017 at 11:00 AM, Greg KH wrote: > > While there are 4 patches in here, there's really only 2, as one ion > patch got reverted due to build errors reported by 0-day. Since the revert was for the previous commit and the two were the top two commits, I just pulled the two actual fix

Re: [PATCH 1/2] kconfig: use bool instead of boolean for type definition attributes, again

2017-12-15 Thread Greg Kroah-Hartman
On Sat, Dec 16, 2017 at 12:38:01AM +0900, Masahiro Yamada wrote: > Commit 6341e62b212a ("kconfig: use bool instead of boolean for type > definition attributes") did treewide replacement of 'boolean', and > also mentioned the keyword 'boolean' would be dropped later on. > > Some years have passed,

[GIT PULL] Staging driver fixes for 4.15-rc4

2017-12-15 Thread Greg KH
The following changes since commit 73996933b53ff396d63a7fccd8e824758634dc19: Merge tag 'staging-4.15-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging (2017-12-05 09:57:34 -0800) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh

Re: [staging:staging-linus 3/3] drivers/staging//android/ion/ion_cma_heap.c:47:14: error: 'CONFIG_CMA_ALIGNMENT' undeclared; did you mean 'CONFIG_CMA_AREAS'?

2017-12-15 Thread Greg Kroah-Hartman
On Wed, Dec 13, 2017 at 12:04:55PM -0800, John Stultz wrote: > On Tue, Dec 12, 2017 at 10:25 PM, kbuild test robot > wrote: > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git > > staging-linus > > head: d98e6dbf42f73101128885a1e0ae672cd92b2e1a > > commit: d98e6dbf42f

[PATCH 1/2] kconfig: use bool instead of boolean for type definition attributes, again

2017-12-15 Thread Masahiro Yamada
Commit 6341e62b212a ("kconfig: use bool instead of boolean for type definition attributes") did treewide replacement of 'boolean', and also mentioned the keyword 'boolean' would be dropped later on. Some years have passed, but it has not happened yet. Meanwhile, some new instances have come up.

Re: [PATCH v2 0/7] x86/kvm/hyperv: stable clocksorce for L2 guests when running nested KVM on Hyper-V

2017-12-15 Thread Vitaly Kuznetsov
Paolo Bonzini writes: > On 13/12/2017 16:09, Vitaly Kuznetsov wrote: >> Currently, KVM passes PVCLOCK_TSC_STABLE_BIT to its guests when running in >> so called 'masterclock' mode and this is only possible when the clocksource >> on the host is TSC. When running nested on Hyper-V we're using a dif

Re: [PATCH v2 0/7] x86/kvm/hyperv: stable clocksorce for L2 guests when running nested KVM on Hyper-V

2017-12-15 Thread Paolo Bonzini
On 13/12/2017 16:09, Vitaly Kuznetsov wrote: > Currently, KVM passes PVCLOCK_TSC_STABLE_BIT to its guests when running in > so called 'masterclock' mode and this is only possible when the clocksource > on the host is TSC. When running nested on Hyper-V we're using a different > clocksource in L1 (H