[PATCH v2 1/2] timekeeping: add EXPORT_SYMBOL_GPL for do_adjtimex()

2014-10-15 Thread Thomas Shao
Export do_adjtimex function for hyper-v Time Synchronization component Signed-off-by: Thomas Shao --- kernel/time/timekeeping.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c index ec1791f..205a4b3 100644 --- a/kerne

[PATCH v2 2/2] hyperv: Implement Time Synchronization using host time sample

2014-10-15 Thread Thomas Shao
In current hyper-v time sync service,it only gets the initial clock time from the host. It didn't process the following time samples. This change introduced a module parameter called host_time_sync. If it is set to true, the guest will periodically sychronize it's time with the host clock using hos

Re: [PATCH 0/5] staging: comedi: usbdux drivers: tidy up urb completion

2014-10-15 Thread Ian Abbott
On 14/10/14 20:14, H Hartley Sweeten wrote: Tidy up the usb completion functions in the usbdux drivers by introducing some helper functions to handle and resubmit the successful urbs. This allows a common exit path to be used in the completion handler to stop the async command, if necessary, and

Re: [PATCH v2 2/2] hyperv: Implement Time Synchronization using host time sample

2014-10-15 Thread Richard Cochran
You really need to put John Stultz onto CC. Thanks, Richard ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

Re: [PATCH 00/34] staging: comedi: addi-data: remove "common" code bloat

2014-10-15 Thread Ian Abbott
On 14/10/14 18:44, H Hartley Sweeten wrote: The ADDI-DATA drivers all originally use some "common" code to provide the comedi driver attach/detach. This "common" code added a lot of bloat to the drivers due to the boardinfo and private data definitions. Most of the ADDI-DATA drivers have been sep

Re: [PATCH] staging: dgnc: Fix a possible crash when the class_create fails

2014-10-15 Thread Dan Carpenter
On Mon, Oct 13, 2014 at 10:26:54PM +0530, devendrana...@gmail.com wrote: > From: Devendra Naga > Just fix your email client, so the from header is correct. These From headers should be for when you forward an email from someone else. > The class_create function can return a pointer with an err

Re: [PATCH v2 2/2] hyperv: Implement Time Synchronization using host time sample

2014-10-15 Thread Richard Cochran
On Wed, Oct 15, 2014 at 01:40:04AM -0700, Thomas Shao wrote: > In current hyper-v time sync service,it only gets the initial clock time > from the host. It didn't process the following time samples. This change > introduced a module parameter called host_time_sync. If it is set to true, > the guest

RE: [PATCH v2 2/2] hyperv: Implement Time Synchronization using host time sample

2014-10-15 Thread Thomas Shao
> -Original Message- > From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- > ow...@vger.kernel.org] On Behalf Of Richard Cochran > Sent: Wednesday, October 15, 2014 5:13 PM > To: Thomas Shao > Cc: t...@linutronix.de; gre...@linuxfoundation.org; linux- > ker...@vger.kernel.org; d

RE: [PATCH v2 2/2] hyperv: Implement Time Synchronization using host time sample

2014-10-15 Thread Thomas Shao
> -Original Message- > From: Richard Cochran [mailto:richardcoch...@gmail.com] > Sent: Wednesday, October 15, 2014 5:18 PM > To: Thomas Shao > Cc: t...@linutronix.de; gre...@linuxfoundation.org; linux- > ker...@vger.kernel.org; de...@linuxdriverproject.org; o...@aepfle.de; > a...@canonical

Re: [PATCH v2 2/2] hyperv: Implement Time Synchronization using host time sample

2014-10-15 Thread Richard Cochran
On Wed, Oct 15, 2014 at 09:21:33AM +, Thomas Shao wrote: > > In V2, I address all the Dan's comments. It is customary to detail the changes in each patch series revision, in order to make things easier for the reviewers. Thanks, Richard ___ devel m

RE: [PATCH v2 2/2] hyperv: Implement Time Synchronization using host time sample

2014-10-15 Thread Thomas Shao
> -Original Message- > From: Richard Cochran [mailto:richardcoch...@gmail.com] > Sent: Wednesday, October 15, 2014 5:43 PM > To: Thomas Shao > Cc: t...@linutronix.de; gre...@linuxfoundation.org; linux- > ker...@vger.kernel.org; de...@linuxdriverproject.org; o...@aepfle.de; > a...@canonical

