[PATCH -next] staging: fsl-mc: remove .owner field for driver

From: Wei Yongjun Remove .owner field if calls are used which set it automatically. Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci Signed-off-by: Wei Yongjun --- drivers/staging/fsl-mc/bus/fsl-mc-allocator.c | 1 - 1 file

[PATCH -next] staging: fsl-mc: use list_del_init instead of list_del/INIT_LIST_HEAD

From: Wei Yongjun Using list_del_init() instead of list_del() + INIT_LIST_HEAD(). Signed-off-by: Wei Yongjun --- drivers/staging/fsl-mc/bus/fsl-mc-allocator.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git

[PATCH -next] staging: android: ion: Fix return value check in hi6220_ion_probe()

From: Wei Yongjun In case of error, the function ion_device_create() returns ERR_PTR() and never returns NULL. The NULL test in the return value check should be replaced with IS_ERR(). Signed-off-by: Wei Yongjun ---

[PATCH 2/2 v2] pci-hyperv: lock pci bus on device eject

From: Long Li A PCI_EJECT message can arrive at the same time we are calling pci_scan_child_bus in the workqueue for the previous PCI_BUS_RELATIONS message or in create_root_hv_pci_bus(), in this case we could potentailly modify the bus from multiple places. Properly

[PATCH 1/2 v2] pci-hyperv: properly handle pci bus remove

From: Long Li hv_pci_devices_present is called in hv_pci_remove when we remove a PCI device from host (e.g. by disabling SRIOV on a device). In hv_pci_remove, the bus is already removed before the call, so we don't need to rescan the bus in the workqueue scheduled from

Re: [RFC 2/3] staging: rtl8712: Change _LED_STATE enum in rtl871x driver to avoid conflicts with LED namespace

On 09/14/2016 04:55 PM, Zach Brown wrote: Adding led support for phy causes namespace conflicts for some phy drivers. The rtl871 driver declared an enum for representing LED states. The enum contains constant LED_OFF which conflicted with declartation found in linux/leds.h. LED_OFF changed to

Re: [RFC 3/3] phy,leds: add support for led triggers on phy link state change

On 09/14/2016 02:55 PM, Zach Brown wrote: > From: Josh Cartwright > > Create an option CONFIG_LED_TRIGGER_PHY (default n), which will > create a set of led triggers for each instantiated PHY device. There is > one LED trigger per link-speed, per-phy. > > This allows for

[RFC 2/3] staging: rtl8712: Change _LED_STATE enum in rtl871x driver to avoid conflicts with LED namespace

Adding led support for phy causes namespace conflicts for some phy drivers. The rtl871 driver declared an enum for representing LED states. The enum contains constant LED_OFF which conflicted with declartation found in linux/leds.h. LED_OFF changed to LED_STATE_OFF Signed-off-by: Zach Brown

[RFC 3/3] phy, leds: add support for led triggers on phy link state change

From: Josh Cartwright Create an option CONFIG_LED_TRIGGER_PHY (default n), which will create a set of led triggers for each instantiated PHY device. There is one LED trigger per link-speed, per-phy. This allows for a user to configure their system to allow a set of LEDs

[RFC 1/3] skge: Change LED_OFF to LED_REG_OFF in marvel skge driver to avoid conflicts with leds namespace

Adding led support for phy causes namespace conflicts for some phy drivers. The marvel skge driver declared an enum for representing the states of Link LED Register. The enum contained constant LED_OFF which conflicted with declartation found in linux/leds.h. LED_OFF changed to LED_REG_OFF

[RFC 0/3] Add support for led triggers on phy link state change

Some drivers that include phy.h defined LED_OFF which conflicts with definition in leds.h. phy led support uses leds.h so the two namespaces are no longer isolated. The first two patches fix the two net drivers that declared enum constants that conflict with enum constants in linux/leds.h. The

Re: drivers: staging: vme: Fixed some code style warnings

On 09/14/2016 06:31 PM, Andrew Kanner wrote: > ‎Thanks, I understood my fault, but haven't done this changes yet. I > can't understand if I should reply to original message with v2 patch or > send a new email with it? Just send the patch with your revised commit message as a new mail, and be sure

Re: [PATCH] staging: android: ion: Make ION_OF depend on OF_ADDRESS

-by: Guenter Roeck <li...@roeck-us.net> > --- > Based on next-20160914 > --- > drivers/staging/android/ion/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/staging/android/ion/Kconfig > b/drivers/staging/android/ion/Kconfig

Re: [PATCH] staging: lustre: include/lustre_net.h: Remove unnecessary space before function pointer arguments.

On Wed, Sep 14, 2016 at 06:09:09PM +0200, Richard wrote: > Greetings Linux Kernel Developers, > > This is Task 10 of the Eudyptula Challenge. These lines are not needed. > I fix few minor warnings spotted by checkpatch.pl in lustre You need to be very specific. > Signed-off-by: Richard

Re: [PATCH] android: binder: Disable preemption while holding the global binder lock

On Wed, Sep 14, 2016 at 06:13:40PM +0200, Peter Zijlstra wrote: > On Wed, Sep 14, 2016 at 06:11:03PM +0200, Peter Zijlstra wrote: > > On Tue, Sep 13, 2016 at 12:53:27PM -0700, Arve Hjønnevåg wrote: > > > On Tue, Sep 13, 2016 at 12:32 AM, Peter Zijlstra > > > wrote: > > > >

