stack gap fix for 4.1

Hi. I'm looking for stack gap fix backport for 4.1 (it's not in 4.1 stable queue git unfortunately). I wonder if any distro still maintains 4.1 and could already make backport? Thanks, -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

stack gap fix for 4.1

Hi. I'm looking for stack gap fix backport for 4.1 (it's not in 4.1 stable queue git unfortunately). I wonder if any distro still maintains 4.1 and could already make backport? Thanks, -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

Re: linux-next: build failure after merge of most trees

On Thu, 22 Jun 2017 15:24:41 +1000 Stephen Rothwell wrote: > Hi Dave, > > After merging almost all the trees, today's linux-next build (sparc64 > defconfig) failed like this: > > arch/sparc/lib/hweight.o: In function `__arch_hweight8': > (.text+0x0): relocation truncated

Re: linux-next: build failure after merge of most trees

On Thu, 22 Jun 2017 15:24:41 +1000 Stephen Rothwell wrote: > Hi Dave, > > After merging almost all the trees, today's linux-next build (sparc64 > defconfig) failed like this: > > arch/sparc/lib/hweight.o: In function `__arch_hweight8': > (.text+0x0): relocation truncated to fit:

[PATCH 3/3] iio: adc: mt7622: Add compatible node for mt7622.

This commit adds mt7622 compatible node. Signed-off-by: Zhiyong Tao --- drivers/iio/adc/mt6577_auxadc.c |1 + 1 file changed, 1 insertion(+) diff --git a/drivers/iio/adc/mt6577_auxadc.c b/drivers/iio/adc/mt6577_auxadc.c index 2dd7c74..4a2cd9e 100644 ---

[PATCH 0/3] ADC: Mediatek auxadc driver for mt7622

These patches are first version of Mediatek auxadc driver for mt7622. These patches include three patches. The First patch adds mt7622 compatible node in binding document. The second patch adds support for suspend/resume. The last patch adds mt7622 compatible node in auxadc driver. Zhiyong Tao

[PATCH 3/3] iio: adc: mt7622: Add compatible node for mt7622.

This commit adds mt7622 compatible node. Signed-off-by: Zhiyong Tao --- drivers/iio/adc/mt6577_auxadc.c |1 + 1 file changed, 1 insertion(+) diff --git a/drivers/iio/adc/mt6577_auxadc.c b/drivers/iio/adc/mt6577_auxadc.c index 2dd7c74..4a2cd9e 100644 --- a/drivers/iio/adc/mt6577_auxadc.c

[PATCH 0/3] ADC: Mediatek auxadc driver for mt7622

These patches are first version of Mediatek auxadc driver for mt7622. These patches include three patches. The First patch adds mt7622 compatible node in binding document. The second patch adds support for suspend/resume. The last patch adds mt7622 compatible node in auxadc driver. Zhiyong Tao

[PATCH 1/3] dt-bindings: adc: mt7622: add binding document

The commit adds mt7622 compatible node in binding document. Signed-off-by: Zhiyong Tao --- .../devicetree/bindings/iio/adc/mt6577_auxadc.txt |1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/iio/adc/mt6577_auxadc.txt

[PATCH 2/3] iio: adc: mt7622: add support for suspend/resume.

This patch supports auxadc suspend/resume flow. Disable auxadc clk and power in suspend function. Enable axuadc clk and power in resume function. Signed-off-by: Zhiyong Tao --- drivers/iio/adc/mt6577_auxadc.c | 37 + 1 file

[PATCH 1/3] dt-bindings: adc: mt7622: add binding document

The commit adds mt7622 compatible node in binding document. Signed-off-by: Zhiyong Tao --- .../devicetree/bindings/iio/adc/mt6577_auxadc.txt |1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/iio/adc/mt6577_auxadc.txt

[PATCH 2/3] iio: adc: mt7622: add support for suspend/resume.

This patch supports auxadc suspend/resume flow. Disable auxadc clk and power in suspend function. Enable axuadc clk and power in resume function. Signed-off-by: Zhiyong Tao --- drivers/iio/adc/mt6577_auxadc.c | 37 + 1 file changed, 37 insertions(+) diff

Re: [PATCH v2 1/3] input: sun4i-a10-lradc-keys: Add support for A83T

2017-06-22 4:35 GMT+08:00 Maxime Ripard : > On Tue, Jun 20, 2017 at 09:44:43PM +0800, Ziping Chen wrote: >> From: Ziping Chen >> >> Allwinner A83T SoC has a low res adc like the one >> in Allwinner A10 SoC, however, the A10 SoC's vref >>

Re: [PATCH v2 1/3] input: sun4i-a10-lradc-keys: Add support for A83T

