Re: [PATCH net-next 1/3] samples/bpf: add bpf map stress test

From: Alexei Starovoitov Date: Tue, 8 Mar 2016 15:07:52 -0800 > this test calls bpf programs from different contexts: > from inside of slub, from rcu, from pretty much everywhere, > since it kprobes all spin_lock functions. > It stresses the bpf hash and percpu map pre-allocation, >

Re: [PATCH net-next 1/3] samples/bpf: add bpf map stress test

From: Alexei Starovoitov Date: Tue, 8 Mar 2016 15:07:52 -0800 > this test calls bpf programs from different contexts: > from inside of slub, from rcu, from pretty much everywhere, > since it kprobes all spin_lock functions. > It stresses the bpf hash and percpu map pre-allocation, > deallocation

Re: [PATCH net-next 2/3] samples/bpf: stress test bpf_get_stackid

From: Alexei Starovoitov Date: Tue, 8 Mar 2016 15:07:53 -0800 > increase stress by also calling bpf_get_stackid() from > various *spin* functions > > Signed-off-by: Alexei Starovoitov Applied.

Re: [PATCH net-next 3/3] samples/bpf: add map performance test

From: Alexei Starovoitov Date: Tue, 8 Mar 2016 15:07:54 -0800 > performance tests for hash map and per-cpu hash map > with and without pre-allocation > > Signed-off-by: Alexei Starovoitov Applied.

Re: [PATCH net-next 2/3] samples/bpf: stress test bpf_get_stackid

From: Alexei Starovoitov Date: Tue, 8 Mar 2016 15:07:53 -0800 > increase stress by also calling bpf_get_stackid() from > various *spin* functions > > Signed-off-by: Alexei Starovoitov Applied.

Re: [PATCH net-next 3/3] samples/bpf: add map performance test

From: Alexei Starovoitov Date: Tue, 8 Mar 2016 15:07:54 -0800 > performance tests for hash map and per-cpu hash map > with and without pre-allocation > > Signed-off-by: Alexei Starovoitov Applied.

linux-next: removal of the llvmlinux tree

Hi all, I noticed that the llvmlinux tree: git://git.linuxfoundation.org/llvmlinux/kernel.git branch for-next has not been updated since November 2014. I am going to remove it from linux-next tomorrow unless you think it should be retained. It can always be added again later if it is going

linux-next: removal of the llvmlinux tree

Hi all, I noticed that the llvmlinux tree: git://git.linuxfoundation.org/llvmlinux/kernel.git branch for-next has not been updated since November 2014. I am going to remove it from linux-next tomorrow unless you think it should be retained. It can always be added again later if it is going

Re: linux-next: manual merge of the usb tree with the tip tree