[PATCH] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Jeff Kirsher
The Beceem WIMAX was generating compile warnings on 64bit machines, which were: drivers/staging/bcm/CmHost.c: In function ‘StoreCmControlResponseMessage’: drivers/staging/bcm/CmHost.c:1503:3: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] (struct bcm_connect_mg

Re: [PATCH] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Joe Perches
On Wed, 2014-10-15 at 05:26 -0700, Jeff Kirsher wrote: > The Beceem WIMAX was generating compile warnings on 64bit machines, > which were: > > drivers/staging/bcm/CmHost.c: In function ‘StoreCmControlResponseMessage’: > drivers/staging/bcm/CmHost.c:1503:3: warning: cast to pointer from integer of

Re: [PATCH] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Dan Carpenter
On Wed, Oct 15, 2014 at 05:26:39AM -0700, Jeff Kirsher wrote: > The Beceem WIMAX was generating compile warnings on 64bit machines, > which were: > > drivers/staging/bcm/CmHost.c: In function ‘StoreCmControlResponseMessage’: > drivers/staging/bcm/CmHost.c:1503:3: warning: cast to pointer from inte

Re: [PATCH] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Dan Carpenter
Or we could fix it but add a multi-line comment with lots of capital letters and exclamation marks. I guess we would need to make a function since this cast is in several places. void *silence_buggy_casting(u32 pointer) { /* * DANGER! DANGER! DANGER! DANGER! DANGER! DANGER! DANGE

Re: [PATCH] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Jeff Kirsher
On Wed, 2014-10-15 at 15:59 +0300, Dan Carpenter wrote: > Or we could fix it but add a multi-line comment with lots of capital > letters and exclamation marks. I guess we would need to make a > function > since this cast is in several places. > > void *silence_buggy_casting(u32 pointer) > { >

Re: [PATCH] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Joe Perches
On Wed, 2014-10-15 at 06:03 -0700, Jeff Kirsher wrote: [] > I thought I remember Greg saying something about getting rid of this > driver anyway, but I could be wrong. If Greg decides to keep this > driver around, then I think we should something like your suggestion > above. Or maybe just make t

Re: [PATCH] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Jeff Kirsher
On Wed, 2014-10-15 at 09:11 -0700, Joe Perches wrote: > On Wed, 2014-10-15 at 06:03 -0700, Jeff Kirsher wrote: > [] > > I thought I remember Greg saying something about getting rid of this > > driver anyway, but I could be wrong. If Greg decides to keep this > > driver around, then I think we shou

Re: [PATCH] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Fabio Estevam
On Wed, Oct 15, 2014 at 2:42 PM, Jeff Kirsher wrote: > I like the idea, but won't this exclude other 32 bit systems like MIPS > and I am sure there might be others. I could assume that Beceem WIMAX > was intended for x86 arch's that are 32 bit only, which may be a safe > bet. The only thing we

Re: [PATCH] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Jeff Kirsher
On Wed, 2014-10-15 at 15:24 -0300, Fabio Estevam wrote: > On Wed, Oct 15, 2014 at 2:42 PM, Jeff Kirsher > wrote: > > > I like the idea, but won't this exclude other 32 bit systems like MIPS > > and I am sure there might be others. I could assume that Beceem WIMAX > > was intended for x86 arch's

Re: [PATCH] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Fabio Estevam
On Wed, Oct 15, 2014 at 3:54 PM, Jeff Kirsher wrote: > On Wed, 2014-10-15 at 15:24 -0300, Fabio Estevam wrote: >> On Wed, Oct 15, 2014 at 2:42 PM, Jeff Kirsher >> wrote: >> >> > I like the idea, but won't this exclude other 32 bit systems like MIPS >> > and I am sure there might be others. I cou

[PATCH v2] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Jeff Kirsher
From: Fabio Estevam The Beceem WIMAX was generating compile warnings on 64bit machines, which were: drivers/staging/bcm/CmHost.c: In function ‘StoreCmControlResponseMessage’: drivers/staging/bcm/CmHost.c:1503:3: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]

Re: [PATCH] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Joe Perches
On Wed, 2014-10-15 at 11:54 -0700, Jeff Kirsher wrote: > On Wed, 2014-10-15 at 15:24 -0300, Fabio Estevam wrote: > > On Wed, Oct 15, 2014 at 2:42 PM, Jeff Kirsher > > wrote: > > > > > I like the idea, but won't this exclude other 32 bit systems like MIPS > > > and I am sure there might be others.

Re: [PATCH] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Dan Carpenter
On Wed, Oct 15, 2014 at 09:11:36AM -0700, Joe Perches wrote: > On Wed, 2014-10-15 at 06:03 -0700, Jeff Kirsher wrote: > [] > > I thought I remember Greg saying something about getting rid of this > > driver anyway, but I could be wrong. If Greg decides to keep this > > driver around, then I think

Re: [PATCH v2] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Dan Carpenter
On Wed, Oct 15, 2014 at 12:01:41PM -0700, Jeff Kirsher wrote: > From: Fabio Estevam > > The Beceem WIMAX was generating compile warnings on 64bit machines, > which were: > > drivers/staging/bcm/CmHost.c: In function ‘StoreCmControlResponseMessage’: > drivers/staging/bcm/CmHost.c:1503:3: warning:

Re: [PATCH] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Joe Perches
On Wed, 2014-10-15 at 22:53 +0300, Dan Carpenter wrote: > On Wed, Oct 15, 2014 at 09:11:36AM -0700, Joe Perches wrote: > > On Wed, 2014-10-15 at 06:03 -0700, Jeff Kirsher wrote: > > [] > > > I thought I remember Greg saying something about getting rid of this > > > driver anyway, but I could be wro

Re: [PATCH v2] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Jeff Kirsher
On Wed, 2014-10-15 at 22:55 +0300, Dan Carpenter wrote: > On Wed, Oct 15, 2014 at 12:01:41PM -0700, Jeff Kirsher wrote: > > From: Fabio Estevam > > > > The Beceem WIMAX was generating compile warnings on 64bit machines, > > which were: > > > > drivers/staging/bcm/CmHost.c: In function ‘StoreCmCo

[PATCH] staging: comedi: ii_pci20kc: add CONFIG_HAS_IOMEM dependence

2014-10-15 Thread David Cohen
ii_pci20kc uses io memory which makes it not compilable on architectures without HAS_IOMEM such as UML: CC drivers/net/wireless/ti/wl1251/main.o drivers/staging/comedi/drivers/ii_pci20kc.c: In function ‘ii20k_attach’: drivers/staging/comedi/drivers/ii_pci20kc.c:442:2: error: implicit declar

Re: [PATCH] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Matthias Beyer
On 15-10-2014 06:03:33, Jeff Kirsher wrote: > > I thought I remember Greg saying something about getting rid of this > driver anyway, but I could be wrong. If Greg decides to keep this > driver around, then I think we should something like your suggestion > above. Let me throw in my comment here

Re: [PATCH] staging: comedi: ii_pci20kc: add CONFIG_HAS_IOMEM dependence

2014-10-15 Thread Ian Abbott
On 15/10/14 22:25, David Cohen wrote: ii_pci20kc uses io memory which makes it not compilable on architectures without HAS_IOMEM such as UML: CC drivers/net/wireless/ti/wl1251/main.o drivers/staging/comedi/drivers/ii_pci20kc.c: In function ‘ii20k_attach’: drivers/staging/comedi/drivers/i

Re: [PATCH] staging: comedi: ii_pci20kc: add CONFIG_HAS_IOMEM dependence

2014-10-15 Thread David Cohen
On Wed, Oct 15, 2014 at 10:57:00PM +0100, Ian Abbott wrote: > On 15/10/14 22:25, David Cohen wrote: > >ii_pci20kc uses io memory which makes it not compilable on architectures > >without HAS_IOMEM such as UML: > > > > CC drivers/net/wireless/ti/wl1251/main.o > >drivers/staging/comedi/drivers

Re: [PATCH] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Jeff Kirsher
On Wed, 2014-10-15 at 23:41 +0200, Matthias Beyer wrote: > On 15-10-2014 06:03:33, Jeff Kirsher wrote: > > > > I thought I remember Greg saying something about getting rid of this > > driver anyway, but I could be wrong. If Greg decides to keep this > > driver around, then I think we should somet

Re: [PATCH] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Matthias Beyer
On 15-10-2014 15:19:44, Jeff Kirsher wrote: > I will just go ahead and create a patch to remove the driver. Greg can > then decide to either accept the patch to fix the Kconfig or accept the > patch to remove the driver. Don't forget the maintainers file :-) -- Mit freundlichen Grüßen, Kind reg

Re: [PATCH] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Jeff Kirsher
On Thu, 2014-10-16 at 00:24 +0200, Matthias Beyer wrote: > On 15-10-2014 15:19:44, Jeff Kirsher wrote: > > I will just go ahead and create a patch to remove the driver. Greg > can > > then decide to either accept the patch to fix the Kconfig or accept > the > > patch to remove the driver. > > Don

Re: [PATCH v2] bcm/CmHost.c: Fix noisy compile warnings

2014-10-15 Thread Jeff Kirsher
On Wed, 2014-10-15 at 12:01 -0700, Jeff Kirsher wrote: > From: Fabio Estevam > > The Beceem WIMAX was generating compile warnings on 64bit machines, > which were: > > drivers/staging/bcm/CmHost.c: In function ‘StoreCmControlResponseMessage’: > drivers/staging/bcm/CmHost.c:1503:3: warning: cast t

[PATCH] drivers: staging: imx-drm Fix checkpatch warning

2014-10-15 Thread Gaston Gonzalez
Fix line over 80 characters in imx-tve.c Signed-off-by: Gaston Gonzalez --- drivers/staging/imx-drm/imx-tve.c |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/staging/imx-drm/imx-tve.c b/drivers/staging/imx-drm/imx-tve.c index 3e8b0a1..a46905f 100644 --- a/driver