2017-06-22 4:35 GMT+08:00 Maxime Ripard : > On Tue, Jun 20, 2017 at 09:44:43PM +0800, Ziping Chen wrote: >> From: Ziping Chen >> >> Allwinner A83T SoC has a low res adc like the one >> in Allwinner A10 SoC, however, the A10 SoC's vref >> of lradc internally is divided by 2/3 and the A83T >> SoC's

Re: linux-next: Tree for Jun 7 (arch/x86/mm/tlb.c: events)

Hi Randy, On Wed, 21 Jun 2017 20:58:38 -0700 Randy Dunlap <rdun...@infradead.org> wrote: > > I cannot repro it on linux-next of 20170621. Thanks. -- Cheers, Stephen Rothwell

Re: linux-next: Tree for Jun 7 (arch/x86/mm/tlb.c: events)

Hi Randy, On Wed, 21 Jun 2017 20:58:38 -0700 Randy Dunlap wrote: > > I cannot repro it on linux-next of 20170621. Thanks. -- Cheers, Stephen Rothwell

linux-next: build failure after merge of most trees

Hi Dave, After merging almost all the trees, today's linux-next build (sparc64 defconfig) failed like this: arch/sparc/lib/hweight.o: In function `__arch_hweight8': (.text+0x0): relocation truncated to fit: R_SPARC_WDISP19 against symbol `__sw_hweight8' defined in .text section in lib/hweight.o

linux-next: build failure after merge of most trees

Hi Dave, After merging almost all the trees, today's linux-next build (sparc64 defconfig) failed like this: arch/sparc/lib/hweight.o: In function `__arch_hweight8': (.text+0x0): relocation truncated to fit: R_SPARC_WDISP19 against symbol `__sw_hweight8' defined in .text section in lib/hweight.o

Re: [PATCH v3 00/11] PCID and improved laziness

On Wed, Jun 21, 2017 at 11:23 AM, Linus Torvalds wrote: > On Tue, Jun 20, 2017 at 10:22 PM, Andy Lutomirski wrote: >> There are three performance benefits here: > > Side note: can you post the actual performance numbers, even if only > from some

Re: [PATCH v3 00/11] PCID and improved laziness

On Wed, Jun 21, 2017 at 11:23 AM, Linus Torvalds wrote: > On Tue, Jun 20, 2017 at 10:22 PM, Andy Lutomirski wrote: >> There are three performance benefits here: > > Side note: can you post the actual performance numbers, even if only > from some silly test program on just one platform? Things

Re: [PATCH][net-next] qtnfmac: fix uninitialized return code in ret

On Wed, Jun 21, 2017 at 02:25:30PM +0100, Colin King wrote: > From: Colin Ian King > > The return value ret is unitialized and garbage is being returned > for the three different error conditions when setting up the PCIe > BARs. Fix this by initializing ret to -ENOMEM

Re: [PATCH][net-next] qtnfmac: fix uninitialized return code in ret

On Wed, Jun 21, 2017 at 02:25:30PM +0100, Colin King wrote: > From: Colin Ian King > > The return value ret is unitialized and garbage is being returned > for the three different error conditions when setting up the PCIe > BARs. Fix this by initializing ret to -ENOMEM to indicate that > the

[PATCH v5 0/2] drm: atmel-hlcdc: clut support

Hi! This series adds support for an 8-bit clut mode in the atmel-hlcdc driver. Changes since v4: - Added .clut_offset for overlay2 at 0xe00 for sama5d4 (unconfirmed if 0xe00 is the correct offset, but I'll eat my hat if it's not there). The sama5d4 overlay2 is indeed there, it is just AWOL

[PATCH v5 2/2] drm: atmel-hlcdc: add support for 8-bit color lookup table mode

All layers of all supported chips support this, the only variable is the base address of the lookup table in the register map. Acked-by: Daniel Vetter Signed-off-by: Peter Rosin --- drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c | 4

[PATCH v5 1/2] drm: atmel-hlcdc: add missing .set_property helper to the crtc

The default implementation should be used. Signed-off-by: Peter Rosin --- drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c b/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c index

[PATCH v5 0/2] drm: atmel-hlcdc: clut support

Hi! This series adds support for an 8-bit clut mode in the atmel-hlcdc driver. Changes since v4: - Added .clut_offset for overlay2 at 0xe00 for sama5d4 (unconfirmed if 0xe00 is the correct offset, but I'll eat my hat if it's not there). The sama5d4 overlay2 is indeed there, it is just AWOL

[PATCH v5 2/2] drm: atmel-hlcdc: add support for 8-bit color lookup table mode

