Re: [PATCH 3/3] hid: logitech-dj: delete unnecessary error messages

Hello Christoph, On Wed, Feb 07, 2018 at 06:08:00PM +0100, Christoph Böhmwalder wrote: > Remove some "out of memory" messages that are considered useless. > > Signed-off-by: Christoph Böhmwalder > --- > drivers/hid/hid-logitech-dj.c | 11 +++ > 1 file changed,

Re: [PATCH 3/3] hid: logitech-dj: delete unnecessary error messages

Hello Christoph, On Wed, Feb 07, 2018 at 06:08:00PM +0100, Christoph Böhmwalder wrote: > Remove some "out of memory" messages that are considered useless. > > Signed-off-by: Christoph Böhmwalder > --- > drivers/hid/hid-logitech-dj.c | 11 +++ > 1 file changed, 3 insertions(+), 8

Re: [PATCH] ACPI/IORT: Remove linker section for IORT entries again

On 07/02/2018 05:11, Jia He wrote: > In commit 316ca8804ea8 ("ACPI/IORT: Remove linker section for IORT entries > probing"), iort entries was removed in vmlinux.lds.h. But in > commit 2fcc112af37f ("clocksource/drivers: Rename clksrc table to timer"), > this line was back incorrectly. > > It does

Re: [PATCH] ACPI/IORT: Remove linker section for IORT entries again

On 07/02/2018 05:11, Jia He wrote: > In commit 316ca8804ea8 ("ACPI/IORT: Remove linker section for IORT entries > probing"), iort entries was removed in vmlinux.lds.h. But in > commit 2fcc112af37f ("clocksource/drivers: Rename clksrc table to timer"), > this line was back incorrectly. > > It does

Re: [PATCH] selftests/x86: Remove 5lvl test from Makefile

On Wed, Feb 07, 2018 at 11:50:28PM -0600, Daniel Díaz wrote: > The 5lvl.c test file was incorporated into another one in > selftests/vm (va_128TBswitch.c) in commit 235266b8. > > Signed-off-by: Daniel Díaz Acked-by: Kirill A. Shutemov

Re: [PATCH] selftests/x86: Remove 5lvl test from Makefile

On Wed, Feb 07, 2018 at 11:50:28PM -0600, Daniel Díaz wrote: > The 5lvl.c test file was incorporated into another one in > selftests/vm (va_128TBswitch.c) in commit 235266b8. > > Signed-off-by: Daniel Díaz Acked-by: Kirill A. Shutemov -- Kirill A. Shutemov

Re: [PATCH v2] ARM: dts: imx6ull: add Toradex Colibri iMX6ULL support

On Tue, Feb 06, 2018 at 05:49:03PM +0100, Stefan Agner wrote: > Add support for the Computer on Module Colibri iMX6ULL and its > Bluetooth/Wifi variant along with the development/evaluation carrier > board device trees. Follow the usual hierarchic include model, > maintaining shared configuration

Re: [PATCH v2] ARM: dts: imx6ull: add Toradex Colibri iMX6ULL support

On Tue, Feb 06, 2018 at 05:49:03PM +0100, Stefan Agner wrote: > Add support for the Computer on Module Colibri iMX6ULL and its > Bluetooth/Wifi variant along with the development/evaluation carrier > board device trees. Follow the usual hierarchic include model, > maintaining shared configuration

Re: [PATCH v2] drm/bridge/synopsys: dsi: Add 1.31 version support

On 06.02.2018 09:42, Philippe Cornu wrote: > Add support for the Synopsys DesignWare MIPI DSI version 1.31 > Two registers need to be updated/added for supporting 1.31: > * PHY_TMR_CFG 0x9c (updated) > 1.30 [31:24] phy_hs2lp_time >[23:16] phy_lp2hs_time >[14: 0] max_rd_time > >

Re: [PATCH] drm/bridge/synopsys: dsi: Add read feature

On 04.02.2018 22:31, Philippe Cornu wrote: > This patch adds the DCS/GENERIC DSI read feature. > > Signed-off-by: Philippe Cornu > --- Queued to drm-misc-next. -- Regards Andrzej

Re: [PATCH v2] drm/bridge/synopsys: dsi: Add 1.31 version support

On 06.02.2018 09:42, Philippe Cornu wrote: > Add support for the Synopsys DesignWare MIPI DSI version 1.31 > Two registers need to be updated/added for supporting 1.31: > * PHY_TMR_CFG 0x9c (updated) > 1.30 [31:24] phy_hs2lp_time >[23:16] phy_lp2hs_time >[14: 0] max_rd_time > >

Re: [PATCH] drm/bridge/synopsys: dsi: Add read feature

On 04.02.2018 22:31, Philippe Cornu wrote: > This patch adds the DCS/GENERIC DSI read feature. > > Signed-off-by: Philippe Cornu > --- Queued to drm-misc-next. -- Regards Andrzej

