linux-next: manual merge of the target-updates tree with the scsi tree

Hi Nicholas, Today's linux-next merge of the target-updates tree got a conflict in: drivers/scsi/qla2xxx/qla_target.c between commit: c5419e2618b9 ("scsi: qla2xxx: Combine Active command arrays.") from the scsi tree and commit: bc1bb269ef7b ("qla2xxx: Fix incorrect tcm_qla2xxx_free_cmd

linux-next: manual merge of the target-updates tree with the scsi tree

Hi Nicholas, Today's linux-next merge of the target-updates tree got a conflict in: drivers/scsi/qla2xxx/qla_target.c between commit: c5419e2618b9 ("scsi: qla2xxx: Combine Active command arrays.") from the scsi tree and commit: bc1bb269ef7b ("qla2xxx: Fix incorrect tcm_qla2xxx_free_cmd

[linux-next] SMT off triggers WARNING: CPU: 1 PID: 13 at arch/powerpc/kernel/watchdog.c:314 stop_wd_on_cpu+0x54/0xf0

Hi, Today's next-20170630 on powerpc shows warnings in dmesg when SMT is disabled. Test: SMT off kernel: 4.12.0-rc7-next-20170630 Machine: Power 8 Bare-metal gcc: 4.8.5 config: attached Steps to recreate - 1. Boot powerpc machine with today's next kernel. By default SMT 8 is

[linux-next] SMT off triggers WARNING: CPU: 1 PID: 13 at arch/powerpc/kernel/watchdog.c:314 stop_wd_on_cpu+0x54/0xf0

Hi, Today's next-20170630 on powerpc shows warnings in dmesg when SMT is disabled. Test: SMT off kernel: 4.12.0-rc7-next-20170630 Machine: Power 8 Bare-metal gcc: 4.8.5 config: attached Steps to recreate - 1. Boot powerpc machine with today's next kernel. By default SMT 8 is

[PATCH] PCI: mediatek: Remove unnecessary PCI_REASSIGN_* flags

The PCI_REASSIGN_ALL_RSRC and PCI_REASSIGN_ALL_BUS flags are not needed, since we should automatically assign resources if the firmware hasn't done it. Signed-off-by: Ryder Lee --- drivers/pci/host/pcie-mediatek.c | 1 - 1 file changed, 1 deletion(-) diff --git

[PATCH] PCI: mediatek: Remove unnecessary PCI_REASSIGN_* flags

The PCI_REASSIGN_ALL_RSRC and PCI_REASSIGN_ALL_BUS flags are not needed, since we should automatically assign resources if the firmware hasn't done it. Signed-off-by: Ryder Lee --- drivers/pci/host/pcie-mediatek.c | 1 - 1 file changed, 1 deletion(-) diff --git

[GIT PULL] EDAC queue for 4.13

Hi Linus, please pull the EDAC pile for 4.13. Nothing earth-shattering - just the normal development flow of cleanups, improvements, fixes and such. Thanks. --- The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d: Linux 4.12-rc2 (2017-05-21 19:30:23 -0700) are

[GIT PULL] EDAC queue for 4.13

Hi Linus, please pull the EDAC pile for 4.13. Nothing earth-shattering - just the normal development flow of cleanups, improvements, fixes and such. Thanks. --- The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d: Linux 4.12-rc2 (2017-05-21 19:30:23 -0700) are

[PATCH 2/2] selftests: ftrace: Add more verbosity for immediate log

Add 3-level verbosity for showing traced command log on console immediately. Since some test cases can cause kernel pacic if there is a probrem (like regression etc.), we can not know which command caused the problem without traced command log. This verbosity (-vvv) solves that because it shows

[PATCH 2/2] selftests: ftrace: Add more verbosity for immediate log

Add 3-level verbosity for showing traced command log on console immediately. Since some test cases can cause kernel pacic if there is a probrem (like regression etc.), we can not know which command caused the problem without traced command log. This verbosity (-vvv) solves that because it shows

[PATCH 1/2] selftests: ftrace: Do not failure if there is unsupported tests

Do not return failure exit code (1) for unsupported testcases, since it is expected for stable kernels. Previously, ftracetest is expected to run only on current release for avoiding regressions. However, nowadays we run it on stable kernels. This means some test cases must return unsupported

[PATCH 1/2] selftests: ftrace: Do not failure if there is unsupported tests

Do not return failure exit code (1) for unsupported testcases, since it is expected for stable kernels. Previously, ftracetest is expected to run only on current release for avoiding regressions. However, nowadays we run it on stable kernels. This means some test cases must return unsupported

Re: [PATCH 02/14] qcom: mtd: nand: add and initialize QPIC DMA resources

On 06/29/2017 12:45 PM, Abhishek Sahu wrote: 1. The QPIC NAND uses 3 BAM channels: command, data tx and data rx while EBI2 NAND uses only single ADM channel. 2. The EBI2 NAND uses normal register read buffer since this buffer will be remapped with dma_map_sg. The QPIC NAND will give

Re: [PATCH 02/14] qcom: mtd: nand: add and initialize QPIC DMA resources

