[PATCH 3/4] staging: speakup: in serialio.c no over 80 chars long

2017-06-05 Thread Bo YU
Fixed the checkpatch.pl warning: WARNING: line over 80 characters Signed-off-by: Bo YU --- drivers/staging/speakup/serialio.c |6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/staging/speakup/serialio.c b/drivers/staging/speakup/serialio.c index f38eb66943bf.

[PATCH 4/4] staging: speakup: alignment match open parens

2017-06-05 Thread Bo YU
I have aligned argument with parenthesis, so checkpatch no check also. Signed-off-by: Bo YU --- drivers/staging/speakup/serialio.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/speakup/serialio.c b/drivers/staging/speakup/serialio.c index 00b25d3591d2..9

[PATCH 2/4] staging: speakup: add a space around '|'

2017-06-05 Thread Bo YU
Add a space around logical symbol '|' to wipe out checkpatch check Signed-off-by: Bo YU --- drivers/staging/speakup/serialio.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/speakup/serialio.c b/drivers/staging/speakup/serialio.c index 8d2f7c672cc6..f38eb

[PATCH 1/4] staging: speakup: add a missing blank line after declaration

2017-06-05 Thread Bo YU
Fixed checkpatch warning by adding a blank line after declare expression Signed-off-by: Bo YU --- drivers/staging/speakup/serialio.c |1 + 1 file changed, 1 insertion(+) diff --git a/drivers/staging/speakup/serialio.c b/drivers/staging/speakup/serialio.c index 969373201356..8d2f7c672cc6 10

[PATCH 0/4] staging: speakup: fix code style

2017-06-05 Thread Bo YU
As checkpatch.pl reported, i fixed these complaint one by one. Maybe patch 04 depend on patch 02. Thanks! Bo YU (4): staging: speakup: add a missing blank line after declaration staging: speakup: add a space around '|' staging: speakup: in serialio.c no over 80 chars long staging: speakup

Re: ks7010 firmware upload fail

2017-06-05 Thread Tobin C. Harding
On Mon, Jun 05, 2017 at 08:07:40PM -0400, Brian Masney wrote: > On Mon, Jun 05, 2017 at 08:24:44PM +1000, Tobin C. Harding wrote: > > On Mon, Jun 05, 2017 at 09:22:12AM +0200, Wolfram Sang wrote: > > > Tobin, > > > > > > > My question is should I be digging further into the MMC code or be doing >

Re: ks7010 firmware upload fail

2017-06-05 Thread Brian Masney
On Mon, Jun 05, 2017 at 08:24:44PM +1000, Tobin C. Harding wrote: > On Mon, Jun 05, 2017 at 09:22:12AM +0200, Wolfram Sang wrote: > > Tobin, > > > > > My question is should I be digging further into the MMC code or be doing > > > something else with the driver code? > > > > So, you haven't found

[PATCH 2/3] Documentation: Move visorbus documentation from staging to Documentation/

2017-06-05 Thread David Kershner
This patch simply does a git mv of the drivers/staging/unisys/Documentation directory to Documentation. It also renames overview.txt to visorbus.txt and renames sysfs-platform-visorchipset to the correct name sysfs-bus-visorbus. Signed-off-by: David Kershner Reviewed-by: Tim Sell --- .../ABI/st

[PATCH 3/3] drivers: virt: Add visorbus to the drivers/virt directory

2017-06-05 Thread David Kershner
This patch moves visorbus from drivers/staging/visorbus to drivers/virt. Signed-off-by: David Kershner Reviewed-by: Tim Sell --- MAINTAINERS | 1 + drivers/staging/unisys/Kconfig | 1 - drivers/staging/unisys/Makefil

[PATCH 1/3] include: linux: visorbus: Add visorbus to include/linux directory

2017-06-05 Thread David Kershner
Update include/linux to include the s-Par drivers set's common header files, which are needed for the s-Par visorbus. Since the include directories are now moved to include/linux/visorbus, this patch makes all the s-Par drivers (visorbus, visorinput, visornic, and visorhba) use the new include fo

[PATCH 0/3] move visorbus out of staging to drivers/virt/visorbus

2017-06-05 Thread David Kershner
This patchset moves drivers/staging/unisys/include to include/linux/visorbus, and moves drivers/staging/unisys/visorbus to drivers/virt/visorbus. David Kershner (3): include: linux: visorbus: Add visorbus to include/linux directory Documentation: Move visorbus documentation from staging to

Re: Firmware for staging atomisp driver