Re: drivers: staging: vme: Fixed some code style warnings

‎Thanks, I understood my fault, but haven't done this changes yet. I can't understand if I should reply to original message with v2 patch or send a new email with it?   Исходное сообщение   От: Markus Böhme Отправлено: среда, 14 сентября 2016 г., 15:56 Кому: Andrew Kanner;

RE: [PATCH 2/2] pci-hyperv: properly handle device eject

> -Original Message- > From: Dexuan Cui > Sent: Tuesday, September 13, 2016 10:45 PM > To: Long Li ; KY Srinivasan ; > Haiyang Zhang ; Bjorn Helgaas > > Cc: de...@linuxdriverproject.org;

Re: [PATCH] staging: android: ion: Make ION_OF depend on OF_ADDRESS

; Add a dependency on OF_ADDRESS > > Reported-by: Guenter Roeck <li...@roeck-us.net> > Signed-off-by: Laura Abbott <labb...@redhat.com> > --- > Based on next-20160914 > --- > drivers/staging/android/ion/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1 dele

[PATCH] staging: lustre: include/lustre_net.h: Remove unnecessary space before function pointer arguments.

Greetings Linux Kernel Developers, This is Task 10 of the Eudyptula Challenge. I fix few minor warnings spotted by checkpatch.pl in lustre Signed-off-by: Richard --- drivers/staging/lustre/lustre/include/lustre_net.h | 46 +++--- 1 file changed, 23

Re: [PATCH] android: binder: Disable preemption while holding the global binder lock

On Wed, Sep 14, 2016 at 06:11:03PM +0200, Peter Zijlstra wrote: > On Tue, Sep 13, 2016 at 12:53:27PM -0700, Arve Hjønnevåg wrote: > > On Tue, Sep 13, 2016 at 12:32 AM, Peter Zijlstra > > wrote: > > > cgroups should be irrelevant, PI is unaware of them. > > > > I don't

Re: [PATCH] android: binder: Disable preemption while holding the global binder lock

On Tue, Sep 13, 2016 at 12:53:27PM -0700, Arve Hjønnevåg wrote: > On Tue, Sep 13, 2016 at 12:32 AM, Peter Zijlstra wrote: > > cgroups should be irrelevant, PI is unaware of them. > > I don't think cgroups are irrelevant. PI being unaware of them > explains the problem I

[PATCH] staging: android: ion: Make ION_OF depend on OF_ADDRESS

to `of_platform_device_create' Add a dependency on OF_ADDRESS Reported-by: Guenter Roeck <li...@roeck-us.net> Signed-off-by: Laura Abbott <labb...@redhat.com> --- Based on next-20160914 --- drivers/staging/android/ion/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dri

Re: [PATCH 1/1] Drivers: hv: hv_util: Avoid dynamic allocation in time synch

On Fri, Sep 09, k...@exchange.microsoft.com wrote: > + * This check is safe since we are executing in the > + * interrupt context and time synch messages arre always Typo. Olaf signature.asc Description: PGP signature ___ devel mailing

Re: [PATCH] android: binder: Disable preemption while holding the global binder lock

On Wed, Sep 14, 2016 at 09:10:01AM +0200, Peter Zijlstra wrote: > On Tue, Sep 13, 2016 at 12:53:27PM -0700, Arve Hjønnevåg wrote: > > Most of the tasks here are not RR/FIFO/DL tasks. I don't see anything > > in the rtmutex code or documentation that indicates that they don't > > work for normal

Re: [PATCH 3/3] Drivers: hv: utils: Support TimeSync version 4.0 protocol samples.

On Tue, Sep 13, Alex Ng (LIS) wrote: > > On Thu, Sep 08, k...@exchange.microsoft.com wrote: > > Perhaps a better approach would be to list the known existing hosts and use > > the new protocol for upcoming, unknown hosts via 'default:'. > This is a good idea. I will create another patch that

Re: drivers: staging: vme: Fixed some code style warnings

On 09/13/2016 12:31 AM, Andrew Kanner wrote: > Signed-off-by: Andrew Kanner > --- > drivers/staging/vme/devices/vme_pio2_core.c | 12 ++-- > drivers/staging/vme/devices/vme_user.c | 2 +- > 2 files changed, 7 insertions(+), 7 deletions(-) > (snip) Hello

Re: [PATCH] android: binder: Disable preemption while holding the global binder lock

On Wed, Sep 14, 2016 at 09:10:01AM +0200, Peter Zijlstra wrote: > We could define a meaningful something for CFS and implement that, but > it isn't currently done. So the generalization of the Priority Inheritance Protocol is Proxy Execution Protocol, which basically lets the boosted task run

Re: [PATCH] android: binder: Disable preemption while holding the global binder lock

On Tue, Sep 13, 2016 at 12:53:27PM -0700, Arve Hjønnevåg wrote: > On Tue, Sep 13, 2016 at 12:32 AM, Peter Zijlstra wrote: > > On Mon, Sep 12, 2016 at 08:44:09PM -0700, Arve Hjønnevåg wrote: > > > >> A previous attempt to fix this problem, changed the lock to use > >>