Re: [PATCH] KVM: X86: Fix SMRAM accessing even if VM is shutdown

2018-02-07 22:16 GMT+08:00 Paolo Bonzini : > On 07/02/2018 07:25, Wanpeng Li wrote: >> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c >> index 786cd00..445e702 100644 >> --- a/arch/x86/kvm/x86.c >> +++ b/arch/x86/kvm/x86.c >> @@ -7458,6 +7458,11 @@ int

Re: [PATCH] KVM: X86: Fix SMRAM accessing even if VM is shutdown

2018-02-07 22:16 GMT+08:00 Paolo Bonzini : > On 07/02/2018 07:25, Wanpeng Li wrote: >> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c >> index 786cd00..445e702 100644 >> --- a/arch/x86/kvm/x86.c >> +++ b/arch/x86/kvm/x86.c >> @@ -7458,6 +7458,11 @@ int kvm_arch_vcpu_ioctl_run(struct kvm_vcpu

Re: [PATCH 05/19] clk: meson: add regmap clocks

HI Jerome: On 02/01/18 02:09, Jerome Brunet wrote: > Meson clock controllers needs to move the classical iomem registers to > regmap. This is triggered because the HHI controllers found on the GXBB > and GXL host more than just clocks. To properly handle this, we would > like to migrate HHI to

Re: [PATCH 05/19] clk: meson: add regmap clocks

HI Jerome: On 02/01/18 02:09, Jerome Brunet wrote: > Meson clock controllers needs to move the classical iomem registers to > regmap. This is triggered because the HHI controllers found on the GXBB > and GXL host more than just clocks. To properly handle this, we would > like to migrate HHI to

[PATCH v2] KVM: X86: Fix SMRAM accessing even if VM is shutdown

From: Wanpeng Li Reported by syzkaller: WARNING: CPU: 6 PID: 2434 at arch/x86/kvm/vmx.c:6660 handle_ept_misconfig+0x54/0x1e0 [kvm_intel] CPU: 6 PID: 2434 Comm: repro_test Not tainted 4.15.0+ #4 RIP: 0010:handle_ept_misconfig+0x54/0x1e0 [kvm_intel] Call Trace:

[PATCH v2] KVM: X86: Fix SMRAM accessing even if VM is shutdown

From: Wanpeng Li Reported by syzkaller: WARNING: CPU: 6 PID: 2434 at arch/x86/kvm/vmx.c:6660 handle_ept_misconfig+0x54/0x1e0 [kvm_intel] CPU: 6 PID: 2434 Comm: repro_test Not tainted 4.15.0+ #4 RIP: 0010:handle_ept_misconfig+0x54/0x1e0 [kvm_intel] Call Trace:

[PATCH 2/2] regmap-i2c: Off by one in regmap_i2c_smbus_i2c_read/write()

The commit message says that we are allowed to read and write up to 32 bytes but the code only allows us to write 31 bytes. In other words, the ">=" should be changed to ">". But this is already checked in regmap_raw_read()/write() so we can just remove the if statemetents. Fixes: 29332534e2b6

[PATCH 2/2] regmap-i2c: Off by one in regmap_i2c_smbus_i2c_read/write()

The commit message says that we are allowed to read and write up to 32 bytes but the code only allows us to write 31 bytes. In other words, the ">=" should be changed to ">". But this is already checked in regmap_raw_read()/write() so we can just remove the if statemetents. Fixes: 29332534e2b6

[PATCH 1/2] regmap: Fix reversed bounds check in regmap_raw_write()

We're supposed to be checking that "val_len" is not too large but instead we check if it is smaller than the max. The only function affected would be regmap_i2c_smbus_i2c_write() in drivers/base/regmap/regmap-i2c.c. Strangely that function has its own limit check which returns an error if (count

[PATCH 1/2] regmap: Fix reversed bounds check in regmap_raw_write()

We're supposed to be checking that "val_len" is not too large but instead we check if it is smaller than the max. The only function affected would be regmap_i2c_smbus_i2c_write() in drivers/base/regmap/regmap-i2c.c. Strangely that function has its own limit check which returns an error if (count

Re: [RFC v2 PATCH 6/7] x86/entry: get rid of ALLOC_PT_GPREGS_ON_STACK and SAVE_AND_CLEAR_REGS

On Wed, Feb 07, 2018 at 01:58:20PM -0800, Linus Torvalds wrote: > I was just hoping that we could play some tricks. > > [...] > > See what I'm saying? Clever. Though I'd include the "pushq %rsi" in the macro, to be even more tricky. textdata bss dec hex filename 19500

Re: [RFC v2 PATCH 6/7] x86/entry: get rid of ALLOC_PT_GPREGS_ON_STACK and SAVE_AND_CLEAR_REGS

On Wed, Feb 07, 2018 at 01:58:20PM -0800, Linus Torvalds wrote: > I was just hoping that we could play some tricks. > > [...] > > See what I'm saying? Clever. Though I'd include the "pushq %rsi" in the macro, to be even more tricky. textdata bss dec hex filename 19500

Re: [PATCH BUGFIX V3] block, bfq: add requeue-request hook

> Il giorno 07 feb 2018, alle ore 23:18, Jens Axboe ha > scritto: > > On 2/7/18 2:19 PM, Paolo Valente wrote: >> Commit 'a6a252e64914 ("blk-mq-sched: decide how to handle flush rq via >> RQF_FLUSH_SEQ")' makes all non-flush re-prepared requests for a device >> be re-inserted

Re: [PATCH BUGFIX V3] block, bfq: add requeue-request hook

> Il giorno 07 feb 2018, alle ore 23:18, Jens Axboe ha > scritto: > > On 2/7/18 2:19 PM, Paolo Valente wrote: >> Commit 'a6a252e64914 ("blk-mq-sched: decide how to handle flush rq via >> RQF_FLUSH_SEQ")' makes all non-flush re-prepared requests for a device >> be re-inserted into the active

Re: [VDSO]: vdso_test failing on arm 32 bit

Dear Nathan & Russel, I have few more question about vdso for arm-32-bit. I am using iMX7 board to very VDSO gettimeofday timing. To make kernel/Documentation/vDSO/vdsotest work on this board, I commented the device tree reading property: arm,cpu-registers-not-fw-configured , from the :

Re: [VDSO]: vdso_test failing on arm 32 bit

Dear Nathan & Russel, I have few more question about vdso for arm-32-bit. I am using iMX7 board to very VDSO gettimeofday timing. To make kernel/Documentation/vDSO/vdsotest work on this board, I commented the device tree reading property: arm,cpu-registers-not-fw-configured , from the :

Re: [PATCH v2 BUGFIX] ARM: dts: imx6ull: fix the imx6ull-14x14-evk configuration

On Fri, Jan 26, 2018 at 09:52:18AM +0100, Lothar Waßmann wrote: > imx6ull-14x14-evk.dts currently includes the imx6ul.dtsi file for an > i.MX6ULL SoC which is plain wrong. > > Rename the current imx6ul-14x14-evk.dts to .dtsi and include it from > imx6ul-14x14-evk.dts and imx6ull-14x14-evk.dts, so

Re: [PATCH v2 BUGFIX] ARM: dts: imx6ull: fix the imx6ull-14x14-evk configuration

On Fri, Jan 26, 2018 at 09:52:18AM +0100, Lothar Waßmann wrote: > imx6ull-14x14-evk.dts currently includes the imx6ul.dtsi file for an > i.MX6ULL SoC which is plain wrong. > > Rename the current imx6ul-14x14-evk.dts to .dtsi and include it from > imx6ul-14x14-evk.dts and imx6ull-14x14-evk.dts, so

Re: [PATCH 2/2] kconfig: echo stdin to stdout if either is redirected

On Thu, Feb 8, 2018 at 7:51 AM, Ulf Magnusson wrote: > On Thu, Feb 8, 2018 at 7:35 AM, Ulf Magnusson wrote: >> On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada >> wrote: >>> If stdio is not tty, conf_askvalue() puts

Re: [PATCH 2/2] kconfig: echo stdin to stdout if either is redirected

On Thu, Feb 8, 2018 at 7:51 AM, Ulf Magnusson wrote: > On Thu, Feb 8, 2018 at 7:35 AM, Ulf Magnusson wrote: >> On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada >> wrote: >>> If stdio is not tty, conf_askvalue() puts additional new line to >>> prevent prompts are all concatenated into a single

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

* Will Deacon wrote: > For the sake of avoiding the conflict, can we just drop it for now, please? Yeah, so I resolved the conflict by merging the (already upstream) bits and Linus pulled that resolution. From now on the level of comments you want there is up to you!

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

* Will Deacon wrote: > For the sake of avoiding the conflict, can we just drop it for now, please? Yeah, so I resolved the conflict by merging the (already upstream) bits and Linus pulled that resolution. From now on the level of comments you want there is up to you! :-) Thanks,