All layers of all supported chips support this, the only variable is the base address of the lookup table in the register map. Acked-by: Daniel Vetter Signed-off-by: Peter Rosin --- drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c | 4 drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c| 14

[PATCH v5 1/2] drm: atmel-hlcdc: add missing .set_property helper to the crtc

The default implementation should be used. Signed-off-by: Peter Rosin --- drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c b/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c index 5348985..cc00ce3

Re: [PATCH] iio: adc: Add support for DLN2 ADC

> This patch adds support for Diolan DLN2 ADC via IIO's ADC interface. > ADC is the fourth and final component of the DLN2 for the kernel. comments below > Signed-off-by: Jack Andersen > --- > drivers/iio/adc/Kconfig| 9 + > drivers/iio/adc/Makefile | 1 + >

Re: [PATCH] iio: adc: Add support for DLN2 ADC

> This patch adds support for Diolan DLN2 ADC via IIO's ADC interface. > ADC is the fourth and final component of the DLN2 for the kernel. comments below > Signed-off-by: Jack Andersen > --- > drivers/iio/adc/Kconfig| 9 + > drivers/iio/adc/Makefile | 1 + >

Re: [PATCH] radio: wl1273: add check on core->write() return value

Hi Gustavi, On Wed, Jun 21, 2017 at 11:01:22PM -0500, Gustavo A. R. Silva wrote: > Check return value from call to core->write(), so in case of > error print error message, jump to goto label fail and eventually > return. > > Addresses-Coverity-ID: 1226943 > Signed-off-by: Gustavo A. R. Silva

Re: [PATCH] radio: wl1273: add check on core->write() return value

Hi Gustavi, On Wed, Jun 21, 2017 at 11:01:22PM -0500, Gustavo A. R. Silva wrote: > Check return value from call to core->write(), so in case of > error print error message, jump to goto label fail and eventually > return. > > Addresses-Coverity-ID: 1226943 > Signed-off-by: Gustavo A. R. Silva >

[PATCH v6 0/2] IV Generation algorithms for dm-crypt

=== dm-crypt optimization for larger block sizes === Currently, the iv generation algorithms are implemented in dm-crypt.c. The goal is to move

[PATCH v6 0/2] IV Generation algorithms for dm-crypt

=== dm-crypt optimization for larger block sizes === Currently, the iv generation algorithms are implemented in dm-crypt.c. The goal is to move

[PATCH v6 1/2] crypto: Add IV generation algorithms

Just for reference. Not for merging. Currently, the iv generation algorithms are implemented in dm-crypt.c. The goal is to move these algorithms from the dm layer to the kernel crypto layer by implementing them as template ciphers so they can be implemented in hardware for performance. As part of

[PATCH v6 1/2] crypto: Add IV generation algorithms

Just for reference. Not for merging. Currently, the iv generation algorithms are implemented in dm-crypt.c. The goal is to move these algorithms from the dm layer to the kernel crypto layer by implementing them as template ciphers so they can be implemented in hardware for performance. As part of

[PATCH v6 2/2] crypto: Multikey template for essiv

Just for reference and to get the performance numbers. Not for merging. Depends on the following patches by Gilad: MAINTAINERS: add Gilad BY as maintainer for ccree staging: ccree: add devicetree bindings staging: ccree: add TODO list staging: add ccree crypto driver A multi key template

[PATCH v6 2/2] crypto: Multikey template for essiv

Just for reference and to get the performance numbers. Not for merging. Depends on the following patches by Gilad: MAINTAINERS: add Gilad BY as maintainer for ccree staging: ccree: add devicetree bindings staging: ccree: add TODO list staging: add ccree crypto driver A multi key template

Re: [PATCH 32/32] ext4: add nombcache mount option

On Wed, Jun 21, 2017 at 04:46:48PM -0700, Tahsin Erdogan wrote: > Remount option handling is a bit strange. If an option is not > specified, it is not automatically cleared in sbi->s_mount_opt. So, > once nombcache option is set in the original mount, it is not possible > to clear it. I don't know

Re: [PATCH 32/32] ext4: add nombcache mount option

On Wed, Jun 21, 2017 at 04:46:48PM -0700, Tahsin Erdogan wrote: > Remount option handling is a bit strange. If an option is not > specified, it is not automatically cleared in sbi->s_mount_opt. So, > once nombcache option is set in the original mount, it is not possible > to clear it. I don't know

Re: [PATCH V4 2/2] powerpc/powernv : Add support for OPAL-OCC command/response interface