On Wed, Mar 09, 2016 at 01:35:15PM +1100, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the usb tree got a conflict in: > > Documentation/kernel-parameters.txt > > between commit: > > d2aa1acad22f ("mm/init: Add 'rodata=off' boot cmdline parameter to disable >

Re: [PATCH 0/2] mm: Enable page parallel initialisation for Power

On Tue, Mar 8, 2016 at 10:45 PM, Balbir Singh wrote: > > > On 08/03/16 14:55, Li Zhang wrote: >> From: Li Zhang >> >> Uptream has supported page parallel initialisation for X86 and the >> boot time is improved greately. Some tests have been

Re: linux-next: manual merge of the usb tree with the tip tree

On Wed, Mar 09, 2016 at 01:35:15PM +1100, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the usb tree got a conflict in: > > Documentation/kernel-parameters.txt > > between commit: > > d2aa1acad22f ("mm/init: Add 'rodata=off' boot cmdline parameter to disable >

Re: [PATCH 0/2] mm: Enable page parallel initialisation for Power

On Tue, Mar 8, 2016 at 10:45 PM, Balbir Singh wrote: > > > On 08/03/16 14:55, Li Zhang wrote: >> From: Li Zhang >> >> Uptream has supported page parallel initialisation for X86 and the >> boot time is improved greately. Some tests have been done for Power. >> >> Here is the result I have done

Re: Linux 4.4.4 [regression]

On Tue, Mar 08, 2016 at 09:48:02AM +0100, Jean Delvare wrote: > On Tue, 8 Mar 2016 09:16:13 +0100, Jean Delvare wrote: > > On Thu, 3 Mar 2016 15:34:15 -0800, Greg KH wrote: > > > I'm announcing the release of the 4.4.4 kernel. > > > > > > All users of the 4.4 kernel series must upgrade. > > >

Re: Linux 4.4.4 [regression]

On Tue, Mar 08, 2016 at 09:48:02AM +0100, Jean Delvare wrote: > On Tue, 8 Mar 2016 09:16:13 +0100, Jean Delvare wrote: > > On Thu, 3 Mar 2016 15:34:15 -0800, Greg KH wrote: > > > I'm announcing the release of the 4.4.4 kernel. > > > > > > All users of the 4.4 kernel series must upgrade. > > >

Re: [PATCH 01/14] pinctrl: at91: use __maybe_unused to hide pm functions

On Wed, Mar 2, 2016 at 10:58 PM, Arnd Bergmann wrote: > The at91-pio4 pinctrl driver uses SET_SYSTEM_SLEEP_PM_OPS() to > conditionally set the correct suspend/resume options, but they > become unused when CONFIG_PM is disabled: > > drivers/pinctrl/pinctrl-at91-pio4.c:827:12:

Re: [PATCH 01/14] pinctrl: at91: use __maybe_unused to hide pm functions

On Wed, Mar 2, 2016 at 10:58 PM, Arnd Bergmann wrote: > The at91-pio4 pinctrl driver uses SET_SYSTEM_SLEEP_PM_OPS() to > conditionally set the correct suspend/resume options, but they > become unused when CONFIG_PM is disabled: > > drivers/pinctrl/pinctrl-at91-pio4.c:827:12: error:

[PATCH v5 7/7] T104xQDS: Add qe node to t104xqds

add qe node to t104xqds.dtsi Signed-off-by: Zhao Qiang --- Changes for v2 - rebase Changes for v3 - rebase Changes for v4 - rebase Changes for v5 - rebase arch/powerpc/boot/dts/fsl/t104xqds.dtsi | 38 + 1 file

[PATCH v5 7/7] T104xQDS: Add qe node to t104xqds

add qe node to t104xqds.dtsi Signed-off-by: Zhao Qiang --- Changes for v2 - rebase Changes for v3 - rebase Changes for v4 - rebase Changes for v5 - rebase arch/powerpc/boot/dts/fsl/t104xqds.dtsi | 38 + 1 file changed, 38

Re: [PATCH 2/3] mm, compaction: cover all compaction mode in compact_zone

> > From: Michal Hocko > > the compiler is complaining after "mm, compaction: change COMPACT_ > constants into enum" > > mm/compaction.c: In function ‘compact_zone’: > mm/compaction.c:1350:2: warning: enumeration value ‘COMPACT_DEFERRED’ not > handled in switch [-Wswitch] >

Re: [PATCH 2/3] mm, compaction: cover all compaction mode in compact_zone

> > From: Michal Hocko > > the compiler is complaining after "mm, compaction: change COMPACT_ > constants into enum" > > mm/compaction.c: In function ‘compact_zone’: > mm/compaction.c:1350:2: warning: enumeration value ‘COMPACT_DEFERRED’ not > handled in switch [-Wswitch] > switch (ret) { >

Re: [PATCH 1/3] mm, compaction: change COMPACT_ constants into enum

> > From: Michal Hocko > > compaction code is doing weird dances between > COMPACT_FOO -> int -> unsigned long > > but there doesn't seem to be any reason for that. All functions which > return/use one of those constants are not expecting any other value > so it really makes

Re: [PATCH 1/3] mm, compaction: change COMPACT_ constants into enum

> > From: Michal Hocko > > compaction code is doing weird dances between > COMPACT_FOO -> int -> unsigned long > > but there doesn't seem to be any reason for that. All functions which > return/use one of those constants are not expecting any other value > so it really makes sense to define an

[PATCH v5 1/7] QE: Add IC, SI and SIRAM document to device tree bindings.

Add IC, SI and SIRAM document of QE to Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe.txt Signed-off-by: Zhao Qiang Acked-by: Rob Herring --- changes for v2 - Add interrupt-controller in Required properties - delete address-cells and

[PATCH v5 1/7] QE: Add IC, SI and SIRAM document to device tree bindings.

Add IC, SI and SIRAM document of QE to Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe.txt Signed-off-by: Zhao Qiang Acked-by: Rob Herring --- changes for v2 - Add interrupt-controller in Required properties - delete address-cells and size-cells for qe-si and qe-siram

[PATCH 3/3] coresight: tmc: adding sysFS management entries

Adding management registers that convey implementation specific characteristics. Those are useful for trace configuration and collection along with general trouble shooting. Signed-off-by: Mathieu Poirier --- .../ABI/testing/sysfs-bus-coresight-devices-tmc| 77

[PATCH 3/3] coresight: tmc: adding sysFS management entries

Adding management registers that convey implementation specific characteristics. Those are useful for trace configuration and collection along with general trouble shooting. Signed-off-by: Mathieu Poirier --- .../ABI/testing/sysfs-bus-coresight-devices-tmc| 77 +++

[PATCH 2/3] coresight: etb10: splitting sysFS "status" entry

The sysFS "status" entry conveys a wealth of information about the status of the HW but goes agains the sysFS rule of one topic per file. This patch rectifies the situation by adding read-only entries for each of the field formaly displayed by "status". The ABI documentation is kept up to date.

[PATCH 2/3] coresight: etb10: splitting sysFS "status" entry

The sysFS "status" entry conveys a wealth of information about the status of the HW but goes agains the sysFS rule of one topic per file. This patch rectifies the situation by adding read-only entries for each of the field formaly displayed by "status". The ABI documentation is kept up to date.

[PATCH 0/3] coresight: sysFS conformance and enhancement

This patchset works on the registers exported to sysFS by the ETB and TMC drivers. For ETB the "status" entry is broken up to present one register per entry. On the TMC driver entries are added to convey the same information as found on ETB. To avoid code duplication the

[PATCH 1/3] coresight: moving coresight_simple_func() to header file

Macro "coresight_simple_func()" can be used by several drivers. As such making the structure type generic and moving to a globally available header file. That way individual drivers can use the functionality by simply specifying the structure they need to work with. Signed-off-by: Mathieu

[PATCH 1/3] coresight: moving coresight_simple_func() to header file

Macro "coresight_simple_func()" can be used by several drivers. As such making the structure type generic and moving to a globally available header file. That way individual drivers can use the functionality by simply specifying the structure they need to work with. Signed-off-by: Mathieu

[PATCH 0/3] coresight: sysFS conformance and enhancement

This patchset works on the registers exported to sysFS by the ETB and TMC drivers. For ETB the "status" entry is broken up to present one register per entry. On the TMC driver entries are added to convey the same information as found on ETB. To avoid code duplication the

Re: [PATCH 4.4 13/74] cifs: fix out-of-bounds access in lease parsing

On Mon, 2016-03-07 at 16:02 -0800, Greg Kroah-Hartman wrote: > 4.4-stable review patch.  If anyone has any objections, please let me know. > > -- > > From: Justin Maggard > > commit deb7deff2f00bdbbcb3d560dad2a89ef37df837d upstream. > > When opening a

Re: [PATCH 4.4 13/74] cifs: fix out-of-bounds access in lease parsing

On Mon, 2016-03-07 at 16:02 -0800, Greg Kroah-Hartman wrote: > 4.4-stable review patch.  If anyone has any objections, please let me know. > > -- > > From: Justin Maggard > > commit deb7deff2f00bdbbcb3d560dad2a89ef37df837d upstream. > > When opening a file, SMB2_open()

RE: [PATCH 2/2] dts/ls2080a: Update DSPI compatible

Hi All, Sorry for the patch: dts/ls2080a: Update DSPI compatible I was just trying to resend this patch: dts/ls2080a: update the DTS for QSPI and DSPI support https://patchwork.ozlabs.org/patch/573108/ But I have a big mistake to sending a wrong patch. Please ignore it. And I will resend the

RE: [PATCH 2/2] dts/ls2080a: Update DSPI compatible

Hi All, Sorry for the patch: dts/ls2080a: Update DSPI compatible I was just trying to resend this patch: dts/ls2080a: update the DTS for QSPI and DSPI support https://patchwork.ozlabs.org/patch/573108/ But I have a big mistake to sending a wrong patch. Please ignore it. And I will resend the

Re: [v5][PATCH] livepatch/ppc: Enable livepatching on powerpc

On 09/03/16 02:34, Torsten Duwe wrote: > On Wed, Mar 09, 2016 at 12:52:03AM +1100, Balbir Singh wrote: >> On 08/03/16 21:45, Torsten Duwe wrote: >>> To be fair, my last mail still was not 100% correct, but the conclusion > Wrote a correction to the correction. It should be clear now. Please nag

Re: [v5][PATCH] livepatch/ppc: Enable livepatching on powerpc

On 09/03/16 02:34, Torsten Duwe wrote: > On Wed, Mar 09, 2016 at 12:52:03AM +1100, Balbir Singh wrote: >> On 08/03/16 21:45, Torsten Duwe wrote: >>> To be fair, my last mail still was not 100% correct, but the conclusion > Wrote a correction to the correction. It should be clear now. Please nag

Re: [PATCH] pinctrl: uniphier: rename CONFIG options and file names

On Wed, Mar 2, 2016 at 1:14 PM, Masahiro Yamada wrote: > The current "CONFIG_PINCTRL_UNIPHIER_PH1_*" is too long. It would > not hurt to drop "PH1_" because "UNIPHIER_" already well specifies > the SoC family. Also, rename files for consistency. > >

Re: [PATCH] usb: chipidea: Configure DMA properties and ops from DT

On Tue, Mar 8, 2016 at 11:52 AM, Li Yang wrote: > On Wed, Mar 2, 2016 at 4:59 PM, Li Yang wrote: >> On Mon, Feb 22, 2016 at 4:07 PM, Bjorn Andersson >> wrote: >>> On Mon 22 Feb 02:03 PST 2016, Srinivas Kandagatla wrote: >>>

Re: [PATCH] pinctrl: uniphier: rename CONFIG options and file names

On Wed, Mar 2, 2016 at 1:14 PM, Masahiro Yamada wrote: > The current "CONFIG_PINCTRL_UNIPHIER_PH1_*" is too long. It would > not hurt to drop "PH1_" because "UNIPHIER_" already well specifies > the SoC family. Also, rename files for consistency. > > Signed-off-by: Masahiro Yamada Patch

Re: [PATCH] usb: chipidea: Configure DMA properties and ops from DT

On Tue, Mar 8, 2016 at 11:52 AM, Li Yang wrote: > On Wed, Mar 2, 2016 at 4:59 PM, Li Yang wrote: >> On Mon, Feb 22, 2016 at 4:07 PM, Bjorn Andersson >> wrote: >>> On Mon 22 Feb 02:03 PST 2016, Srinivas Kandagatla wrote: >>> On 22/02/16 05:32, Bjorn Andersson wrote: >On

Re: [RESEND PATCH v7] mtd: spi-nor: add hisilicon spi-nor flash controller driver

Hi Boris, On 2016/3/8 17:46, Boris Brezillon wrote: >> [...] +static int hisi_spi_nor_read_reg(struct spi_nor *nor, u8 opcode, u8 *buf, + int len) +{ + struct hifmc_priv *priv = nor->priv; + struct hifmc_host *host = priv->host; + int ret; + +

Re: [RESEND PATCH v7] mtd: spi-nor: add hisilicon spi-nor flash controller driver

Hi Boris, On 2016/3/8 17:46, Boris Brezillon wrote: >> [...] +static int hisi_spi_nor_read_reg(struct spi_nor *nor, u8 opcode, u8 *buf, + int len) +{ + struct hifmc_priv *priv = nor->priv; + struct hifmc_host *host = priv->host; + int ret; + +

Re: [v5][PATCH] livepatch/ppc: Enable livepatching on powerpc

On 09/03/16 03:02, Petr Mladek wrote: > On Tue 2016-03-08 18:33:57, Balbir Singh wrote: >> Changelog v5: >> 1. Removed the mini-stack frame created for klp_return_helper. >> As a result of the mini-stack frame, function with > 8 >> arguments could not be patched >> 2.

Re: [v5][PATCH] livepatch/ppc: Enable livepatching on powerpc

On 09/03/16 03:02, Petr Mladek wrote: > On Tue 2016-03-08 18:33:57, Balbir Singh wrote: >> Changelog v5: >> 1. Removed the mini-stack frame created for klp_return_helper. >> As a result of the mini-stack frame, function with > 8 >> arguments could not be patched >> 2.

linux-next: manual merge of the gpio tree with the mfd tree

Hi Linus, Today's linux-next merge of the gpio tree got a conflict in: drivers/gpio/gpio-tps65912.c between commits: 65b6555971d0 ("mfd: tps65912: Remove old driver in preparation for new driver") ca801a22f465 ("gpio: tps65912: Add GPIO driver for the TPS65912 PMIC") from the mfd tree

linux-next: manual merge of the gpio tree with the mfd tree

Hi Linus, Today's linux-next merge of the gpio tree got a conflict in: drivers/gpio/gpio-tps65912.c between commits: 65b6555971d0 ("mfd: tps65912: Remove old driver in preparation for new driver") ca801a22f465 ("gpio: tps65912: Add GPIO driver for the TPS65912 PMIC") from the mfd tree

[PATCH 0/9] GIC updates for 4.6

Hi Thomas, Please find below the GIC updates for 4.6. This time around, the first round of ACPI support for GICv3, the Alpine MSI widget and a RealView support update (blast from the past!). Thanks, M. The following changes since commit fe2f95468e4bdf4a526be4f86efaefe48ca63b83:

[PATCH 0/9] GIC updates for 4.6

Hi Thomas, Please find below the GIC updates for 4.6. This time around, the first round of ACPI support for GICv3, the Alpine MSI widget and a RealView support update (blast from the past!). Thanks, M. The following changes since commit fe2f95468e4bdf4a526be4f86efaefe48ca63b83:

Re: [PATCH v3 2/9] clocksource: arm_arch_timer: Extend arch_timer_kvm_info to get the virtual IRQ

On Tue, Mar 08, 2016 at 11:29:26AM +, Julien Grall wrote: > Currently, the firmware table is parsed by the virtual timer code in > order to retrieve the virtual timer interrupt. However, this is already > done by the arch timer driver. > > To avoid code duplication, extend arch_timer_kvm_info

Re: [PATCH v3 2/9] clocksource: arm_arch_timer: Extend arch_timer_kvm_info to get the virtual IRQ

On Tue, Mar 08, 2016 at 11:29:26AM +, Julien Grall wrote: > Currently, the firmware table is parsed by the virtual timer code in > order to retrieve the virtual timer interrupt. However, this is already > done by the arch timer driver. > > To avoid code duplication, extend arch_timer_kvm_info

Re: [PATCH 7/8] drivers/pinctrl: make sunxi/pinctrl-sun9i-a80-r.c explicitly non-modular

On Tue, Mar 1, 2016 at 3:48 AM, Paul Gortmaker wrote: > The Kconfig currently controlling compilation of this code is: > > drivers/pinctrl/sunxi/Kconfig:config PINCTRL_SUN9I_A80_R > drivers/pinctrl/sunxi/Kconfig: def_bool MACH_SUN9I > > ...meaning that it currently

Re: [PATCH 7/8] drivers/pinctrl: make sunxi/pinctrl-sun9i-a80-r.c explicitly non-modular

On Tue, Mar 1, 2016 at 3:48 AM, Paul Gortmaker wrote: > The Kconfig currently controlling compilation of this code is: > > drivers/pinctrl/sunxi/Kconfig:config PINCTRL_SUN9I_A80_R > drivers/pinctrl/sunxi/Kconfig: def_bool MACH_SUN9I > > ...meaning that it currently is not being built as a

[PATCH] Revert "[media] au0828: use v4l2_mc_create_media_graph()"

This reverts commit 9822f4173f84cb7c592edb5e1478b7903f69d018. This commit breaks au0828_enable_handler() logic to find the tuner. Audio, Video, and Digital applications are broken and fail to start streaming with tuner busy error even when tuner is free. Signed-off-by: Shuah Khan

[PATCH] Revert "[media] au0828: use v4l2_mc_create_media_graph()"

This reverts commit 9822f4173f84cb7c592edb5e1478b7903f69d018. This commit breaks au0828_enable_handler() logic to find the tuner. Audio, Video, and Digital applications are broken and fail to start streaming with tuner busy error even when tuner is free. Signed-off-by: Shuah Khan ---

Re: [PATCH 5/8] drivers/pinctrl: make stm32/pinctrl-stm32f429.c explicitly non-modular

On Tue, Mar 1, 2016 at 3:48 AM, Paul Gortmaker wrote: > The Kconfig currently controlling compilation of this code is: > > drivers/pinctrl/stm32/Kconfig:config PINCTRL_STM32F429 > drivers/pinctrl/stm32/Kconfig: bool "STMicroelectronics STM32F429 pin > control" if

Re: [PATCH 5/8] drivers/pinctrl: make stm32/pinctrl-stm32f429.c explicitly non-modular

On Tue, Mar 1, 2016 at 3:48 AM, Paul Gortmaker wrote: > The Kconfig currently controlling compilation of this code is: > > drivers/pinctrl/stm32/Kconfig:config PINCTRL_STM32F429 > drivers/pinctrl/stm32/Kconfig: bool "STMicroelectronics STM32F429 pin > control" if COMPILE_TEST &&

Re: [PATCH 4/8] drivers/pinctrl: make sh-pfc/core.c explicitly non-modular

On Tue, Mar 1, 2016 at 3:48 AM, Paul Gortmaker wrote: > The Kconfig / Makefile currently controlling compilation of this code is: > > drivers/pinctrl/sh-pfc/Makefile:obj-$(CONFIG_PINCTRL_SH_PFC)+= sh-pfc.o > drivers/pinctrl/sh-pfc/Makefile:sh-pfc-objs

Re: [PATCH 4/8] drivers/pinctrl: make sh-pfc/core.c explicitly non-modular

On Tue, Mar 1, 2016 at 3:48 AM, Paul Gortmaker wrote: > The Kconfig / Makefile currently controlling compilation of this code is: > > drivers/pinctrl/sh-pfc/Makefile:obj-$(CONFIG_PINCTRL_SH_PFC)+= sh-pfc.o > drivers/pinctrl/sh-pfc/Makefile:sh-pfc-objs = core.o >

[PATCH v2 2/6] leds: lp8788: Use devm_led_classdev_register

Switch to resource-managed function devm_led_classdev_register instead of led_classdev_register and remove unneeded led_classdev_unregister. Also, remove platform_set_drvdata in probe function and the remove function, lp8788_led_remove as it is now has nothing to do. The Coccinelle semantic

[PATCH v2 3/6] leds: wm831x-status: Use devm_led_classdev_register

Switch to resource-managed function devm_led_classdev_register instead of led_classdev_register and remove unneeded led_classdev_unregister. Also, remove platform_set_drvdata from probe function and the remove function, wm831x_status_remove as it is now has nothing to do. The Coccinelle semantic

[PATCH v2 5/6] leds: da903x: Use devm_led_classdev_register

Switch to resource-managed function devm_led_classdev_register instead of led_classdev_register and remove unneeded led_classdev_unregister. Also, remove platform_set_drvdata in probe function and the remove function, da903x_led_remove as it is now has nothing to do. The Coccinelle semantic

[PATCH v2 2/6] leds: lp8788: Use devm_led_classdev_register

Switch to resource-managed function devm_led_classdev_register instead of led_classdev_register and remove unneeded led_classdev_unregister. Also, remove platform_set_drvdata in probe function and the remove function, lp8788_led_remove as it is now has nothing to do. The Coccinelle semantic

[PATCH v2 3/6] leds: wm831x-status: Use devm_led_classdev_register

Switch to resource-managed function devm_led_classdev_register instead of led_classdev_register and remove unneeded led_classdev_unregister. Also, remove platform_set_drvdata from probe function and the remove function, wm831x_status_remove as it is now has nothing to do. The Coccinelle semantic

[PATCH v2 5/6] leds: da903x: Use devm_led_classdev_register

Switch to resource-managed function devm_led_classdev_register instead of led_classdev_register and remove unneeded led_classdev_unregister. Also, remove platform_set_drvdata in probe function and the remove function, da903x_led_remove as it is now has nothing to do. The Coccinelle semantic

[PATCH v2 6/6] leds: max8997: Use devm_led_classdev_register

Switch to resource-managed function devm_led_classdev_register instead of led_classdev_register and remove unneeded led_classdev_unregister. Also, remove platform_set_drvdata in probe function and the remove function, max8997_led_remove as it is now has nothing to do. The Coccinelle semantic

Re: [PATCH v3 1/9] clocksource: arm_arch_timer: Gather KVM specific information in a structure

On Tue, Mar 08, 2016 at 11:29:25AM +, Julien Grall wrote: > Introduce a structure which are filled up by the arch timer driver and > used by the virtual timer in KVM. > > The first member of this structure will be the timecounter. More members > will be added later. > > A stub for the new

[PATCH v2 4/6] leds: s3c24xx: Use devm_led_classdev_register

Switch to resource-managed function devm_led_classdev_register instead of led_classdev_register and remove unneeded led_classdev_unregister. Also, remove unnecessary function pdev_to_gpio, platform_set_drvdata in the probe function and the remove function, s3c24xx_led_remove as it is now has

[PATCH v2 1/6] leds: 88pm860x: Use devm_led_classdev_register

Switch to resource-managed function devm_led_classdev_register instead of led_classdev_register and remove unneeded led_classdev_unregister. Also, remove platform_set_drvdata in probe function and the remove function, pm860x_led_remove as it is now has nothing to do. The Coccinelle semantic

[PATCH v2 6/6] leds: max8997: Use devm_led_classdev_register

Switch to resource-managed function devm_led_classdev_register instead of led_classdev_register and remove unneeded led_classdev_unregister. Also, remove platform_set_drvdata in probe function and the remove function, max8997_led_remove as it is now has nothing to do. The Coccinelle semantic

Re: [PATCH v3 1/9] clocksource: arm_arch_timer: Gather KVM specific information in a structure

On Tue, Mar 08, 2016 at 11:29:25AM +, Julien Grall wrote: > Introduce a structure which are filled up by the arch timer driver and > used by the virtual timer in KVM. > > The first member of this structure will be the timecounter. More members > will be added later. > > A stub for the new

[PATCH v2 4/6] leds: s3c24xx: Use devm_led_classdev_register

Switch to resource-managed function devm_led_classdev_register instead of led_classdev_register and remove unneeded led_classdev_unregister. Also, remove unnecessary function pdev_to_gpio, platform_set_drvdata in the probe function and the remove function, s3c24xx_led_remove as it is now has

[PATCH v2 1/6] leds: 88pm860x: Use devm_led_classdev_register

Switch to resource-managed function devm_led_classdev_register instead of led_classdev_register and remove unneeded led_classdev_unregister. Also, remove platform_set_drvdata in probe function and the remove function, pm860x_led_remove as it is now has nothing to do. The Coccinelle semantic

[PATCH v2 0/6] leds: Use devm_led_classdev_register

Switch to resource-managed function devm_led_classdev_register instead of led_classdev_register and remove unneeded led_classdev_unregister. The Coccinelle semantic patch used to make this change is as follows: // @platform@ identifier p, probefn, removefn; @@ struct platform_driver p = {

[PATCH v2 0/6] leds: Use devm_led_classdev_register

Switch to resource-managed function devm_led_classdev_register instead of led_classdev_register and remove unneeded led_classdev_unregister. The Coccinelle semantic patch used to make this change is as follows: // @platform@ identifier p, probefn, removefn; @@ struct platform_driver p = {

Re: [PATCH 3/8] drivers/pinctrl: make meson/pinctrl-meson.c explicitly non-modular

On Tue, Mar 1, 2016 at 3:48 AM, Paul Gortmaker wrote: > The Kconfig currently controlling compilation of this code is: > > drivers/pinctrl/Kconfig:config PINCTRL_MESON > drivers/pinctrl/Kconfig:bool > > ...meaning that it currently is not being built as a

Re: [PATCH 3/8] drivers/pinctrl: make meson/pinctrl-meson.c explicitly non-modular

On Tue, Mar 1, 2016 at 3:48 AM, Paul Gortmaker wrote: > The Kconfig currently controlling compilation of this code is: > > drivers/pinctrl/Kconfig:config PINCTRL_MESON > drivers/pinctrl/Kconfig:bool > > ...meaning that it currently is not being built as a module by anyone. > > Lets

Re: [PATCH 2/8] drivers/pinctrl: make mediatek/pinctrl-mt6397 driver explicitly non-modular

On Tue, Mar 1, 2016 at 3:48 AM, Paul Gortmaker wrote: > The Kconfig for this driver is currently: > > config PINCTRL_MT6397 > bool "Mediatek MT6397 pin control" if COMPILE_TEST && !MFD_MT6397 > > ...meaning that it is currently not being built as a module by

Re: [PATCH 2/8] drivers/pinctrl: make mediatek/pinctrl-mt6397 driver explicitly non-modular

On Tue, Mar 1, 2016 at 3:48 AM, Paul Gortmaker wrote: > The Kconfig for this driver is currently: > > config PINCTRL_MT6397 > bool "Mediatek MT6397 pin control" if COMPILE_TEST && !MFD_MT6397 > > ...meaning that it is currently not being built as a module by anyone. > Lets remove the

Re: [PATCH 01/11] rxrpc: Add a common object cache

From: David Howells Date: Tue, 08 Mar 2016 21:11:09 + > I can put in a limit per peer, where a 'peer' is either a particular remote > UDP port or particulat remote host. TCP has this by virtue of having a > limited number of ports available per IP address. But if I

Re: [PATCH 01/11] rxrpc: Add a common object cache

From: David Howells Date: Tue, 08 Mar 2016 21:11:09 + > I can put in a limit per peer, where a 'peer' is either a particular remote > UDP port or particulat remote host. TCP has this by virtue of having a > limited number of ports available per IP address. But if I have 10 IP > addresses

Re: [PATCH 1/8] drivers/pinctrl: sunxi/pinctrl-sunxi.c does not need module.h

On Tue, Mar 1, 2016 at 3:48 AM, Paul Gortmaker wrote: > This file is not modular, nor is it using modular functions. The > only thing close is the global THIS_MODULE which comes from export.h > so lets replace it appropriately and cut back on the amount of > header

Re: [PATCH 1/8] drivers/pinctrl: sunxi/pinctrl-sunxi.c does not need module.h

On Tue, Mar 1, 2016 at 3:48 AM, Paul Gortmaker wrote: > This file is not modular, nor is it using modular functions. The > only thing close is the global THIS_MODULE which comes from export.h > so lets replace it appropriately and cut back on the amount of > header stuff we draw in by several

Re: [PATCH v3 01/13] pinctrl: sunxi: Add A83T R_PIO controller support

On Sat, Mar 5, 2016 at 10:42 PM, Vishnu Patekar wrote: > The A83T has R_PIO pin controller, it's same as A23, execpt A83T > interrupt bit is 6th and A83T has one extra pin PL12. > > Signed-off-by: Vishnu Patekar > Acked-by: Chen-Yu Tsai

Re: [PATCH v3 01/13] pinctrl: sunxi: Add A83T R_PIO controller support

On Sat, Mar 5, 2016 at 10:42 PM, Vishnu Patekar wrote: > The A83T has R_PIO pin controller, it's same as A23, execpt A83T > interrupt bit is 6th and A83T has one extra pin PL12. > > Signed-off-by: Vishnu Patekar > Acked-by: Chen-Yu Tsai > Acked-by: Rob Herring As partly noted by others: >

[PATCH v5 4/7] bindings: move cpm_qe binding from powerpc/fsl to soc/fsl

cpm_qe is supported on both powerpc and arm. and the QE code has been moved from arch/powerpc into drivers/soc/fsl, so move cpm_qe binding from powerpc/fsl to soc/fsl Signed-off-by: Zhao Qiang Acked-by: Rob Herring --- Changes for v3 - NA Changes for

[PATCH v5 4/7] bindings: move cpm_qe binding from powerpc/fsl to soc/fsl

cpm_qe is supported on both powerpc and arm. and the QE code has been moved from arch/powerpc into drivers/soc/fsl, so move cpm_qe binding from powerpc/fsl to soc/fsl Signed-off-by: Zhao Qiang Acked-by: Rob Herring --- Changes for v3 - NA Changes for v4 - NA Changes for v5

[PATCH] watchdog: Ensure that wdd is not dereferenced if NULL

Smatch rightfully complains that wdd is dereferenced in the watchdog release function after being checked for NULL. Also make sure that it is not accessed outside mutex protection to avoid use-after-free problems. Fixes: e6c71e84e4c0 ("watchdog: Introduce WDOG_HW_RUNNING flag") Reported-by: Dan

[PATCH] watchdog: Ensure that wdd is not dereferenced if NULL

Smatch rightfully complains that wdd is dereferenced in the watchdog release function after being checked for NULL. Also make sure that it is not accessed outside mutex protection to avoid use-after-free problems. Fixes: e6c71e84e4c0 ("watchdog: Introduce WDOG_HW_RUNNING flag") Reported-by: Dan

[PATCH v3 7/7] clk: rockchip: add clock controller for the RK3399

Add the clock tree definition for the new RK3399 SoC. Signed-off-by: Xing Zheng --- Changes in v3: - rename pclkin_cif to pclkin_cifmux, add diagram and comment for pclkin_cifmux - add the clk_test node - modify the cif_testout path - include two new patches that

[PATCH v3 7/7] clk: rockchip: add clock controller for the RK3399

Add the clock tree definition for the new RK3399 SoC. Signed-off-by: Xing Zheng --- Changes in v3: - rename pclkin_cif to pclkin_cifmux, add diagram and comment for pclkin_cifmux - add the clk_test node - modify the cif_testout path - include two new patches that dt-bindings and header file

Re: [PATCH v2] gpio: add driver for MEN 16Z127 GPIO controller

On Tue, Mar 1, 2016 at 1:44 AM, Andreas Werner wrote: > The 16Z127 is a 32bit GPIO controller on a MCB FPGA. > Every single line can be configured as input and output. > > Push pull and open drain are supported as well as setting > a debounce value for the input lines. > >

Re: [PATCH v2] gpio: add driver for MEN 16Z127 GPIO controller

On Tue, Mar 1, 2016 at 1:44 AM, Andreas Werner wrote: > The 16Z127 is a 32bit GPIO controller on a MCB FPGA. > Every single line can be configured as input and output. > > Push pull and open drain are supported as well as setting > a debounce value for the input lines. > > Signed-off-by: Andreas

[PATCH v3 5/7] clk: rockchip: add new pll-type for rk3399 and similar socs

The rk3399's pll and clock are similar with rk3036's, it different with base on the rk3066(rk3188, rk3288, rk3368 use it), there are different adjust foctors and control registers, so these should be independent and separate from the series of rk3066s. Signed-off-by: Xing Zheng

[PATCH v3 6/7] clk: rockchip: add a COMPOSITE_FRACMUX_NOGATE type

Because there are some frac clock mux nodes don't need gate node on the RK3399. Signed-off-by: Xing Zheng --- Changes in v3: None Changes in v2: None drivers/clk/rockchip/clk.h | 16 1 file changed, 16 insertions(+) diff --git

[PATCH v3 5/7] clk: rockchip: add new pll-type for rk3399 and similar socs

The rk3399's pll and clock are similar with rk3036's, it different with base on the rk3066(rk3188, rk3288, rk3368 use it), there are different adjust foctors and control registers, so these should be independent and separate from the series of rk3066s. Signed-off-by: Xing Zheng --- Changes in

[PATCH v3 6/7] clk: rockchip: add a COMPOSITE_FRACMUX_NOGATE type

Because there are some frac clock mux nodes don't need gate node on the RK3399. Signed-off-by: Xing Zheng --- Changes in v3: None Changes in v2: None drivers/clk/rockchip/clk.h | 16 1 file changed, 16 insertions(+) diff --git a/drivers/clk/rockchip/clk.h

[PATCH 2/2] mmc: dw_mmc: avoid using dmaengine_terminate_all

dmaengine_terminate_all is deprecated and should be replaced by more explicit synchronous and asynchronous terminate functions. This change is based on the commit b36f09c3c441 ("dmaengine: Add transfer termination synchronization support"). Currently dw_mci_stop_dma may be called under the

[PATCH 2/2] mmc: dw_mmc: avoid using dmaengine_terminate_all

dmaengine_terminate_all is deprecated and should be replaced by more explicit synchronous and asynchronous terminate functions. This change is based on the commit b36f09c3c441 ("dmaengine: Add transfer termination synchronization support"). Currently dw_mci_stop_dma may be called under the

<    1   2   3   4   5   6   7   8   9   10   >