Re: [PATCH 2/2] kconfig: echo stdin to stdout if either is redirected

2018-02-08 15:51 GMT+09:00 Ulf Magnusson : > On Thu, Feb 8, 2018 at 7:35 AM, Ulf Magnusson wrote: >> On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada >> wrote: >>> If stdio is not tty, conf_askvalue() puts additional new

Re: [PATCH 2/2] kconfig: echo stdin to stdout if either is redirected

2018-02-08 15:51 GMT+09:00 Ulf Magnusson : > On Thu, Feb 8, 2018 at 7:35 AM, Ulf Magnusson wrote: >> On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada >> wrote: >>> If stdio is not tty, conf_askvalue() puts additional new line to >>> prevent prompts are all concatenated into a single line. This

Re: [PATCH 2/2] kconfig: echo stdin to stdout if either is redirected

On Thu, Feb 8, 2018 at 7:35 AM, Ulf Magnusson wrote: > On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada > wrote: >> If stdio is not tty, conf_askvalue() puts additional new line to >> prevent prompts are all concatenated into a single line.

Re: [PATCH 2/2] kconfig: echo stdin to stdout if either is redirected

On Thu, Feb 8, 2018 at 7:35 AM, Ulf Magnusson wrote: > On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada > wrote: >> If stdio is not tty, conf_askvalue() puts additional new line to >> prevent prompts are all concatenated into a single line. This care >> is missing in conf_choice(), so a 'choice'