On 06/29/2017 12:45 PM, Abhishek Sahu wrote: 1. The QPIC NAND uses 3 BAM channels: command, data tx and data rx while EBI2 NAND uses only single ADM channel. 2. The EBI2 NAND uses normal register read buffer since this buffer will be remapped with dma_map_sg. The QPIC NAND will give

RE: [PATCH 3/3] ACPI: EC: Change EC noirq tuning to be an optional behavior

Hi, Rafael > From: Rafael J. Wysocki [mailto:r...@rjwysocki.net] > Subject: Re: [PATCH 3/3] ACPI: EC: Change EC noirq tuning to be an optional > behavior > > On Wednesday, June 14, 2017 01:59:24 PM Lv Zheng wrote: > > According to the bug report, though the busy polling mode can make noirq > >

RE: [PATCH 3/3] ACPI: EC: Change EC noirq tuning to be an optional behavior

Hi, Rafael > From: Rafael J. Wysocki [mailto:r...@rjwysocki.net] > Subject: Re: [PATCH 3/3] ACPI: EC: Change EC noirq tuning to be an optional > behavior > > On Wednesday, June 14, 2017 01:59:24 PM Lv Zheng wrote: > > According to the bug report, though the busy polling mode can make noirq > >

Re: [PATCH V2] dmaengine: qcom_hidma: correct API violation for submit

On Fri, Jun 30, 2017 at 10:43:05AM -0400, Sinan Kaya wrote: > Current code is violating the DMA Engine API by putting the submitted > requests directly into the HW queue. This causes queued transactions > to be started by another thread as soon as the first one finishes. > > The DMA Engine

Re: [PATCH V2] dmaengine: qcom_hidma: correct API violation for submit

On Fri, Jun 30, 2017 at 10:43:05AM -0400, Sinan Kaya wrote: > Current code is violating the DMA Engine API by putting the submitted > requests directly into the HW queue. This causes queued transactions > to be started by another thread as soon as the first one finishes. > > The DMA Engine

Re: [PATCH v2] X86: don't report PAT on CPUs that don't support it

On Tue, 6 Jun 2017, Mikulas Patocka wrote: > Hi > > Here I send the second version of the patch. It drops the change from > boot_cpu_has(X86_FEATURE_PAT) to this_cpu_has(X86_FEATURE_PAT) (that > caused kernel to be unbootable for some people). > > Another change is that setup_arch() calls

Re: [PATCH v2] X86: don't report PAT on CPUs that don't support it

On Tue, 6 Jun 2017, Mikulas Patocka wrote: > Hi > > Here I send the second version of the patch. It drops the change from > boot_cpu_has(X86_FEATURE_PAT) to this_cpu_has(X86_FEATURE_PAT) (that > caused kernel to be unbootable for some people). > > Another change is that setup_arch() calls

Re: [PATCH 1/1] staging: ks7010: Fix cast to restricted __le16 in ks_wlan_net.c

W dniu 2017-07-02 o 23:23, Luc Van Oostenryck pisze: On Sun, Jul 2, 2017 at 10:49 PM, Janusz Lisiecki wrote: W dniu 2017-07-02 o 21:38, Luc Van Oostenryck pisze: On Sun, Jul 2, 2017 at 4:27 PM, Janusz Lisiecki wrote: This patch fixes

Re: [PATCH 1/1] staging: ks7010: Fix cast to restricted __le16 in ks_wlan_net.c

W dniu 2017-07-02 o 23:23, Luc Van Oostenryck pisze: On Sun, Jul 2, 2017 at 10:49 PM, Janusz Lisiecki wrote: W dniu 2017-07-02 o 21:38, Luc Van Oostenryck pisze: On Sun, Jul 2, 2017 at 4:27 PM, Janusz Lisiecki wrote: This patch fixes the following Sparse warnings in ks_wlan_net.c:

[PATCH 1/1] staging: ks7010: Fix cast to restricted __le16 in ks_wlan_net.c

This patch fixes the following Sparse warnings in ks_wlan_net.c: drivers/staging/ks7010/ks_wlan_net.c:1359:24: warning: cast to restricted __le16 link_ap_info_t structure field 'capability' has native order and is used everywhere in the code in such way (i.e get_ap_information, get_current_ap).

[PATCH 1/1] staging: ks7010: Fix cast to restricted __le16 in ks_wlan_net.c

This patch fixes the following Sparse warnings in ks_wlan_net.c: drivers/staging/ks7010/ks_wlan_net.c:1359:24: warning: cast to restricted __le16 link_ap_info_t structure field 'capability' has native order and is used everywhere in the code in such way (i.e get_ap_information, get_current_ap).

[PATCH 0/1] Fix cast to restricted __le16 in ks7010 driver

This patch fixes Sparse warining found in ks_wlan_net.c. This seems to be last of it reported by Sparse for that driver. link_ap_info_t structure field 'capability' has native order and is used everywhere in the code in such way (i.e get_ap_information, get_current_ap), so le16_to_cpu() on it is