2017-06-05 Thread Alan Cox
> I'm asking because that is hard to believe given e.g. the recursion bug > I've just fixed. It was kind of working yes (with libxcam and a simple test tool). The recursion one was my fault. I didn't mean that one to go upstream as I was still debugging it. The older code handled it right until I

Re: [PATCH v4 10/10] tracing/hyper-v: trace hyperv_mmu_flush_tlb_others()

2017-06-05 Thread Vitaly Kuznetsov
Steven Rostedt writes: > On Wed, 24 May 2017 14:04:05 +0200 > Vitaly Kuznetsov wrote: > >> Add Hyper-V tracing subsystem and trace hyperv_mmu_flush_tlb_others(). >> Tracing is done the same way we do xen_mmu_flush_tlb_others(). >> >> Signed-off-by: Vitaly Kuznetsov >> Acked-by: K. Y. Srinivasa

Re: [PATCH v4 10/10] tracing/hyper-v: trace hyperv_mmu_flush_tlb_others()

2017-06-05 Thread Steven Rostedt
On Wed, 24 May 2017 14:04:05 +0200 Vitaly Kuznetsov wrote: > Add Hyper-V tracing subsystem and trace hyperv_mmu_flush_tlb_others(). > Tracing is done the same way we do xen_mmu_flush_tlb_others(). > > Signed-off-by: Vitaly Kuznetsov > Acked-by: K. Y. Srinivasan > Tested-by: Simon Xiao > Teste

Re: [PATCH v4 02/10] x86/hyper-v: stash the max number of virtual/logical processor

2017-06-05 Thread Stephen Hemminger
On Mon, 5 Jun 2017 11:24:27 -0400 Steven Rostedt wrote: > On Sat, 27 May 2017 20:43:58 +0300 > Andy Shevchenko wrote: > > > On Wed, May 24, 2017 at 3:03 PM, Vitaly Kuznetsov > > wrote: > > > Max virtual processor will be needed for 'extended' hypercalls supporting > > > more than 64 vCPUs.

Re: [PATCH v4 02/10] x86/hyper-v: stash the max number of virtual/logical processor

2017-06-05 Thread Steven Rostedt
On Sat, 27 May 2017 20:43:58 +0300 Andy Shevchenko wrote: > On Wed, May 24, 2017 at 3:03 PM, Vitaly Kuznetsov wrote: > > Max virtual processor will be needed for 'extended' hypercalls supporting > > more than 64 vCPUs. While on it, unify on 'Hyper-V' in mshyperv.c as we > > currently have a mix,

Re: ks7010 firmware upload fail

2017-06-05 Thread Tobin C. Harding
On Mon, Jun 05, 2017 at 09:22:12AM +0200, Wolfram Sang wrote: > Tobin, > > > My question is should I be digging further into the MMC code or be doing > > something else with the driver code? > > So, you haven't found any branch that worked? No plain v4.9 or the > gen3-sdio branch from my tree? I

[PATCH][V2] staging: rtl8723bs: fix a couple of spelling mistakes

2017-06-05 Thread Colin King
From: Colin Ian King Replace cant with cannot, argumetns with arguments and add line break to overly long DBG_871X statement. Signed-off-by: Colin Ian King --- drivers/staging/rtl8723bs/hal/hal_com.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/staging/rtl87

[PATCH V2] staging: rt5208: Fix a sleep-in-atomic bug in xd_copy_page

2017-06-05 Thread Jia-Ju Bai
The driver may sleep under a spin lock, and the function call path is: rtsx_exclusive_enter_ss (acquire the lock by spin_lock) rtsx_enter_ss rtsx_power_off_card xd_cleanup_work xd_delay_write xd_finish_write xd_copy_page wait_timeout

[PATCH V2] staging: rt5208: Fix a sleep-in-atomic bug in xd_copy_page

2017-06-05 Thread Jia-Ju Bai
The driver may sleep under a spin lock, and the function call path is: rtsx_exclusive_enter_ss (acquire the lock by spin_lock) rtsx_enter_ss rtsx_power_off_card xd_cleanup_work xd_delay_write xd_finish_write xd_copy_page wait_timeout

Re: ks7010 firmware upload fail

2017-06-05 Thread Wolfram Sang
Tobin, > My question is should I be digging further into the MMC code or be doing > something else with the driver code? So, you haven't found any branch that worked? No plain v4.9 or the gen3-sdio branch from my tree? Regards, Wolfram signature.asc Description: PGP signature