Hi Cyril, On 06/22/2017 06:28 AM, Cyril Bur wrote: > On Wed, 2017-06-21 at 13:36 +0530, Shilpasri G Bhat wrote: >> In P9, OCC (On-Chip-Controller) supports shared memory based >> commad-response interface. Within the shared memory there is an OPAL >> command buffer and OCC response buffer that

Re: [PATCH V4 2/2] powerpc/powernv : Add support for OPAL-OCC command/response interface

Hi Cyril, On 06/22/2017 06:28 AM, Cyril Bur wrote: > On Wed, 2017-06-21 at 13:36 +0530, Shilpasri G Bhat wrote: >> In P9, OCC (On-Chip-Controller) supports shared memory based >> commad-response interface. Within the shared memory there is an OPAL >> command buffer and OCC response buffer that

Re: [lkp-robot] [mm] 1be7107fbe: kernel_BUG_at_mm/mmap.c

On Wed, 21 Jun 2017, Oleg Nesterov wrote: > On 06/21, Linus Torvalds wrote: > > > > Hugh, Michal - I also merged Helge's drop-up cleanup, is there > > anything I've missed? I think Oleg had something, but I can't recall > > right now, and I might just have missed it. > > Well, I meant, perhaps we

Re: [lkp-robot] [mm] 1be7107fbe: kernel_BUG_at_mm/mmap.c

On Wed, 21 Jun 2017, Oleg Nesterov wrote: > On 06/21, Linus Torvalds wrote: > > > > Hugh, Michal - I also merged Helge's drop-up cleanup, is there > > anything I've missed? I think Oleg had something, but I can't recall > > right now, and I might just have missed it. > > Well, I meant, perhaps we

[PATCH] dvb-usb-v2: lmedm04: remove unnecessary variable in lme2510_stream_restart()

Remove unnecessary variable _ret_ and refactor the code. Addresses-Coverity-ID: 1226934 Signed-off-by: Gustavo A. R. Silva --- drivers/media/usb/dvb-usb-v2/lmedm04.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git

[PATCH] dvb-usb-v2: lmedm04: remove unnecessary variable in lme2510_stream_restart()

Remove unnecessary variable _ret_ and refactor the code. Addresses-Coverity-ID: 1226934 Signed-off-by: Gustavo A. R. Silva --- drivers/media/usb/dvb-usb-v2/lmedm04.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/drivers/media/usb/dvb-usb-v2/lmedm04.c

[PATCH] docs/memory-hotplug: adjust the explanation of valid_zones sysfs

After commit "mm, memory_hotplug: do not associate hotadded memory to zones until online", the meaning of valid_zones is changed. 1. When the memory block is online, it returns the onlined zone name 2. We won't have "Movable Normal" case, because default_zone couldn't be MOVABLE This patch

[PATCH] docs/memory-hotplug: adjust the explanation of valid_zones sysfs

After commit "mm, memory_hotplug: do not associate hotadded memory to zones until online", the meaning of valid_zones is changed. 1. When the memory block is online, it returns the onlined zone name 2. We won't have "Movable Normal" case, because default_zone couldn't be MOVABLE This patch

[PATCH 5/6] ARM: sun8i: a83t: Add device node for AXP813 PMIC

The AXP813/AXP818 PMICs used with the A83T/H8 SoCs are actually 2 dies in one package sharing the serial bus (I2C/RSB) pins. One die is the actual PMIC. The other is an AC100 codec / RTC combo chip. This patch adds a device node for the PMIC die. Signed-off-by: Chen-Yu Tsai ---

[PATCH 5/6] ARM: sun8i: a83t: Add device node for AXP813 PMIC

The AXP813/AXP818 PMICs used with the A83T/H8 SoCs are actually 2 dies in one package sharing the serial bus (I2C/RSB) pins. One die is the actual PMIC. The other is an AC100 codec / RTC combo chip. This patch adds a device node for the PMIC die. Signed-off-by: Chen-Yu Tsai ---

[PATCH 0/6] mfd: axp20x: Add basic support for AXP813

Hi everyone, This series adds basic device tree bindings and driver support for the AXP813/818 PMICs. The two models are identical when comparing their datasheets. These PMICs are actually two dies in one package: one being the actual PMIC, the other being an AC100 codec/RTC combo chip. The

[PATCH 0/6] mfd: axp20x: Add basic support for AXP813

Hi everyone, This series adds basic device tree bindings and driver support for the AXP813/818 PMICs. The two models are identical when comparing their datasheets. These PMICs are actually two dies in one package: one being the actual PMIC, the other being an AC100 codec/RTC combo chip. The

[PATCH 4/6] ARM: sun8i: a83t: Add device node and pinmux setting for RSB controller