[PATCH 0/1] Fix cast to restricted __le16 in ks7010 driver

This patch fixes Sparse warining found in ks_wlan_net.c. This seems to be last of it reported by Sparse for that driver. link_ap_info_t structure field 'capability' has native order and is used everywhere in the code in such way (i.e get_ap_information, get_current_ap), so le16_to_cpu() on it is

Re: [PATCH 01/14] qcom: mtd: nand: Add driver data for QPIC DMA

On 06/29/2017 12:45 PM, Abhishek Sahu wrote: The current driver only support EBI2 NAND which uses ADM DMA. The latest QCOM controller supports QPIC NAND which uses BAM DMA. NAND registers and programming sequence are same for EBI2 and QPIC NAND so the same driver can support QPIC NAND also by

Re: [PATCH 01/14] qcom: mtd: nand: Add driver data for QPIC DMA

On 06/29/2017 12:45 PM, Abhishek Sahu wrote: The current driver only support EBI2 NAND which uses ADM DMA. The latest QCOM controller supports QPIC NAND which uses BAM DMA. NAND registers and programming sequence are same for EBI2 and QPIC NAND so the same driver can support QPIC NAND also by

[PATCH v3 3/3] hwmon: ltc2990: support all measurement modes

Updated version of the ltc2990 driver which supports all measurement modes (current, voltage, temperature) available in the chip. If devicetree is used, the mode must be specified with the property "lltc,meas-mode". The format and possible values of the property are described in the binding. If

[PATCH v3 3/3] hwmon: ltc2990: support all measurement modes

Updated version of the ltc2990 driver which supports all measurement modes (current, voltage, temperature) available in the chip. If devicetree is used, the mode must be specified with the property "lltc,meas-mode". The format and possible values of the property are described in the binding. If

[PATCH v3 2/3] hwmon: ltc2990: add devicetree binding

Add a devicetree binding for the ltc2990 hwmon driver. Signed-off-by: Tom Levens --- .../devicetree/bindings/hwmon/ltc2990.txt | 36 ++ 1 file changed, 36 insertions(+) create mode 100644 Documentation/devicetree/bindings/hwmon/ltc2990.txt diff

[PATCH v3 2/3] hwmon: ltc2990: add devicetree binding

Add a devicetree binding for the ltc2990 hwmon driver. Signed-off-by: Tom Levens --- .../devicetree/bindings/hwmon/ltc2990.txt | 36 ++ 1 file changed, 36 insertions(+) create mode 100644 Documentation/devicetree/bindings/hwmon/ltc2990.txt diff --git

[PATCH v3 1/3] hwmon: ltc2990: refactor value conversion

Conversion from raw values to signed integers has been refactored using bitops.h. This also fixes a bug where negative temperatures were converted incorrectly. Signed-off-by: Tom Levens --- drivers/hwmon/ltc2990.c | 18 -- 1 file changed, 4 insertions(+), 14

[PATCH v3 1/3] hwmon: ltc2990: refactor value conversion

Conversion from raw values to signed integers has been refactored using bitops.h. This also fixes a bug where negative temperatures were converted incorrectly. Signed-off-by: Tom Levens --- drivers/hwmon/ltc2990.c | 18 -- 1 file changed, 4 insertions(+), 14 deletions(-) diff

Re: [linux-next][PATCH] usb: dwc3: omap: remove IRQ_NOAUTOEN used with shared irq

Hi, On Saturday 01 July 2017 01:04 AM, Strashko, Grygorii wrote: > > > On 06/29/2017 01:03 AM, Tony Lindgren wrote: >> * Vignesh R [170628 21:21]: >>> >>> >>> On Thursday 29 June 2017 05:01 AM, Strashko, Grygorii wrote: IRQ_NOAUTOEN can't be used with shared IRQs and

Re: [linux-next][PATCH] usb: dwc3: omap: remove IRQ_NOAUTOEN used with shared irq

Hi, On Saturday 01 July 2017 01:04 AM, Strashko, Grygorii wrote: > > > On 06/29/2017 01:03 AM, Tony Lindgren wrote: >> * Vignesh R [170628 21:21]: >>> >>> >>> On Thursday 29 June 2017 05:01 AM, Strashko, Grygorii wrote: IRQ_NOAUTOEN can't be used with shared IRQs and Kernel now will

Re: [PATCH] PCI: Work around poweroff & suspend-to-RAM issue on Macbook Pro 11

Hi, On Sun, Jul 02, 2017 at 03:59:48PM -0500, Bjorn Helgaas wrote: > Neither soft poweroff (transition to ACPI power state S5) nor > suspend-to-RAM (transition to state S3) works on the Macbook Pro 11,4 and > 11,5. > > The problem is related to the [mem 0x7fa0-0x7fbf] space. When we >

Re: [PATCH] PCI: Work around poweroff & suspend-to-RAM issue on Macbook Pro 11

Hi, On Sun, Jul 02, 2017 at 03:59:48PM -0500, Bjorn Helgaas wrote: > Neither soft poweroff (transition to ACPI power state S5) nor > suspend-to-RAM (transition to state S3) works on the Macbook Pro 11,4 and > 11,5. > > The problem is related to the [mem 0x7fa0-0x7fbf] space. When we >