[PATCH v2 1/2] net, can, ifi: fix "write buffer full" error

the driver reads in the ISR first the IRQpending register, and clears after that in a write *all* bits in it. It could happen that the isr register raise bits between this 2 register accesses, which leads in lost bits ... In case it clears "TX message sent successfully", the driver never sends

[PATCH v2 1/2] net, can, ifi: fix "write buffer full" error

the driver reads in the ISR first the IRQpending register, and clears after that in a write *all* bits in it. It could happen that the isr register raise bits between this 2 register accesses, which leads in lost bits ... In case it clears "TX message sent successfully", the driver never sends

[PATCH net-queue 2/3] e1000e: Fix queue interrupt re-raising in Other interrupt.

restores the ICS write for rx/tx queue interrupts which was present before commit 16ecba59bc33 ("e1000e: Do not read ICR in Other interrupt", v4.5-rc1) but was not restored in commit 4aea7a5c5e94 ("e1000e: Avoid receiver overrun interrupt bursts", v4.15-rc1). This re-raises the queue interrupts

[PATCH v2 2/2] net, can, ifi: loopback Tx message in IFI block

Current ifi driver reads first Rx messages, than loopback the Tx message, if the IFI_CANFD_INTERRUPT_TXFIFO_REMOVE bit is set. This can lead into the case, that Rx messages overhelm Tx messages! Fixed this in the following way: Set in the IFI_CANFD_TXFIFO_DLC register the FN value to 1, so the

[PATCH net-queue 2/3] e1000e: Fix queue interrupt re-raising in Other interrupt.

restores the ICS write for rx/tx queue interrupts which was present before commit 16ecba59bc33 ("e1000e: Do not read ICR in Other interrupt", v4.5-rc1) but was not restored in commit 4aea7a5c5e94 ("e1000e: Avoid receiver overrun interrupt bursts", v4.15-rc1). This re-raises the queue interrupts

[PATCH v2 2/2] net, can, ifi: loopback Tx message in IFI block

Current ifi driver reads first Rx messages, than loopback the Tx message, if the IFI_CANFD_INTERRUPT_TXFIFO_REMOVE bit is set. This can lead into the case, that Rx messages overhelm Tx messages! Fixed this in the following way: Set in the IFI_CANFD_TXFIFO_DLC register the FN value to 1, so the

Re: [PATCH v2 1/2] soc: imx: gpcv2: Do not pass static memory as platform data

On Mon, Jan 22, 2018 at 07:07:47AM -0800, Andrey Smirnov wrote: > Platform device core assumes the ownership of dev.platform_data as > well as that it is dynamically allocated and it will try to kfree it > as a part of platform_device_release(). Change the code to pass > kzalloc'ed chunk of memory

Re: [PATCH v2 1/2] soc: imx: gpcv2: Do not pass static memory as platform data

On Mon, Jan 22, 2018 at 07:07:47AM -0800, Andrey Smirnov wrote: > Platform device core assumes the ownership of dev.platform_data as > well as that it is dynamically allocated and it will try to kfree it > as a part of platform_device_release(). Change the code to pass > kzalloc'ed chunk of memory

[PATCH net-queue 1/3] Partial revert "e1000e: Avoid receiver overrun interrupt bursts"

This partially reverts commit 4aea7a5c5e940c1723add439f4088844cd26196d. We keep the fix for the first part of the problem (1) described in the log of that commit, that is to read ICR in the other interrupt handler. We remove the fix for the second part of the problem (2), Other interrupt

[PATCH net-queue 3/3] e1000e: Avoid missed interrupts following ICR read.

The 82574 specification update errata 12 states that interrupts may be missed if ICR is read while INT_ASSERTED is not set. Avoid that problem by setting all bits related to events that can trigger the Other interrupt in IMS. The Other interrupt is raised for such events regardless of whether or

[PATCH net-queue 1/3] Partial revert "e1000e: Avoid receiver overrun interrupt bursts"

This partially reverts commit 4aea7a5c5e940c1723add439f4088844cd26196d. We keep the fix for the first part of the problem (1) described in the log of that commit, that is to read ICR in the other interrupt handler. We remove the fix for the second part of the problem (2), Other interrupt

[PATCH net-queue 3/3] e1000e: Avoid missed interrupts following ICR read.

