[patch] staging: cxt1e1: cleanup mfg_template[] a bit

2014-01-23 Thread Dan Carpenter
1) Make it static. 2) Change it to u8 data instead of short. 3) This means we can memcpy() it to the correct location instead of using a for loop. 4) With memcpy() we can use the union member we want directly instead of copying to the generic .bytes union member. Signed-off-by: Dan

Re: [PATCH] staging: usbip: convert usbip-host driver to usb_device_driver

2014-01-23 Thread Valentina Manea
On Thu, Jan 23, 2014 at 9:09 PM, Greg KH gre...@linuxfoundation.org wrote: On Thu, Jan 23, 2014 at 08:36:46PM +0200, Valentina Manea wrote: This driver was previously an interface driver. Since USB/IP exports a whole device, not just an interface, it would make sense to be a device driver.

Re: [PATCH] staging: usbip: convert usbip-host driver to usb_device_driver

2014-01-23 Thread Greg KH
On Thu, Jan 23, 2014 at 09:37:28PM +0200, Valentina Manea wrote: On Thu, Jan 23, 2014 at 9:09 PM, Greg KH gre...@linuxfoundation.org wrote: On Thu, Jan 23, 2014 at 08:36:46PM +0200, Valentina Manea wrote: This driver was previously an interface driver. Since USB/IP exports a whole device,

[PATCH v2] staging: usbip: convert usbip-host driver to usb_device_driver

2014-01-23 Thread Valentina Manea
This driver was previously an interface driver. Since USB/IP exports a whole device, not just an interface, it would make sense to be a device driver. This patch also modifies the way userspace sees and uses a shared device: * the usbip_status file is no longer created for interface 0, but for

Re: [PATCH] staging: usbip: convert usbip-host driver to usb_device_driver

2014-01-23 Thread Valentina Manea
If you don't bind the interfaces, they will naturally bind to their normal drivers on the host. You probably don't want that to happen. (Although, at the moment, I don't see how you can prevent it.) That's true but, the way I see USB/IP general use case, the drivers from the host the device

[PATCH v3] staging: usbip: convert usbip-host driver to usb_device_driver

2014-01-23 Thread Valentina Manea
This driver was previously an interface driver. Since USB/IP exports a whole device, not just an interface, it would make sense to be a device driver. This patch also modifies the way userspace sees and uses a shared device: * the usbip_status file is no longer created for interface 0, but for

[PATCH 5/5] lustre: add myself to list of people to CC on lustre patches

2014-01-23 Thread Oleg Drokin
Signed-off-by: Oleg Drokin oleg.dro...@intel.com --- drivers/staging/lustre/TODO | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/staging/lustre/TODO b/drivers/staging/lustre/TODO index 22742d6..0a2b6cb 100644 --- a/drivers/staging/lustre/TODO +++

[PATCH 2/5] staging/lustre/lnet: Fix use after free in ksocknal_send

2014-01-23 Thread Oleg Drokin
Call to ksocknal_launch_packet might schedule a callback that might free the just sent message, and so subsequent access to it via lntmsg-msg_vmflush goes to freed memory. Instead we'll just remember if we are in the vmflush thread and only restore if we happened to set mempressure flag.

[PATCH 0/5] Lustre fixes from my testing

2014-01-23 Thread Oleg Drokin
I just deployed a mainline lustre client in my test system. These patches below are for stuff that causes crashes or other issues in my (so far) very basic sanity testing (more to come). The patches mostly originate from our main tree, but I decided to prioritize these as they disrupt my testing,

[PATCH 1/5] staging/lustre: fix compile warning with is_vmalloc_addr

2014-01-23 Thread Oleg Drokin
Recent commit 175f5475fb9c5800319da4e3c4204413d7280f5c introduced this compile warning (because vaddr is unsigned long), so add a cast: drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c: In function ‘kiblnd_kvaddr_to_page’: drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c:532:2:

[PATCH 4/5] lustre: Correct KUC code max changelog msg size

2014-01-23 Thread Oleg Drokin
The kernel to userspace communication routines (KUC) allocate and limit the maximum cs_buf size to CR_MAXSIZE. However this fails to account for the fact that the buffer is assumed to begin with a struct kuc_hdr. To allocate and account for that space, we introduce a new define,

[PATCH 3/5] lustre: Account for changelog_ext_rec in CR_MAXSIZE

2014-01-23 Thread Oleg Drokin
CR_MAXSIZE needs to account for an llog_changelog_rec that actually contains a changelog_ext_rec structure rather than a changelog_rec. With out doing so, a file size approaching the Linux kernel NAME_MAX length that is renamed to a size also close to, or at, NAME_MAX will exceed CR_MAXSIZE and

Re: [PATCH 5/5] lustre: add myself to list of people to CC on lustre patches

2014-01-23 Thread Oleg Drokin
Hello! +STAGING - LUSTRE +M: Andreas Dilger andreas.dil...@intel.com +M: Oleg Drokin oleg.dro...@intel.com +M: Peng Tao tao.p...@emc.com. +L: hpdd-discuss hpdd-disc...@lists.01.org +S: Odd Fixes Actually we are at least Maintained here, if not outright Supported. Bye, Oleg

[PATCH] x86, hyperv: bypass the timer_irq_works() check

2014-01-23 Thread Jason Wang
This patch bypass the timer_irq_works() check for hyperv guest since: - It was guaranteed to work. - timer_irq_works() may fail sometime due to the lpj calibration were inaccurate in a hyperv guest or a buggy host. In the future, we should get the tsc frequency from hypervisor and use preset