The A83T has an RSB controller for talking to the PMIC and audio codec. Add a device node for it. Since there is only one usable pinmux setting, for it, add that as well. Signed-off-by: Chen-Yu Tsai --- arch/arm/boot/dts/sun8i-a83t.dtsi | 22 ++ 1 file

[PATCH 4/6] ARM: sun8i: a83t: Add device node and pinmux setting for RSB controller

The A83T has an RSB controller for talking to the PMIC and audio codec. Add a device node for it. Since there is only one usable pinmux setting, for it, add that as well. Signed-off-by: Chen-Yu Tsai --- arch/arm/boot/dts/sun8i-a83t.dtsi | 22 ++ 1 file changed, 22

[PATCH 3/6] mfd: axp20x: Add support for AXP813 PMIC

The X-Powers AXP813 PMIC is normally used with Allwinner's A83T SoC. It has the same range of functions as other X-Powers PMICs, such as DC-DC buck converter and linear regulator outputs, AC-IN and VBUS power supplies, power button trigger, GPIOs, ADCs, and a battery charger. Note that the IRQ

[PATCH 2/6] dt-bindings: mfd: axp20x: Introduce bindings for AXP813

The X-Powers AXP813 is a PMIC designed to be paired with Allwinner's A83T SoC. There is also an AXP818, which is paired with the H8 SoC. The two models seem to be identical, apart from the external markings. This patch introduces the basic mfd and regulator bindings for the AXP813.

[PATCH 2/6] dt-bindings: mfd: axp20x: Introduce bindings for AXP813

The X-Powers AXP813 is a PMIC designed to be paired with Allwinner's A83T SoC. There is also an AXP818, which is paired with the H8 SoC. The two models seem to be identical, apart from the external markings. This patch introduces the basic mfd and regulator bindings for the AXP813.

[PATCH 3/6] mfd: axp20x: Add support for AXP813 PMIC

The X-Powers AXP813 PMIC is normally used with Allwinner's A83T SoC. It has the same range of functions as other X-Powers PMICs, such as DC-DC buck converter and linear regulator outputs, AC-IN and VBUS power supplies, power button trigger, GPIOs, ADCs, and a battery charger. Note that the IRQ

[PATCH 6/6] ARM: sun8i: a83t: Enable AC100 codec / RTC combo chip in AXP813 PMIC

The AXP813/AXP818 PMICs used with the A83T/H8 SoCs are actually 2 dies in one package sharing the serial bus (I2C/RSB) pins. One die is the actual PMIC. The other is an AC100 codec / RTC combo chip. This patch enables the RSB controller and adds the device nodes for the AC100 chip under it.

[PATCH 6/6] ARM: sun8i: a83t: Enable AC100 codec / RTC combo chip in AXP813 PMIC

The AXP813/AXP818 PMICs used with the A83T/H8 SoCs are actually 2 dies in one package sharing the serial bus (I2C/RSB) pins. One die is the actual PMIC. The other is an AC100 codec / RTC combo chip. This patch enables the RSB controller and adds the device nodes for the AC100 chip under it.

[PATCH 1/6] dt-bindings: mfd: axp20x: Add AXP806 to supported list of chips

The binding already lists compatibles and regulators for the AXP806, but it is missing from the list of supported chips at the beginning. Add it. Fixes: 204ae2963e10 ("mfd: axp20x: Add bindings for AXP806 PMIC") Signed-off-by: Chen-Yu Tsai ---

[PATCH 1/6] dt-bindings: mfd: axp20x: Add AXP806 to supported list of chips

The binding already lists compatibles and regulators for the AXP806, but it is missing from the list of supported chips at the beginning. Add it. Fixes: 204ae2963e10 ("mfd: axp20x: Add bindings for AXP806 PMIC") Signed-off-by: Chen-Yu Tsai --- Documentation/devicetree/bindings/mfd/axp20x.txt |

Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem

On Wed, Jun 21, 2017 at 5:02 PM, Dave Chinner wrote: > > You seem to be calling the "fdatasync on every page fault" the It's the opposite of fdatasync(). It needs to sync whatever metadata is needed to find the data. The data doesn't need to be synced. > "lightweight"

Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem

On Wed, Jun 21, 2017 at 5:02 PM, Dave Chinner wrote: > > You seem to be calling the "fdatasync on every page fault" the It's the opposite of fdatasync(). It needs to sync whatever metadata is needed to find the data. The data doesn't need to be synced. > "lightweight" option. That's the

Re: [PATCH 2/6] drivers base/arch_topology: frequency-invariant load-tracking support

On 21-06-17, 17:57, Morten Rasmussen wrote: > It is true that this patch relies on the notifiers, but I don't see how > that prevents us from adding a non-notifier based solution for > fast-switch enabled platforms later? No it doesn't, but I thought it would be better to have a single solution