The 82574 specification update errata 12 states that interrupts may be missed if ICR is read while INT_ASSERTED is not set. Avoid that problem by setting all bits related to events that can trigger the Other interrupt in IMS. The Other interrupt is raised for such events regardless of whether or

Re: [PATCHv2] ARM: dts: imx6q-bx50v3: Enable secure-reg-access

On Mon, Feb 05, 2018 at 06:08:40PM +0100, Sebastian Reichel wrote: > From: Peter Senna Tschudin > > Enable secure debug enable register access for Bx50v3 devices to enable > PMU and hardware counters for perf. > > Signed-off-by: Peter Senna Tschudin

Re: [PATCHv2] ARM: dts: imx6q-bx50v3: Enable secure-reg-access

On Mon, Feb 05, 2018 at 06:08:40PM +0100, Sebastian Reichel wrote: > From: Peter Senna Tschudin > > Enable secure debug enable register access for Bx50v3 devices to enable > PMU and hardware counters for perf. > > Signed-off-by: Peter Senna Tschudin > Signed-off-by: Sebastian Reichel > --- >

[PATCH] mpls, nospec: Sanitize array index in mpls_label_ok()

mpls_label_ok() validates that the 'platform_label' array index from a userspace netlink message payload is valid. Under speculation the mpls_label_ok() result may not resolve in the CPU pipeline until after the index is used to access an array element. Sanitize the index to zero to prevent

[PATCH] mpls, nospec: Sanitize array index in mpls_label_ok()

mpls_label_ok() validates that the 'platform_label' array index from a userspace netlink message payload is valid. Under speculation the mpls_label_ok() result may not resolve in the CPU pipeline until after the index is used to access an array element. Sanitize the index to zero to prevent

Re: [PATCH 3/3] Revert "e1000e: Do not read ICR in Other interrupt"

On 2018/01/29 09:22, Alexander Duyck wrote: [...] > > > Consequently, we must clear OTHER manually from ICR, otherwise the > > interrupt is immediately re-raised after exiting the handler. > > > > These observations are the same whether the interrupt is triggered via a > > write to ICS or in

Re: [PATCH 3/3] Revert "e1000e: Do not read ICR in Other interrupt"

On 2018/01/29 09:22, Alexander Duyck wrote: [...] > > > Consequently, we must clear OTHER manually from ICR, otherwise the > > interrupt is immediately re-raised after exiting the handler. > > > > These observations are the same whether the interrupt is triggered via a > > write to ICS or in

[PATCH] x86/linker script: drop superfluous ALIGN

ALIGN(8) is superfluous since macro TEXT_TEXT already has one. bonus: indentation fix, spaces -> tab. Signed-off-by: Cao jin --- arch/x86/kernel/vmlinux.lds.S | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/arch/x86/kernel/vmlinux.lds.S

[PATCH] x86/linker script: drop superfluous ALIGN

ALIGN(8) is superfluous since macro TEXT_TEXT already has one. bonus: indentation fix, spaces -> tab. Signed-off-by: Cao jin --- arch/x86/kernel/vmlinux.lds.S | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/arch/x86/kernel/vmlinux.lds.S b/arch/x86/kernel/vmlinux.lds.S

Re: dell-smbios makes wireless card unusable on Dell XPS 13 9360

Dear Mario, Am 08.02.2018 um 05:57 schrieb mario.limoncie...@dell.com: -Original Message- From: Paul Menzel [mailto:pmenzel+platform-driver-...@molgen.mpg.de] Sent: Wednesday, February 7, 2018 3:41 AM To: Limonciello, Mario Cc: Pali Rohár

Re: dell-smbios makes wireless card unusable on Dell XPS 13 9360

Dear Mario, Am 08.02.2018 um 05:57 schrieb mario.limoncie...@dell.com: -Original Message- From: Paul Menzel [mailto:pmenzel+platform-driver-...@molgen.mpg.de] Sent: Wednesday, February 7, 2018 3:41 AM To: Limonciello, Mario Cc: Pali Rohár ; it+platform-driver-...@molgen.mpg.de;

Re: [PATCH 2/2] kconfig: echo stdin to stdout if either is redirected

On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada wrote: > If stdio is not tty, conf_askvalue() puts additional new line to > prevent prompts are all concatenated into a single line. This care > is missing in conf_choice(), so a 'choice' prompt and the next prompt >

Re: [PATCH 2/2] kconfig: echo stdin to stdout if either is redirected

On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada wrote: > If stdio is not tty, conf_askvalue() puts additional new line to > prevent prompts are all concatenated into a single line. This care > is missing in conf_choice(), so a 'choice' prompt and the next prompt > are shown in the same line. > >

Regression after commit 19809c2da28a ("mm, vmalloc: use __GFP_HIGHMEM implicitly")