Re: [PATCH] selftests: ftrace: Use md5sum to take less time of checking logs

On Fri, 30 Jun 2017 10:53:15 -0600 Shuah Khan wrote: > On 06/30/2017 08:49 AM, Steven Rostedt wrote: > > On Thu, 29 Jun 2017 14:21:41 -0600 > > Shuah Khan wrote: > > \ > >> Hi Steve/Masami, > >> > >> I tested this patch on my test system running 4.12-rc7 and

Re: [PATCH] selftests: ftrace: Use md5sum to take less time of checking logs

On Fri, 30 Jun 2017 10:53:15 -0600 Shuah Khan wrote: > On 06/30/2017 08:49 AM, Steven Rostedt wrote: > > On Thu, 29 Jun 2017 14:21:41 -0600 > > Shuah Khan wrote: > > \ > >> Hi Steve/Masami, > >> > >> I tested this patch on my test system running 4.12-rc7 and didn't see any > >> problems. I am

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

Hi all, On Mon, 3 Jul 2017 13:56:16 +1000 Stephen Rothwell wrote: > > +if (cpu < nr_queues) { > - map[cpu] = cpu_to_queue_index(nr_queues, cpu, > online_mask); > ++map[cpu] = cpu_to_queue_index(nr_queues, cpu) > +

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

Hi all, On Mon, 3 Jul 2017 13:56:16 +1000 Stephen Rothwell wrote: > > +if (cpu < nr_queues) { > - map[cpu] = cpu_to_queue_index(nr_queues, cpu, > online_mask); > ++map[cpu] = cpu_to_queue_index(nr_queues, cpu) > +} else { > +

[PATCH] powerpc/powernv/idle: Put pnv_cpu_offline behind HOTPLUG_CPU

In commit 900612315788 ("powerpc/powernv/smp: Add busy-wait loop as fall back for CPU-Hotplug") the idle code uses generic_check_cpu_restart(), but that function is not available when CONFIG_HOTPLUG_CPU is disabled. arch/powerpc/platforms/powernv/idle.c: In function ‘pnv_cpu_offline’:

[PATCH] powerpc/powernv/idle: Put pnv_cpu_offline behind HOTPLUG_CPU

In commit 900612315788 ("powerpc/powernv/smp: Add busy-wait loop as fall back for CPU-Hotplug") the idle code uses generic_check_cpu_restart(), but that function is not available when CONFIG_HOTPLUG_CPU is disabled. arch/powerpc/platforms/powernv/idle.c: In function ‘pnv_cpu_offline’:

linux-next: manual merge of the tip tree with the block tree

Hi all, Today's linux-next merge of the tip tree got a conflict in: block/blk-mq-cpumap.c between commit: fe631457ff3e ("blk-mq: map all HWQ also in hyperthreaded system") from the block tree and commit: 5f042e7cbd9e ("blk-mq: Include all present CPUs in the default queue mapping")

linux-next: manual merge of the tip tree with the block tree

Hi all, Today's linux-next merge of the tip tree got a conflict in: block/blk-mq-cpumap.c between commit: fe631457ff3e ("blk-mq: map all HWQ also in hyperthreaded system") from the block tree and commit: 5f042e7cbd9e ("blk-mq: Include all present CPUs in the default queue mapping")

Re: [PATCH v5 10/12] x86/xen: Bypass intr mode setup in enlighten_pv system

Hi Thomas, At 07/03/2017 03:18 AM, Thomas Gleixner wrote: On Fri, 30 Jun 2017, Dou Liyang wrote: xen_smp_ops overwrites smp_prepare_cpus to xen_pv_smp_prepare_cpus which initializes interrupt itself. Touching the intr_mode_init causes unexpected results on the system. Bypass it in

Re: [PATCH v5 10/12] x86/xen: Bypass intr mode setup in enlighten_pv system

Hi Thomas, At 07/03/2017 03:18 AM, Thomas Gleixner wrote: On Fri, 30 Jun 2017, Dou Liyang wrote: xen_smp_ops overwrites smp_prepare_cpus to xen_pv_smp_prepare_cpus which initializes interrupt itself. Touching the intr_mode_init causes unexpected results on the system. Bypass it in

Re: [PATCH v2 2/4] selftests/ftrace: Add a test to probe module functions

On Mon, 3 Jul 2017 12:27:33 +0900 Masami Hiramatsu wrote: > On Thu, 29 Jun 2017 19:05:37 +0530 > "Naveen N. Rao" wrote: > > > Add a kprobes test to ensure that we are able to add a probe on a > > module function using 'p :' format, without

Re: [PATCH v2 2/4] selftests/ftrace: Add a test to probe module functions

On Mon, 3 Jul 2017 12:27:33 +0900 Masami Hiramatsu wrote: > On Thu, 29 Jun 2017 19:05:37 +0530 > "Naveen N. Rao" wrote: > > > Add a kprobes test to ensure that we are able to add a probe on a > > module function using 'p :' format, without having to > > specify a probe name. > > > >

RE: [PATCH 1/9] clk: clk-divider: add CLK_DIVIDER_ZERO_GATE clk support

> -Original Message- > From: Stephen Boyd [mailto:sb...@codeaurora.org] > Sent: Saturday, July 01, 2017 8:56 AM > To: Dong Aisheng > Cc: A.s. Dong; linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; > linux-arm-ker...@lists.infradead.org; mturque...@baylibre.com; >

RE: [PATCH 1/9] clk: clk-divider: add CLK_DIVIDER_ZERO_GATE clk support

> -Original Message- > From: Stephen Boyd [mailto:sb...@codeaurora.org] > Sent: Saturday, July 01, 2017 8:56 AM > To: Dong Aisheng > Cc: A.s. Dong; linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; > linux-arm-ker...@lists.infradead.org; mturque...@baylibre.com; >

linux-next: build failure after merge of the spi tree

Hi Mark, After merging the spi tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/spi/spi-imx.c: In function 'spi_imx_setupxfer': drivers/spi/spi-imx.c:1007:16: error: 'config' undeclared (first use in this function) mask = (1 << config.bpw) - 1; ^

linux-next: build failure after merge of the spi tree

Hi Mark, After merging the spi tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/spi/spi-imx.c: In function 'spi_imx_setupxfer': drivers/spi/spi-imx.c:1007:16: error: 'config' undeclared (first use in this function) mask = (1 << config.bpw) - 1; ^

Re: [PATCH v2 4/4] selftests/ftrace: Add a testcase for kprobe event naming

On Thu, 29 Jun 2017 19:05:39 +0530 "Naveen N. Rao" wrote: > From: Masami Hiramatsu > > Add a testcase for kprobe event naming. This testcase > checks whether the kprobe events can automatically ganerate > its event name on normal function

Re: [PATCH v2 4/4] selftests/ftrace: Add a testcase for kprobe event naming

On Thu, 29 Jun 2017 19:05:39 +0530 "Naveen N. Rao" wrote: > From: Masami Hiramatsu > > Add a testcase for kprobe event naming. This testcase > checks whether the kprobe events can automatically ganerate > its event name on normal function and dot-suffixed function. > Also it checks whether the

Re: [PATCH v2 3/4] selftests/ftrace: Update multiple kprobes test for powerpc

On Thu, 29 Jun 2017 19:05:38 +0530 "Naveen N. Rao" wrote: > KPROBES_ON_FTRACE is only available on powerpc64le. Update comment to > clarify this. > > Also, we should use an offset of 8 to ensure that the probe does not > fall on ftrace location. The current

Re: [PATCH v2 3/4] selftests/ftrace: Update multiple kprobes test for powerpc

On Thu, 29 Jun 2017 19:05:38 +0530 "Naveen N. Rao" wrote: > KPROBES_ON_FTRACE is only available on powerpc64le. Update comment to > clarify this. > > Also, we should use an offset of 8 to ensure that the probe does not > fall on ftrace location. The current offset of 4 will fall before the >

Re: [PATCH v5 09/12] x86/init: add intr_mode_init to x86_init_ops

Hi Thomas, At 07/03/2017 03:16 AM, Thomas Gleixner wrote: On Fri, 30 Jun 2017, Dou Liyang wrote: Add an unconditional x86_init_ops function which defaults to the standard function and can be overridden by the early platform code. That changelog describes WHAT the patch does, but not WHY.

Re: [PATCH v5 09/12] x86/init: add intr_mode_init to x86_init_ops

Hi Thomas, At 07/03/2017 03:16 AM, Thomas Gleixner wrote: On Fri, 30 Jun 2017, Dou Liyang wrote: Add an unconditional x86_init_ops function which defaults to the standard function and can be overridden by the early platform code. That changelog describes WHAT the patch does, but not WHY.

Re: [PATCH v2 2/4] selftests/ftrace: Add a test to probe module functions

On Thu, 29 Jun 2017 19:05:37 +0530 "Naveen N. Rao" wrote: > Add a kprobes test to ensure that we are able to add a probe on a > module function using 'p :' format, without having to > specify a probe name. > > Suggested-by: Masami Hiramatsu

Re: [PATCH v2 2/4] selftests/ftrace: Add a test to probe module functions

On Thu, 29 Jun 2017 19:05:37 +0530 "Naveen N. Rao" wrote: > Add a kprobes test to ensure that we are able to add a probe on a > module function using 'p :' format, without having to > specify a probe name. > > Suggested-by: Masami Hiramatsu > Acked-by: Masami Hiramatsu > Signed-off-by: Naveen

Re: [PATCH v5 08/12] x86/ioapic: Refactor the delay logic in timer_irq_works()

Hi Thomas, At 07/03/2017 03:15 AM, Thomas Gleixner wrote: On Fri, 30 Jun 2017, Dou Liyang wrote: +static void __init delay_with_tsc(void) +{ + unsigned long long start, now; + unsigned long ticks = jiffies; Please make that unsigned long end = jiffies + 4; ticks really

Re: [PATCH v5 08/12] x86/ioapic: Refactor the delay logic in timer_irq_works()

Hi Thomas, At 07/03/2017 03:15 AM, Thomas Gleixner wrote: On Fri, 30 Jun 2017, Dou Liyang wrote: +static void __init delay_with_tsc(void) +{ + unsigned long long start, now; + unsigned long ticks = jiffies; Please make that unsigned long end = jiffies + 4; ticks really

Re: [RFC PATCH 2/2] kprobes: Allow specifying names for certain blacklisted address ranges

On Thu, 29 Jun 2017 19:38:38 +0530 "Naveen N. Rao" wrote: > This allows us to provide meaningful names for certain address ranges > that are blacklisted such as those with __kprobes annotation, kernel > entry text, and so on. For such ranges, using the

Re: [RFC PATCH 2/2] kprobes: Allow specifying names for certain blacklisted address ranges

On Thu, 29 Jun 2017 19:38:38 +0530 "Naveen N. Rao" wrote: > This allows us to provide meaningful names for certain address ranges > that are blacklisted such as those with __kprobes annotation, kernel > entry text, and so on. For such ranges, using the symbol/function name > at the start of the

Re: [RFC PATCH 1/2] kprobes: Simplify kprobe blacklist management

Hi Naveen, On Thu, 29 Jun 2017 19:38:37 +0530 "Naveen N. Rao" wrote: > Currently, the kprobe blacklist file in debugfs (usually > /sys/kernel/debug/kprobes/blacklist) does not capture all address > ranges that are blacklisted. For instance, functions annotated

Re: [RFC PATCH 1/2] kprobes: Simplify kprobe blacklist management

Hi Naveen, On Thu, 29 Jun 2017 19:38:37 +0530 "Naveen N. Rao" wrote: > Currently, the kprobe blacklist file in debugfs (usually > /sys/kernel/debug/kprobes/blacklist) does not capture all address > ranges that are blacklisted. For instance, functions annotated with > __kprobes (between

RE: [PATCH 4/9] clk: imx: add pllv4 support

> -Original Message- > From: Stephen Boyd [mailto:sb...@codeaurora.org] > Sent: Saturday, July 01, 2017 8:37 AM > To: Dong Aisheng > Cc: A.s. Dong; linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; > linux-arm-ker...@lists.infradead.org; mturque...@baylibre.com; >

RE: [PATCH 4/9] clk: imx: add pllv4 support

> -Original Message- > From: Stephen Boyd [mailto:sb...@codeaurora.org] > Sent: Saturday, July 01, 2017 8:37 AM > To: Dong Aisheng > Cc: A.s. Dong; linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; > linux-arm-ker...@lists.infradead.org; mturque...@baylibre.com; >

Re: linux-next: build failure after merge of the sound-asoc tree

Hi all, On Fri, 30 Jun 2017 11:51:35 +1000 Stephen Rothwell wrote: > > On Thu, 29 Jun 2017 02:01:16 + Bard Liao wrote: > > > > > -Original Message- > > > From: Stephen Rothwell [mailto:s...@canb.auug.org.au] > > > Sent: Thursday, June

Re: linux-next: build failure after merge of the sound-asoc tree

Hi all, On Fri, 30 Jun 2017 11:51:35 +1000 Stephen Rothwell wrote: > > On Thu, 29 Jun 2017 02:01:16 + Bard Liao wrote: > > > > > -Original Message- > > > From: Stephen Rothwell [mailto:s...@canb.auug.org.au] > > > Sent: Thursday, June 29, 2017 9:54 AM > > > To: Mark Brown; Liam

RE: [PATCH 9/9] clk: imx: add imx7ulp clk driver

> -Original Message- > From: Stephen Boyd [mailto:sb...@codeaurora.org] > Sent: Saturday, July 01, 2017 8:35 AM > To: A.s. Dong > Cc: Dong Aisheng; linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; > linux-arm-ker...@lists.infradead.org; mturque...@baylibre.com; >

RE: [PATCH 9/9] clk: imx: add imx7ulp clk driver

> -Original Message- > From: Stephen Boyd [mailto:sb...@codeaurora.org] > Sent: Saturday, July 01, 2017 8:35 AM > To: A.s. Dong > Cc: Dong Aisheng; linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; > linux-arm-ker...@lists.infradead.org; mturque...@baylibre.com; >

Re: linux-next: build failure after merge of the tip tree

Hi all, With the merge window opening, just a reminder that this semantic conflict still exists. On Wed, 28 Jun 2017 13:43:10 +1000 Stephen Rothwell wrote: > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > >

Re: linux-next: build failure after merge of the tip tree

Hi all, With the merge window opening, just a reminder that this semantic conflict still exists. On Wed, 28 Jun 2017 13:43:10 +1000 Stephen Rothwell wrote: > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > net/bluetooth/hidp/core.c:1241:39:

Re: linux-next: manual merge of the jc_docs tree with the kbuild tree

Hi all, With the merge window opening, just a reminder that this conflict still exists. On Mon, 26 Jun 2017 11:13:31 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the jc_docs tree got a conflict in: > > scripts/kernel-doc-xml-ref > > between commit: >

Re: linux-next: manual merge of the jc_docs tree with the kbuild tree

Hi all, With the merge window opening, just a reminder that this conflict still exists. On Mon, 26 Jun 2017 11:13:31 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the jc_docs tree got a conflict in: > > scripts/kernel-doc-xml-ref > > between commit: > > cb77f0d623ff

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

Hi all, With the merge window opening, just a reminder that this conflict still exists. On Mon, 26 Jun 2017 10:51:54 +1000 Stephen Rothwell wrote: > > Hi Bjorn, > > Today's linux-next merge of the pci tree got a conflict in: > > drivers/gpu/drm/radeon/radeon_device.c

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

Hi all, With the merge window opening, just a reminder that this conflict still exists. On Mon, 26 Jun 2017 10:51:54 +1000 Stephen Rothwell wrote: > > Hi Bjorn, > > Today's linux-next merge of the pci tree got a conflict in: > > drivers/gpu/drm/radeon/radeon_device.c > > between commit: >

Re: linux-next: manual merge of the sound-asoc tree with the pm tree

Hi all, [cc-ing the sound tree maintainer] With the merge window opening, just a reminder that this conflict still exists. On Fri, 23 Jun 2017 12:25:34 +1000 Stephen Rothwell wrote: > > Hi all, > > Today's linux-next merge of the sound-asoc tree got a conflict in: > >

Re: linux-next: manual merge of the sound-asoc tree with the pm tree

Hi all, [cc-ing the sound tree maintainer] With the merge window opening, just a reminder that this conflict still exists. On Fri, 23 Jun 2017 12:25:34 +1000 Stephen Rothwell wrote: > > Hi all, > > Today's linux-next merge of the sound-asoc tree got a conflict in: > > drivers/of/base.c >

[lkp-robot] [net] 0b7266402f: kernel_BUG_at_mm/slab_common.c

FYI, we noticed the following commit: commit: 0b7266402fc6ebfa0af7488f34dc113696511fdd ("net: define usercopy region in struct proto slab cache") https://git.kernel.org/cgit/linux/kernel/git/kees/linux.git kspp/usercopy-whitelist/20170619 in testcase: trinity with following parameters:

[lkp-robot] [net] 0b7266402f: kernel_BUG_at_mm/slab_common.c

FYI, we noticed the following commit: commit: 0b7266402fc6ebfa0af7488f34dc113696511fdd ("net: define usercopy region in struct proto slab cache") https://git.kernel.org/cgit/linux/kernel/git/kees/linux.git kspp/usercopy-whitelist/20170619 in testcase: trinity with following parameters:

Re: [PATCH v5 07/12] x86/apic: Unify interrupt mode setup for UP system

Hi Thomas, At 07/03/2017 02:19 AM, Thomas Gleixner wrote: On Fri, 30 Jun 2017, Dou Liyang wrote: static inline int apic_force_enable(unsigned long addr) diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c index 0601054..9bf7e95 100644 --- a/arch/x86/kernel/apic/apic.c +++

Re: [PATCH v5 05/12] x86/apic: Unify interrupt mode setup for SMP-capable system

Hi Thomas, At 07/03/2017 02:07 AM, Thomas Gleixner wrote: On Fri, 30 Jun 2017, Dou Liyang wrote: -static int __init apic_intr_mode_select(void) +static int __init apic_intr_mode_select(int *upmode) { /* Check kernel option */ if (disable_apic) { @@ -1206,12 +1208,30 @@ static

Re: [PATCH v5 05/12] x86/apic: Unify interrupt mode setup for SMP-capable system

Hi Thomas, At 07/03/2017 02:07 AM, Thomas Gleixner wrote: On Fri, 30 Jun 2017, Dou Liyang wrote: -static int __init apic_intr_mode_select(void) +static int __init apic_intr_mode_select(int *upmode) { /* Check kernel option */ if (disable_apic) { @@ -1206,12 +1208,30 @@ static

Re: [PATCH v5 07/12] x86/apic: Unify interrupt mode setup for UP system

Hi Thomas, At 07/03/2017 02:19 AM, Thomas Gleixner wrote: On Fri, 30 Jun 2017, Dou Liyang wrote: static inline int apic_force_enable(unsigned long addr) diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c index 0601054..9bf7e95 100644 --- a/arch/x86/kernel/apic/apic.c +++

linux-next: build warning after merge of the sound-asoc tree

Hi all, After merging the sound-asoc tree, today's linux-next build (x86_64 allmodconfig) produced this warning: In file included from sound/soc/intel/skylake/skl-debug.c:23:0: sound/soc/intel/skylake/../common/sst-dsp-priv.h:63:42: warning: 'struct sst_pdata' declared inside parameter list

linux-next: build warning after merge of the sound-asoc tree

Hi all, After merging the sound-asoc tree, today's linux-next build (x86_64 allmodconfig) produced this warning: In file included from sound/soc/intel/skylake/skl-debug.c:23:0: sound/soc/intel/skylake/../common/sst-dsp-priv.h:63:42: warning: 'struct sst_pdata' declared inside parameter list

Re: [PATCH 1/5] [media] rockchip/rga: v4l2 m2m support

On 06/27/2017 11:49 PM, Nicolas Dufresne wrote: Le mardi 27 juin 2017 à 23:11 +0800, Jacob Chen a écrit : Hi Nicolas. 2017-06-26 23:49 GMT+08:00 Nicolas Dufresne : Le lundi 26 juin 2017 à 22:51 +0800, Jacob Chen a écrit : Rockchip RGA is a separate 2D raster graphic

Re: [PATCH 1/5] [media] rockchip/rga: v4l2 m2m support

On 06/27/2017 11:49 PM, Nicolas Dufresne wrote: Le mardi 27 juin 2017 à 23:11 +0800, Jacob Chen a écrit : Hi Nicolas. 2017-06-26 23:49 GMT+08:00 Nicolas Dufresne : Le lundi 26 juin 2017 à 22:51 +0800, Jacob Chen a écrit : Rockchip RGA is a separate 2D raster graphic acceleration unit. It

Re: [PATCH v2] mm/zsmalloc: simplify zs_max_alloc_size handling

Forgot to add Andrew. On Mon, Jul 03, 2017 at 11:13:12AM +0900, Minchan Kim wrote: > On Fri, Jun 30, 2017 at 01:48:59PM +0200, Jerome Marchand wrote: > > Commit 40f9fb8cffc6 ("mm/zsmalloc: support allocating obj with size of > > ZS_MAX_ALLOC_SIZE") fixes a size calculation error that prevented >

Re: [PATCH v2] mm/zsmalloc: simplify zs_max_alloc_size handling

Forgot to add Andrew. On Mon, Jul 03, 2017 at 11:13:12AM +0900, Minchan Kim wrote: > On Fri, Jun 30, 2017 at 01:48:59PM +0200, Jerome Marchand wrote: > > Commit 40f9fb8cffc6 ("mm/zsmalloc: support allocating obj with size of > > ZS_MAX_ALLOC_SIZE") fixes a size calculation error that prevented >

Re: [PATCH v2] mm/zsmalloc: simplify zs_max_alloc_size handling

On Fri, Jun 30, 2017 at 01:48:59PM +0200, Jerome Marchand wrote: > Commit 40f9fb8cffc6 ("mm/zsmalloc: support allocating obj with size of > ZS_MAX_ALLOC_SIZE") fixes a size calculation error that prevented > zsmalloc to allocate an object of the maximal size > (ZS_MAX_ALLOC_SIZE). I think however

Re: [PATCH v2] mm/zsmalloc: simplify zs_max_alloc_size handling

On Fri, Jun 30, 2017 at 01:48:59PM +0200, Jerome Marchand wrote: > Commit 40f9fb8cffc6 ("mm/zsmalloc: support allocating obj with size of > ZS_MAX_ALLOC_SIZE") fixes a size calculation error that prevented > zsmalloc to allocate an object of the maximal size > (ZS_MAX_ALLOC_SIZE). I think however

linux-next: manual merge of the drm tree with the vfs tree

Hi Dave, Today's linux-next merge of the drm tree got a conflict in: drivers/gpu/drm/drm_internal.h between commits: 012c6741c6aa ("switch compat_drm_version() to drm_ioctl_kernel()") 17e3dade62d6 ("switch compat_drm_getunique() to drm_ioctl_kernel()") 9e92662d01d8 ("switch

linux-next: manual merge of the drm tree with the vfs tree

Hi Dave, Today's linux-next merge of the drm tree got a conflict in: drivers/gpu/drm/drm_internal.h between commits: 012c6741c6aa ("switch compat_drm_version() to drm_ioctl_kernel()") 17e3dade62d6 ("switch compat_drm_getunique() to drm_ioctl_kernel()") 9e92662d01d8 ("switch

Re: [PATCH v5 04/12] x86/apic: Move logical APIC ID away from apic_bsp_setup()

Hi, Thomas At 07/03/2017 01:54 AM, Thomas Gleixner wrote: On Fri, 30 Jun 2017, Dou Liyang wrote: /* diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c index 93f0cda..d6721f0 100644 --- a/arch/x86/kernel/smpboot.c +++ b/arch/x86/kernel/smpboot.c @@ -1347,8 +1347,11 @@ void

Re: [PATCH v5 04/12] x86/apic: Move logical APIC ID away from apic_bsp_setup()

Hi, Thomas At 07/03/2017 01:54 AM, Thomas Gleixner wrote: On Fri, 30 Jun 2017, Dou Liyang wrote: /* diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c index 93f0cda..d6721f0 100644 --- a/arch/x86/kernel/smpboot.c +++ b/arch/x86/kernel/smpboot.c @@ -1347,8 +1347,11 @@ void

  1   2   3   4   5   >