Re: [PATCH 2/6] drivers base/arch_topology: frequency-invariant load-tracking support

On 21-06-17, 17:57, Morten Rasmussen wrote: > It is true that this patch relies on the notifiers, but I don't see how > that prevents us from adding a non-notifier based solution for > fast-switch enabled platforms later? No it doesn't, but I thought it would be better to have a single solution

[PATCH] radio: wl1273: add check on core->write() return value

Check return value from call to core->write(), so in case of error print error message, jump to goto label fail and eventually return. Addresses-Coverity-ID: 1226943 Signed-off-by: Gustavo A. R. Silva --- drivers/media/radio/radio-wl1273.c | 15 +-- 1 file

[PATCH] radio: wl1273: add check on core->write() return value

Check return value from call to core->write(), so in case of error print error message, jump to goto label fail and eventually return. Addresses-Coverity-ID: 1226943 Signed-off-by: Gustavo A. R. Silva --- drivers/media/radio/radio-wl1273.c | 15 +-- 1 file changed, 13 insertions(+),

Re: linux-next: Tree for Jun 7 (arch/x86/mm/tlb.c: events)

334:21: error: 'NR_TLB_REMOTE_FLUSH' undeclared (first >> use in this function) >> count_vm_tlb_event(NR_TLB_REMOTE_FLUSH); >> ^ >> ../include/linux/vmstat.h:90:49: note: in definition of macro >> 'count_vm_tlb_event' >> #define count_vm_tlb_event(x)count_vm_event(x) > > Do you know if this has been fixed? > I cannot repro it on linux-next of 20170621. -- ~Randy

Re: linux-next: Tree for Jun 7 (arch/x86/mm/tlb.c: events)

_FLUSH' undeclared (first >> use in this function) >> count_vm_tlb_event(NR_TLB_REMOTE_FLUSH); >> ^ >> ../include/linux/vmstat.h:90:49: note: in definition of macro >> 'count_vm_tlb_event' >> #define count_vm_tlb_event(x)count_vm_event(x) > > Do you know if this has been fixed? > I cannot repro it on linux-next of 20170621. -- ~Randy

Re: [PATCH 2/6] drivers base/arch_topology: frequency-invariant load-tracking support

On 21-06-17, 17:38, Dietmar Eggemann wrote: > On 20/06/17 07:17, Viresh Kumar wrote: > > Any specific reason on why are we doing this from PRECHANGE and > > not POSTCHANGE ? i.e. we are doing this before the frequency is > > really updated. > > Not really. In case I get a CPUFREQ_POSTCHANGE all

Re: [PATCH 2/6] drivers base/arch_topology: frequency-invariant load-tracking support

On 21-06-17, 17:38, Dietmar Eggemann wrote: > On 20/06/17 07:17, Viresh Kumar wrote: > > Any specific reason on why are we doing this from PRECHANGE and > > not POSTCHANGE ? i.e. we are doing this before the frequency is > > really updated. > > Not really. In case I get a CPUFREQ_POSTCHANGE all

Re: [PATCH 1/1] futex: remove duplicated code and fix UB

On Wed, Jun 21, 2017 at 01:53:18PM +0200, Jiri Slaby wrote: > There is code duplicated over all architecture's headers for > futex_atomic_op_inuser. Namely op decoding, access_ok check for uaddr, > and comparison of the result. > > Remove this duplication and leave up to the arches only the

Re: [PATCH 1/1] futex: remove duplicated code and fix UB

On Wed, Jun 21, 2017 at 01:53:18PM +0200, Jiri Slaby wrote: > There is code duplicated over all architecture's headers for > futex_atomic_op_inuser. Namely op decoding, access_ok check for uaddr, > and comparison of the result. > > Remove this duplication and leave up to the arches only the

Re: [PATCH NET] net/hns:bugfix of ethtool -t phy self_test

Hi, Andrew On 2017/6/22 11:35, Andrew Lunn wrote: >> I don't think returning to user space is an option, because it mean >> ethtool phy self test would fail because if availability of some software >> resoure, which is not some application would expect. here is what I can >> think of: >> >>

Re: [PATCH NET] net/hns:bugfix of ethtool -t phy self_test

Hi, Andrew On 2017/6/22 11:35, Andrew Lunn wrote: >> I don't think returning to user space is an option, because it mean >> ethtool phy self test would fail because if availability of some software >> resoure, which is not some application would expect. here is what I can >> think of: >> >>

[Patch v2 3/3] arm64: dts: register Hi3660's thermal sensor