A user with i386 instead of AMD64 machine reports [1] that commit 19809c2da28a ("mm, vmalloc: use __GFP_HIGHMEM implicitly”) causes a regression. BUG_ON(PageHighMem(pg)) in drivers/media/common/saa7146/saa7146_core.c always gets triggered after that commit. Commit 704b862f9efd ("mm/vmalloc.c:

Regression after commit 19809c2da28a ("mm, vmalloc: use __GFP_HIGHMEM implicitly")

A user with i386 instead of AMD64 machine reports [1] that commit 19809c2da28a ("mm, vmalloc: use __GFP_HIGHMEM implicitly”) causes a regression. BUG_ON(PageHighMem(pg)) in drivers/media/common/saa7146/saa7146_core.c always gets triggered after that commit. Commit 704b862f9efd ("mm/vmalloc.c:

Re: [PATCH] KVM: nVMX: Fix CR4 after VMLAUNCH/VMRESUME failure

2018-02-08 0:57 GMT+08:00 Jim Mattson : > vmcs12->host_cr[34] does not contain the up-to-date values when L1 is > running. L1 can vmwrite any values there. We know at this point that It will incur a vmexit to emulate L1 vmwrites vmcs12->host_cr[34] even if vmcs shadow is

Re: [PATCH] KVM: nVMX: Fix CR4 after VMLAUNCH/VMRESUME failure

2018-02-08 0:57 GMT+08:00 Jim Mattson : > vmcs12->host_cr[34] does not contain the up-to-date values when L1 is > running. L1 can vmwrite any values there. We know at this point that It will incur a vmexit to emulate L1 vmwrites vmcs12->host_cr[34] even if vmcs shadow is enabled since host_cr[34]

Re: [PATCH 1/2] kconfig: remove check_stdin()

On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada wrote: > Except silentoldconfig, valid_stdin is 1, so check_stdin() is no-op. > > oldconfig and silentoldconfig work almost in the same way except that > the latter generates additional files. Both ask users for input

Re: [PATCH 1/2] kconfig: remove check_stdin()

On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada wrote: > Except silentoldconfig, valid_stdin is 1, so check_stdin() is no-op. > > oldconfig and silentoldconfig work almost in the same way except that > the latter generates additional files. Both ask users for input for > new symbols. > > I do

Re: [PATCH] ALSA: usb-audio: Fix UAC2 get_ctl request with a RANGE attribute

On 02/07/18 06:45, Takashi Iwai wrote: > On Mon, 29 Jan 2018 06:37:55 +0100, > Kirill Marinushkin wrote: >> The layout of the UAC2 Control request and response varies depending on >> the request type. With the current implementation, only the Layout 2 >> Parameter Block (with the 2-byte sized

Re: [PATCH] ALSA: usb-audio: Fix UAC2 get_ctl request with a RANGE attribute

On 02/07/18 06:45, Takashi Iwai wrote: > On Mon, 29 Jan 2018 06:37:55 +0100, > Kirill Marinushkin wrote: >> The layout of the UAC2 Control request and response varies depending on >> the request type. With the current implementation, only the Layout 2 >> Parameter Block (with the 2-byte sized

Re: [PATCH v3 1/2] dt-bindings: gpio: Add Spreadtrum GPIO controller documentation

Hi Rob, On 8 February 2018 at 05:19, Rob Herring wrote: > On Mon, Feb 05, 2018 at 09:55:10AM +0800, Baolin Wang wrote: >> This patch adds the device tree bindings for the Spreadtrum >> GPIO controller. The gpios will be supported by the GPIO >> generic library. >> >>

Re: [PATCH v3 1/2] dt-bindings: gpio: Add Spreadtrum GPIO controller documentation

Hi Rob, On 8 February 2018 at 05:19, Rob Herring wrote: > On Mon, Feb 05, 2018 at 09:55:10AM +0800, Baolin Wang wrote: >> This patch adds the device tree bindings for the Spreadtrum >> GPIO controller. The gpios will be supported by the GPIO >> generic library. >> >> Signed-off-by: Baolin Wang

Re: linux-next: Signed-off-by missing for commit in the s390 tree

On Thu, 8 Feb 2018 07:35:39 +1100 Stephen Rothwell wrote: > Commit > > b175210bd231 ("s390/kconfig: Remove ARCH_WANTS_PROT_NUMA_PROT_NONE select") > > is missing a Signed-off-by from its committer. It is always that "last" one you add. Fixed. Thanks. -- blue skies,

Re: linux-next: Signed-off-by missing for commit in the s390 tree

On Thu, 8 Feb 2018 07:35:39 +1100 Stephen Rothwell wrote: > Commit > > b175210bd231 ("s390/kconfig: Remove ARCH_WANTS_PROT_NUMA_PROT_NONE select") > > is missing a Signed-off-by from its committer. It is always that "last" one you add. Fixed. Thanks. -- blue skies, Martin. "Reality

[git pull] drm for v4.16-rc1 (part 2 - fixes)

Hi Linus, Ben missed sending his tree, but he really didn't have much stuff in it, GP108 acceleration support is enabled by "secure boot" support, some clockgating work on Kepler, and bunch of fixes. The main bulk is regenerated firmware files, the change to them really isn't that large.

[git pull] drm for v4.16-rc1 (part 2 - fixes)

Hi Linus, Ben missed sending his tree, but he really didn't have much stuff in it, GP108 acceleration support is enabled by "secure boot" support, some clockgating work on Kepler, and bunch of fixes. The main bulk is regenerated firmware files, the change to them really isn't that large.

Re: [PATCH 04/14] kconfig: print additional new line for choice for redirection

2018-02-08 8:34 GMT+09:00 Ulf Magnusson : > On Tue, Feb 6, 2018 at 1:34 AM, Masahiro Yamada > wrote: >> If stdout is redirected to a file, prompts look differently due to >> missing new lines. >> >> Currently, conf_askvalue() takes care of this

Re: [PATCH 04/14] kconfig: print additional new line for choice for redirection

2018-02-08 8:34 GMT+09:00 Ulf Magnusson : > On Tue, Feb 6, 2018 at 1:34 AM, Masahiro Yamada > wrote: >> If stdout is redirected to a file, prompts look differently due to >> missing new lines. >> >> Currently, conf_askvalue() takes care of this by putting additional >> new line, but conf_choice()

[PATCH 2/2] kconfig: echo stdin to stdout if either is redirected

If stdio is not tty, conf_askvalue() puts additional new line to prevent prompts are all concatenated into a single line. This care is missing in conf_choice(), so a 'choice' prompt and the next prompt are shown in the same line. Move the code into xfgets() to take care of all cases. To improve

[PATCH 1/2] kconfig: remove check_stdin()

Except silentoldconfig, valid_stdin is 1, so check_stdin() is no-op. oldconfig and silentoldconfig work almost in the same way except that the latter generates additional files. Both ask users for input for new symbols. I do not know why only silentoldconfig requires stdio be tty. $ rm -f

[PATCH 2/2] kconfig: echo stdin to stdout if either is redirected

If stdio is not tty, conf_askvalue() puts additional new line to prevent prompts are all concatenated into a single line. This care is missing in conf_choice(), so a 'choice' prompt and the next prompt are shown in the same line. Move the code into xfgets() to take care of all cases. To improve

[PATCH 1/2] kconfig: remove check_stdin()

Except silentoldconfig, valid_stdin is 1, so check_stdin() is no-op. oldconfig and silentoldconfig work almost in the same way except that the latter generates additional files. Both ask users for input for new symbols. I do not know why only silentoldconfig requires stdio be tty. $ rm -f

Re: [PATCH v2 2/5] clk: mediatek: modify MT7622 audsys to adapt MFD device

On Wed, 2018-02-07 at 16:18 +0100, Matthias Brugger wrote: > > On 02/05/2018 05:07 AM, Ryder Lee wrote: > > On Sat, 2018-02-03 at 15:26 +0100, Matthias Brugger wrote: > >> > >> On 01/31/2018 08:42 AM, Ryder Lee wrote: > >>> As the new MFD parent is in place, switch probing method to adapt it. >

Re: [PATCH v2 2/5] clk: mediatek: modify MT7622 audsys to adapt MFD device

On Wed, 2018-02-07 at 16:18 +0100, Matthias Brugger wrote: > > On 02/05/2018 05:07 AM, Ryder Lee wrote: > > On Sat, 2018-02-03 at 15:26 +0100, Matthias Brugger wrote: > >> > >> On 01/31/2018 08:42 AM, Ryder Lee wrote: > >>> As the new MFD parent is in place, switch probing method to adapt it. >

Re: [PATCH v2 4/5] dt-bindings: clock: mediatek: update audsys documentation to adapt MFD device

On Wed, 2018-02-07 at 18:49 -0600, Rob Herring wrote: > >> > diff --git > >> > a/Documentation/devicetree/bindings/arm/mediatek/mediatek,audsys.txt > >> > b/Documentation/devicetree/bindings/arm/mediatek/mediatek,audsys.txt > >> > index 9b8f578..677af40 100644 > >> > ---

Re: [PATCH v2 4/5] dt-bindings: clock: mediatek: update audsys documentation to adapt MFD device

On Wed, 2018-02-07 at 18:49 -0600, Rob Herring wrote: > >> > diff --git > >> > a/Documentation/devicetree/bindings/arm/mediatek/mediatek,audsys.txt > >> > b/Documentation/devicetree/bindings/arm/mediatek/mediatek,audsys.txt > >> > index 9b8f578..677af40 100644 > >> > ---

[PATCH] selftests/x86: Remove 5lvl test from Makefile

The 5lvl.c test file was incorporated into another one in selftests/vm (va_128TBswitch.c) in commit 235266b8. Signed-off-by: Daniel Díaz --- tools/testing/selftests/x86/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] selftests/x86: Remove 5lvl test from Makefile

The 5lvl.c test file was incorporated into another one in selftests/vm (va_128TBswitch.c) in commit 235266b8. Signed-off-by: Daniel Díaz --- tools/testing/selftests/x86/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/testing/selftests/x86/Makefile

Re: [PATCH 04/18] tracing/x86: Add arch_get_func_args() function

Hi Steve, On Fri, Feb 02, 2018 at 06:05:02PM -0500, Steven Rostedt wrote: > From: "Steven Rostedt (VMware)" > > Add function to get the function arguments from pt_regs. > > Signed-off-by: Steven Rostedt (VMware) > --- > arch/x86/kernel/ftrace.c | 28

Re: [PATCH 04/18] tracing/x86: Add arch_get_func_args() function

Hi Steve, On Fri, Feb 02, 2018 at 06:05:02PM -0500, Steven Rostedt wrote: > From: "Steven Rostedt (VMware)" > > Add function to get the function arguments from pt_regs. > > Signed-off-by: Steven Rostedt (VMware) > --- > arch/x86/kernel/ftrace.c | 28 > 1 file

[PATCH] ath9k: turn on btcoex_enable as default

Without btcoex_enable, WiFi activies make both WiFi and Bluetooth unstable if there's a bluetooth connection. Enable this option when bt_ant_diversity is disabled. BugLink: https://bugs.launchpad.net/bugs/1746164 Signed-off-by: Kai-Heng Feng ---

[PATCH] ath9k: turn on btcoex_enable as default

Without btcoex_enable, WiFi activies make both WiFi and Bluetooth unstable if there's a bluetooth connection. Enable this option when bt_ant_diversity is disabled. BugLink: https://bugs.launchpad.net/bugs/1746164 Signed-off-by: Kai-Heng Feng --- drivers/net/wireless/ath/ath9k/init.c | 10

Re: [PATCH RFC 2/2] mmc: sdhci-msm: support voltage pad switching

On 2/3/2018 3:21 AM, Bjorn Andersson wrote: On Thu 18 Jan 00:05 PST 2018, Vijay Viswanath wrote: From: Krishna Konda The PADs for sdhc controller are dual-voltage that support 3v/1.8v. Those PADs have a control signal (io_pad_pwr_switch/mode18 ) that indicates

Re: [PATCH RFC 2/2] mmc: sdhci-msm: support voltage pad switching

On 2/3/2018 3:21 AM, Bjorn Andersson wrote: On Thu 18 Jan 00:05 PST 2018, Vijay Viswanath wrote: From: Krishna Konda The PADs for sdhc controller are dual-voltage that support 3v/1.8v. Those PADs have a control signal (io_pad_pwr_switch/mode18 ) that indicates whether the PAD works in 3v

Re: [PATCH] selftests/android: Fix line continuation in Makefile

On Wed, Feb 7, 2018 at 5:22 AM, Daniel Díaz wrote: > The Makefile lacks a couple of line continuation backslashes > in an `if' clause, which can make the subsequent rsync > command go awry over the whole filesystem (`rsync -a / /`). > > /bin/sh: -c: line 5: syntax error:

Re: [PATCH] selftests/android: Fix line continuation in Makefile

On Wed, Feb 7, 2018 at 5:22 AM, Daniel Díaz wrote: > The Makefile lacks a couple of line continuation backslashes > in an `if' clause, which can make the subsequent rsync > command go awry over the whole filesystem (`rsync -a / /`). > > /bin/sh: -c: line 5: syntax error: unexpected end of file

Re: [PATCH] selftests/android: Fix line continuation in Makefile

On Wed, Feb 7, 2018 at 10:46 PM, Daniel Díaz Rodríguez wrote: > Hello! > > > On 7 February 2018 at 00:01, Pintu Kumar wrote: > [...] >> Thanks for your patch. >> However, I have copied this Makefile from >> tools/testing/selftests/futex/Makefile

Re: [PATCH] selftests/android: Fix line continuation in Makefile

On Wed, Feb 7, 2018 at 10:46 PM, Daniel Díaz Rodríguez wrote: > Hello! > > > On 7 February 2018 at 00:01, Pintu Kumar wrote: > [...] >> Thanks for your patch. >> However, I have copied this Makefile from >> tools/testing/selftests/futex/Makefile before modifying it. >> If there is a problem with

[PATCH] x86/kvm/vmx: Don't halt vcpu when L1 is injecting events to L2

Although L2 is in halt state, it will be in the active state after VM entry if the VM entry is vectoring. Halting the vcpu here means the event won't be injected to L2 and this decision isn't reported to L1. Thus L0 drops an event that should be injected to L2. Because virtual interrupt delivery

[PATCH] x86/kvm/vmx: Don't halt vcpu when L1 is injecting events to L2

Although L2 is in halt state, it will be in the active state after VM entry if the VM entry is vectoring. Halting the vcpu here means the event won't be injected to L2 and this decision isn't reported to L1. Thus L0 drops an event that should be injected to L2. Because virtual interrupt delivery

  1   2   3   4   5   6   7   8   9   10   >