Bind thermal sensor driver for Hi3660. Signed-off-by: Tao Wang Signed-off-by: Leo Yan --- Changes in v2: - rebase changes on linux next arch/arm64/boot/dts/hisilicon/hi3660.dtsi |6 ++ 1 file changed, 6 insertions(+) diff --git

[Patch v2 3/3] arm64: dts: register Hi3660's thermal sensor

Bind thermal sensor driver for Hi3660. Signed-off-by: Tao Wang Signed-off-by: Leo Yan --- Changes in v2: - rebase changes on linux next arch/arm64/boot/dts/hisilicon/hi3660.dtsi |6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm64/boot/dts/hisilicon/hi3660.dtsi

[Patch v2 1/3] dt-bindings: Document the hi3660 thermal sensor bindings

This adds documentation of device tree bindings for the thermal sensor controller of hi3660 SoC. Signed-off-by: Tao Wang --- Changes in v2: - remove redundant property .../devicetree/bindings/thermal/hi3660-thermal.txt | 16 1 file changed, 16

[Patch v2 2/3] thermal: hisilicon: add thermal sensor driver for Hi3660

This patch adds the support for thermal sensor of Hi3660 SoC. this will register sensors for thermal framework and use device tree to bind cooling device. Signed-off-by: Tao Wang Signed-off-by: Leo Yan --- Changes in v2: - correct alphabet order

[Patch v2 1/3] dt-bindings: Document the hi3660 thermal sensor bindings

This adds documentation of device tree bindings for the thermal sensor controller of hi3660 SoC. Signed-off-by: Tao Wang --- Changes in v2: - remove redundant property .../devicetree/bindings/thermal/hi3660-thermal.txt | 16 1 file changed, 16 insertions(+) create mode

[Patch v2 2/3] thermal: hisilicon: add thermal sensor driver for Hi3660

This patch adds the support for thermal sensor of Hi3660 SoC. this will register sensors for thermal framework and use device tree to bind cooling device. Signed-off-by: Tao Wang Signed-off-by: Leo Yan --- Changes in v2: - correct alphabet order - correct compatible name

[PATCH V5 Resend] PM / OPP: Use - instead of @ for DT entries

Compiling the DT file with W=1, DTC warns like follows: Warning (unit_address_vs_reg): Node /opp_table0/opp@10 has a unit name, but no reg property Fix this by replacing '@' with '-' as the OPP nodes will never have a "reg" property. Reported-by: Krzysztof Kozlowski

[PATCH V5 Resend] PM / OPP: Use - instead of @ for DT entries

Compiling the DT file with W=1, DTC warns like follows: Warning (unit_address_vs_reg): Node /opp_table0/opp@10 has a unit name, but no reg property Fix this by replacing '@' with '-' as the OPP nodes will never have a "reg" property. Reported-by: Krzysztof Kozlowski Reported-by:

Re: [RFC][PATCH 0/2] x86/boot/KASLR: Restrict kernel to be randomized in mirror regions if existed

On Thu, Jun 22, 2017 at 11:20:32AM +0800, Baoquan He wrote: >On 06/22/17 at 11:10am, Chao Fan wrote: >> Hi all, >> >> After testing this issue for 100 times in total, I think this patchset >> works well. > >Thanks for your effort, Chao! No problem, and many thanks for your patch, Bao! > >Then I

Re: [RFC][PATCH 0/2] x86/boot/KASLR: Restrict kernel to be randomized in mirror regions if existed

On Thu, Jun 22, 2017 at 11:20:32AM +0800, Baoquan He wrote: >On 06/22/17 at 11:10am, Chao Fan wrote: >> Hi all, >> >> After testing this issue for 100 times in total, I think this patchset >> works well. > >Thanks for your effort, Chao! No problem, and many thanks for your patch, Bao! > >Then I

Re: [PATCH NET] net/hns:bugfix of ethtool -t phy self_test

> I don't think returning to user space is an option, because it mean > ethtool phy self test would fail because if availability of some software > resoure, which is not some application would expect. here is what I can > think of: > > driver/net/ethernet/hisilicon/hns/hns_ethtool.c > int

Re: [PATCH NET] net/hns:bugfix of ethtool -t phy self_test

> I don't think returning to user space is an option, because it mean > ethtool phy self test would fail because if availability of some software > resoure, which is not some application would expect. here is what I can > think of: > > driver/net/ethernet/hisilicon/hns/hns_ethtool.c > int

Re: [PATCH 01/12] coresight replicator: Cleanup programmable replicator naming

On Tue, Jun 20, 2017 at 11:44 AM, Mathieu Poirier wrote: > On 18 June 2017 at 08:04, Rob Herring wrote: >> On Tue, Jun 13, 2017 at 10:55:28AM -0600, Mathieu Poirier wrote: >>> On Mon, Jun 12, 2017 at 03:36:40PM +0100, Suzuki K Poulose wrote: >>> > The

Re: [PATCH 01/12] coresight replicator: Cleanup programmable replicator naming

On Tue, Jun 20, 2017 at 11:44 AM, Mathieu Poirier wrote: > On 18 June 2017 at 08:04, Rob Herring wrote: >> On Tue, Jun 13, 2017 at 10:55:28AM -0600, Mathieu Poirier wrote: >>> On Mon, Jun 12, 2017 at 03:36:40PM +0100, Suzuki K Poulose wrote: >>> > The Linux coresight drivers define the

[PATCH] tuners: mxl5005s: remove useless variable assignments

Values assigned to variables Fmax and Fmin at lines 2740 and 2741 are overwritten at lines 2754 and 2755 before they can be used. This makes such variable assignments useless. Addresses-Coverity-ID: 1226952 Addresses-Coverity-ID: 1226953 Signed-off-by: Gustavo A. R. Silva

[PATCH] tuners: mxl5005s: remove useless variable assignments

Values assigned to variables Fmax and Fmin at lines 2740 and 2741 are overwritten at lines 2754 and 2755 before they can be used. This makes such variable assignments useless. Addresses-Coverity-ID: 1226952 Addresses-Coverity-ID: 1226953 Signed-off-by: Gustavo A. R. Silva ---

Re: [RFC][PATCH 0/2] x86/boot/KASLR: Restrict kernel to be randomized in mirror regions if existed

On 06/22/17 at 11:10am, Chao Fan wrote: > Hi all, > > After testing this issue for 100 times in total, I think this patchset > works well. Thanks for your effort, Chao! Then I will repost with some modification according to the kbuild test report and your comment, and thanks again for that.

Re: [RFC][PATCH 0/2] x86/boot/KASLR: Restrict kernel to be randomized in mirror regions if existed

On 06/22/17 at 11:10am, Chao Fan wrote: > Hi all, > > After testing this issue for 100 times in total, I think this patchset > works well. Thanks for your effort, Chao! Then I will repost with some modification according to the kbuild test report and your comment, and thanks again for that.

[PATCH] iio: adc: Add support for DLN2 ADC

This patch adds support for Diolan DLN2 ADC via IIO's ADC interface. ADC is the fourth and final component of the DLN2 for the kernel. Signed-off-by: Jack Andersen --- drivers/iio/adc/Kconfig| 9 + drivers/iio/adc/Makefile | 1 + drivers/iio/adc/dln2-adc.c | 648

[PATCH] iio: adc: Add support for DLN2 ADC

This patch adds support for Diolan DLN2 ADC via IIO's ADC interface. ADC is the fourth and final component of the DLN2 for the kernel. Signed-off-by: Jack Andersen --- drivers/iio/adc/Kconfig| 9 + drivers/iio/adc/Makefile | 1 + drivers/iio/adc/dln2-adc.c | 648

[PATCH] DLN2 module for ADC interface

Hello, I've been having to blacklist the dln2 module in order to use Diolan's iffy libusb-based "driver". I'd much rather use dln2, but the lack of ADC support has been an issue for my robotics application. I've extended the dln2 module with an additional platform driver to expose the ADC using

Re: [PATCH v1 1/2] dt-binding: ptp: add bindings document for dte based ptp clock

On Tue, Jun 20, 2017 at 3:48 PM, Scott Branden wrote: > Hi Rob, > > > On 17-06-18 07:04 AM, Rob Herring wrote: >> >> On Mon, Jun 12, 2017 at 01:26:00PM -0700, Arun Parameswaran wrote: >>> >>> Add device tree binding documentation for the Broadcom DTE >>> PTP clock

[PATCH] DLN2 module for ADC interface

Hello, I've been having to blacklist the dln2 module in order to use Diolan's iffy libusb-based "driver". I'd much rather use dln2, but the lack of ADC support has been an issue for my robotics application. I've extended the dln2 module with an additional platform driver to expose the ADC using

Re: [PATCH v1 1/2] dt-binding: ptp: add bindings document for dte based ptp clock

On Tue, Jun 20, 2017 at 3:48 PM, Scott Branden wrote: > Hi Rob, > > > On 17-06-18 07:04 AM, Rob Herring wrote: >> >> On Mon, Jun 12, 2017 at 01:26:00PM -0700, Arun Parameswaran wrote: >>> >>> Add device tree binding documentation for the Broadcom DTE >>> PTP clock driver. >>> >>> Signed-off-by:

  1   2   3   4   5   6   7   8   9   10   >