Re: [PATCH] [DRM][KMS][MODE][MEDIATEK] Using the function drm_display_mode_to_videomode

Hi, Satendra: I've applied this patch to my branch mediatek-drm-next-4.18, and I've added below modification in this patch to prevent build error, diff --git a/drivers/gpu/drm/mediatek/Kconfig b/drivers/gpu/drm/mediatek/Kconfig index 294de45..119ec0a 100644 --- a/drivers/gpu/drm/mediatek/Kconfig

Re: [PATCH] [DRM][KMS][MODE][MEDIATEK] Using the function drm_display_mode_to_videomode

Hi, Satendra: I've applied this patch to my branch mediatek-drm-next-4.18, and I've added below modification in this patch to prevent build error, diff --git a/drivers/gpu/drm/mediatek/Kconfig b/drivers/gpu/drm/mediatek/Kconfig index 294de45..119ec0a 100644 --- a/drivers/gpu/drm/mediatek/Kconfig

[tip:perf/urgent] perf evsel: Only fall back group read for leader

Commit-ID: 121f325f34caf9a7654ec8a50e20942ed9d6dafc Gitweb: https://git.kernel.org/tip/121f325f34caf9a7654ec8a50e20942ed9d6dafc Author: Kan Liang AuthorDate: Tue, 24 Apr 2018 11:20:12 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Tue,

[tip:perf/urgent] perf evsel: Only fall back group read for leader

Commit-ID: 121f325f34caf9a7654ec8a50e20942ed9d6dafc Gitweb: https://git.kernel.org/tip/121f325f34caf9a7654ec8a50e20942ed9d6dafc Author: Kan Liang AuthorDate: Tue, 24 Apr 2018 11:20:12 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 24 Apr 2018 16:11:59 -0300 perf evsel:

[tip:perf/urgent] perf stat: Print out hint for mixed PMU group error

Commit-ID: 30060eaed769039c6e523b9d159f2b2858fa8907 Gitweb: https://git.kernel.org/tip/30060eaed769039c6e523b9d159f2b2858fa8907 Author: Kan Liang AuthorDate: Tue, 24 Apr 2018 11:20:11 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Tue,

[tip:perf/urgent] perf stat: Print out hint for mixed PMU group error

Commit-ID: 30060eaed769039c6e523b9d159f2b2858fa8907 Gitweb: https://git.kernel.org/tip/30060eaed769039c6e523b9d159f2b2858fa8907 Author: Kan Liang AuthorDate: Tue, 24 Apr 2018 11:20:11 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 24 Apr 2018 16:11:59 -0300 perf stat:

[tip:perf/urgent] perf pmu: Fix core PMU alias list for X86 platform

Commit-ID: 292c34c10249c64a70def442f0d977bf9d466ed7 Gitweb: https://git.kernel.org/tip/292c34c10249c64a70def442f0d977bf9d466ed7 Author: Kan Liang AuthorDate: Tue, 24 Apr 2018 11:20:10 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Tue,

[tip:perf/urgent] perf pmu: Fix core PMU alias list for X86 platform

Commit-ID: 292c34c10249c64a70def442f0d977bf9d466ed7 Gitweb: https://git.kernel.org/tip/292c34c10249c64a70def442f0d977bf9d466ed7 Author: Kan Liang AuthorDate: Tue, 24 Apr 2018 11:20:10 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 24 Apr 2018 16:02:29 -0300 perf pmu: Fix

[tip:perf/urgent] perf record: Fix s390 undefined record__auxtrace_init() return value

Commit-ID: 5d9946c3e5e38e07ab7019db9413a96807a325f2 Gitweb: https://git.kernel.org/tip/5d9946c3e5e38e07ab7019db9413a96807a325f2 Author: Thomas Richter AuthorDate: Mon, 23 Apr 2018 16:29:40 +0200 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/urgent] perf record: Fix s390 undefined record__auxtrace_init() return value

Commit-ID: 5d9946c3e5e38e07ab7019db9413a96807a325f2 Gitweb: https://git.kernel.org/tip/5d9946c3e5e38e07ab7019db9413a96807a325f2 Author: Thomas Richter AuthorDate: Mon, 23 Apr 2018 16:29:40 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr 2018 12:05:02 -0300 perf

[tip:perf/urgent] perf evsel: Disable write_backward for leader sampling group events

Commit-ID: e9add8bac6c69edb4bf391e537faa659b2ed70d2 Gitweb: https://git.kernel.org/tip/e9add8bac6c69edb4bf391e537faa659b2ed70d2 Author: Jiri Olsa AuthorDate: Mon, 23 Apr 2018 11:08:19 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr

[tip:perf/urgent] perf evsel: Disable write_backward for leader sampling group events

Commit-ID: e9add8bac6c69edb4bf391e537faa659b2ed70d2 Gitweb: https://git.kernel.org/tip/e9add8bac6c69edb4bf391e537faa659b2ed70d2 Author: Jiri Olsa AuthorDate: Mon, 23 Apr 2018 11:08:19 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr 2018 11:21:56 -0300 perf evsel:

[tip:perf/urgent] perf mem: Document incorrect and missing options

Commit-ID: 3138a2ef62667b6ac8eb5fb33a9e0b84ec3ab165 Gitweb: https://git.kernel.org/tip/3138a2ef62667b6ac8eb5fb33a9e0b84ec3ab165 Author: Sangwon Hong AuthorDate: Sun, 22 Apr 2018 16:29:06 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23

[tip:perf/urgent] perf mem: Document incorrect and missing options

Commit-ID: 3138a2ef62667b6ac8eb5fb33a9e0b84ec3ab165 Gitweb: https://git.kernel.org/tip/3138a2ef62667b6ac8eb5fb33a9e0b84ec3ab165 Author: Sangwon Hong AuthorDate: Sun, 22 Apr 2018 16:29:06 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr 2018 11:59:18 -0300 perf mem:

[PATCH 4/4] tty: n_gsm: Fix the test for if DLCI0 is open

Logically, if gsm->dlci[0] is NULL then it's not open. Also if it's NULL then we would Oops when we do dlci_get(gsm->dlci[0]); at the end of the function. Reported-by: Sun Peng Signed-off-by: Dan Carpenter diff --git a/drivers/tty/n_gsm.c

[tip:perf/urgent] perf pmu: Fix pmu events parsing rule

Commit-ID: 9a4a931ce847f4aaa12edf11b2e050e18bf45910 Gitweb: https://git.kernel.org/tip/9a4a931ce847f4aaa12edf11b2e050e18bf45910 Author: Jiri Olsa AuthorDate: Mon, 23 Apr 2018 11:08:18 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr

[PATCH 4/4] tty: n_gsm: Fix the test for if DLCI0 is open

Logically, if gsm->dlci[0] is NULL then it's not open. Also if it's NULL then we would Oops when we do dlci_get(gsm->dlci[0]); at the end of the function. Reported-by: Sun Peng Signed-off-by: Dan Carpenter diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c index 44e9c5e3dbc1..660153538ca7

[tip:perf/urgent] perf pmu: Fix pmu events parsing rule

Commit-ID: 9a4a931ce847f4aaa12edf11b2e050e18bf45910 Gitweb: https://git.kernel.org/tip/9a4a931ce847f4aaa12edf11b2e050e18bf45910 Author: Jiri Olsa AuthorDate: Mon, 23 Apr 2018 11:08:18 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr 2018 11:17:27 -0300 perf pmu: Fix

[tip:perf/urgent] perf stat: Keep the / modifier separator in fallback

Commit-ID: 129193bb0c43d42f1c397c175346e3e0dba5a578 Gitweb: https://git.kernel.org/tip/129193bb0c43d42f1c397c175346e3e0dba5a578 Author: Jiri Olsa AuthorDate: Mon, 23 Apr 2018 11:08:17 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr

[PATCH 3/4] tty: n_gsm: Remove an unused lock

We don't use this spin_lock so we can remove the dead code. Signed-off-by: Dan Carpenter diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c index 1f2fd9e76fe0..44e9c5e3dbc1 100644 --- a/drivers/tty/n_gsm.c +++ b/drivers/tty/n_gsm.c @@ -177,7 +177,6 @@ struct

[tip:perf/urgent] perf stat: Keep the / modifier separator in fallback

Commit-ID: 129193bb0c43d42f1c397c175346e3e0dba5a578 Gitweb: https://git.kernel.org/tip/129193bb0c43d42f1c397c175346e3e0dba5a578 Author: Jiri Olsa AuthorDate: Mon, 23 Apr 2018 11:08:17 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr 2018 11:14:10 -0300 perf stat: Keep

[PATCH 3/4] tty: n_gsm: Remove an unused lock

We don't use this spin_lock so we can remove the dead code. Signed-off-by: Dan Carpenter diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c index 1f2fd9e76fe0..44e9c5e3dbc1 100644 --- a/drivers/tty/n_gsm.c +++ b/drivers/tty/n_gsm.c @@ -177,7 +177,6 @@ struct gsm_control { struct gsm_mux

[PATCH 2/4] tty: n_gsm: Prevent a potential use after free

We're freeing the gsm->dlci[] array elements but leaving the freed pointers hanging around. My concern here is if we use the ioctl to change the config, it triggers a restart in gsmld_config(). In that case, we would only reset the first ->dlci[0] element and not the others so it does look to me

[PATCH 2/4] tty: n_gsm: Prevent a potential use after free

We're freeing the gsm->dlci[] array elements but leaving the freed pointers hanging around. My concern here is if we use the ioctl to change the config, it triggers a restart in gsmld_config(). In that case, we would only reset the first ->dlci[0] element and not the others so it does look to me

[PATCH 1/4] tty: n_gsm: add some locking around gsm_mux[]

We should take "gsm_mux_lock" when we access gsm_mux[]. Reported-by: Sun Peng Signed-off-by: Dan Carpenter diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c index 3b3e1f6632d7..cc7f68814200 100644 --- a/drivers/tty/n_gsm.c +++

Re: [PATCH 8/9] mtd: nand: qcom: helper function for raw read

On 2018-04-25 18:29, Miquel Raynal wrote: Hi Abhishek, On Wed, 25 Apr 2018 12:02:29 +0530, Abhishek Sahu wrote: On 2018-04-23 12:28, Miquel Raynal wrote: > Hi Abhishek, > > On Mon, 23 Apr 2018 11:58:42 +0530, Abhishek Sahu > wrote: > >> On

[PATCH 1/4] tty: n_gsm: add some locking around gsm_mux[]

We should take "gsm_mux_lock" when we access gsm_mux[]. Reported-by: Sun Peng Signed-off-by: Dan Carpenter diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c index 3b3e1f6632d7..cc7f68814200 100644 --- a/drivers/tty/n_gsm.c +++ b/drivers/tty/n_gsm.c @@ -2898,18 +2898,22 @@ static int

Re: [PATCH 8/9] mtd: nand: qcom: helper function for raw read

On 2018-04-25 18:29, Miquel Raynal wrote: Hi Abhishek, On Wed, 25 Apr 2018 12:02:29 +0530, Abhishek Sahu wrote: On 2018-04-23 12:28, Miquel Raynal wrote: > Hi Abhishek, > > On Mon, 23 Apr 2018 11:58:42 +0530, Abhishek Sahu > wrote: > >> On 2018-04-22 21:49, Miquel Raynal wrote: >> > Hi

[tip:perf/urgent] perf test: Adapt test case record+probe_libc_inet_pton.sh for s390

Commit-ID: b31a8cc1a53dda3a33b6c9c62779869d4d5fc142 Gitweb: https://git.kernel.org/tip/b31a8cc1a53dda3a33b6c9c62779869d4d5fc142 Author: Thomas Richter AuthorDate: Mon, 23 Apr 2018 10:24:28 +0200 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/urgent] perf list: Remove s390 specific strcmp_cpuid_cmp function

Commit-ID: ce04abfbd3ea545a8eb38a8b6a48fb6e7d139dcb Gitweb: https://git.kernel.org/tip/ce04abfbd3ea545a8eb38a8b6a48fb6e7d139dcb Author: Thomas Richter AuthorDate: Mon, 23 Apr 2018 10:17:45 +0200 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/urgent] perf test: Adapt test case record+probe_libc_inet_pton.sh for s390

Commit-ID: b31a8cc1a53dda3a33b6c9c62779869d4d5fc142 Gitweb: https://git.kernel.org/tip/b31a8cc1a53dda3a33b6c9c62779869d4d5fc142 Author: Thomas Richter AuthorDate: Mon, 23 Apr 2018 10:24:28 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr 2018 11:04:37 -0300 perf test:

[tip:perf/urgent] perf list: Remove s390 specific strcmp_cpuid_cmp function

Commit-ID: ce04abfbd3ea545a8eb38a8b6a48fb6e7d139dcb Gitweb: https://git.kernel.org/tip/ce04abfbd3ea545a8eb38a8b6a48fb6e7d139dcb Author: Thomas Richter AuthorDate: Mon, 23 Apr 2018 10:17:45 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr 2018 11:03:13 -0300 perf list:

[tip:perf/urgent] perf machine: Set main kernel end address properly

Commit-ID: ee05d21791db6db954bbb7b79bb18d88b5f6b7ff Gitweb: https://git.kernel.org/tip/ee05d21791db6db954bbb7b79bb18d88b5f6b7ff Author: Namhyung Kim AuthorDate: Mon, 19 Feb 2018 19:05:45 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23

[tip:perf/urgent] perf machine: Set main kernel end address properly

Commit-ID: ee05d21791db6db954bbb7b79bb18d88b5f6b7ff Gitweb: https://git.kernel.org/tip/ee05d21791db6db954bbb7b79bb18d88b5f6b7ff Author: Namhyung Kim AuthorDate: Mon, 19 Feb 2018 19:05:45 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr 2018 10:52:55 -0300 perf

Re: [PATCH] i2c: at91: Read all available bytes at once

Hi Ludovic, Am 25.04.2018 um 17:08 schrieb Ludovic Desroches: Hi David, On Wed, Apr 18, 2018 at 02:40:55PM +0200, David Engraf wrote: With FIFO enabled it is possible to read multiple bytes at once in the interrupt handler as long as RXRDY is set. This may also reduce the number of

Re: [PATCH] i2c: at91: Read all available bytes at once

Hi Ludovic, Am 25.04.2018 um 17:08 schrieb Ludovic Desroches: Hi David, On Wed, Apr 18, 2018 at 02:40:55PM +0200, David Engraf wrote: With FIFO enabled it is possible to read multiple bytes at once in the interrupt handler as long as RXRDY is set. This may also reduce the number of

Re: Linux messages full of `random: get_random_u32 called from`

Hi! > Since Linux 4.17-rcX, Linux spams a lot of `random: get_random_u32 called > from` messages. I believe, this setting should be reverted by default as > otherwise a lot of other messages are not seen. > > Please find my configuration attached. Same here, thinkpad X60: [3.163839]

Re: Linux messages full of `random: get_random_u32 called from`

Hi! > Since Linux 4.17-rcX, Linux spams a lot of `random: get_random_u32 called > from` messages. I believe, this setting should be reverted by default as > otherwise a lot of other messages are not seen. > > Please find my configuration attached. Same here, thinkpad X60: [3.163839]

[PATCH v2] wlcore: sdio: allow pm to handle sdio power

pm_runtime handles sdio power on and power off transitions. An old workaround for trying to control the power explicitly from the driver was in fact causing failures on suspend/resume as the mmc layer already power the module on resume. In case of resume pm_runtime_get sync returns a positive

[PATCH v2] wlcore: sdio: allow pm to handle sdio power

pm_runtime handles sdio power on and power off transitions. An old workaround for trying to control the power explicitly from the driver was in fact causing failures on suspend/resume as the mmc layer already power the module on resume. In case of resume pm_runtime_get sync returns a positive

[PATCH] x86/idt: Simplify the idt_setup_apic_and_irq_gates()

The vectors between FIRST_SYSTEM_VECTOR and NR_VECTORS are special IRQ vectors used by the SMP architecture. But, if X86_LOCAL_APIC=n, it will not be used, and the FIRST_SYSTEM_VECTOR is equal to NR_VECTORS. idt_setup_apic_and_irq_gates() didn't notice that, which make the code a little complex.

[PATCH] x86/idt: Simplify the idt_setup_apic_and_irq_gates()

The vectors between FIRST_SYSTEM_VECTOR and NR_VECTORS are special IRQ vectors used by the SMP architecture. But, if X86_LOCAL_APIC=n, it will not be used, and the FIRST_SYSTEM_VECTOR is equal to NR_VECTORS. idt_setup_apic_and_irq_gates() didn't notice that, which make the code a little complex.

Re: [PATCH 0/3] K2G: mmc: Update mmc dt node to use sdhci-omap

On Wednesday 25 April 2018 11:10 PM, Santosh Shilimkar wrote: > On 4/25/2018 6:27 AM, Kishon Vijay Abraham I wrote: >> Update mmc dt node to use sdhci-omap binding instead of omap_hsmmc >> binding. >> >> I've also updated keystone_defconfig to enable CONFIG_MMC_SDHCI_OMAP. >> Everyone who use a

Re: [PATCH 0/3] K2G: mmc: Update mmc dt node to use sdhci-omap

On Wednesday 25 April 2018 11:10 PM, Santosh Shilimkar wrote: > On 4/25/2018 6:27 AM, Kishon Vijay Abraham I wrote: >> Update mmc dt node to use sdhci-omap binding instead of omap_hsmmc >> binding. >> >> I've also updated keystone_defconfig to enable CONFIG_MMC_SDHCI_OMAP. >> Everyone who use a

Re: [PATCH] net: phy: marvell: clear wol event before setting it

Hi, On 4/19/2018 5:48 PM, Andrew Lunn wrote: On Thu, Apr 19, 2018 at 04:02:32PM +0800, Jisheng Zhang wrote: From: Jingju Hou If WOL event happened once, the LED[2] interrupt pin will not be cleared unless reading the CSISR register. So clear the WOL event before

Re: [PATCH] net: phy: marvell: clear wol event before setting it

Hi, On 4/19/2018 5:48 PM, Andrew Lunn wrote: On Thu, Apr 19, 2018 at 04:02:32PM +0800, Jisheng Zhang wrote: From: Jingju Hou If WOL event happened once, the LED[2] interrupt pin will not be cleared unless reading the CSISR register. So clear the WOL event before enabling it. Signed-off-by:

Re: [PATCH v2] staging: bcm2835-audio: Disconnect and free vchi_instance on module_exit()

Greg deleted your patch already... regards, dan carpenter

Re: [PATCH v2] staging: bcm2835-audio: Disconnect and free vchi_instance on module_exit()

Greg deleted your patch already... regards, dan carpenter

Re: [PATCH v2] input/touchscreen: atmel_mxt_ts: Add correct touchpad button mapping for the Caroline Chromebook.

Hello, On 26/04/2018 00:57:34 CEST, Dmitry Torokhov wrote: > On Wed, Apr 25, 2018 at 03:26:50PM -0700, Dmitry Torokhov wrote: >> On Wed, Apr 25, 2018 at 02:32:58PM +0200, Vittorio Gambaletta (VittGam) >> wrote: >> > This patch adds the correct platform data information for the Caroline >> >

Re: [PATCH v2] input/touchscreen: atmel_mxt_ts: Add correct touchpad button mapping for the Caroline Chromebook.

Hello, On 26/04/2018 00:57:34 CEST, Dmitry Torokhov wrote: > On Wed, Apr 25, 2018 at 03:26:50PM -0700, Dmitry Torokhov wrote: >> On Wed, Apr 25, 2018 at 02:32:58PM +0200, Vittorio Gambaletta (VittGam) >> wrote: >> > This patch adds the correct platform data information for the Caroline >> >

[tip:x86/urgent] x86/vector: Remove the macro VECTOR_OFFSET_START

Commit-ID: e3072805c61167b85a30ceeef606620704db31f7 Gitweb: https://git.kernel.org/tip/e3072805c61167b85a30ceeef606620704db31f7 Author: Dou Liyang AuthorDate: Wed, 25 Apr 2018 10:05:53 +0800 Committer: Ingo Molnar CommitDate: Thu, 26 Apr

[tip:x86/urgent] x86/vector: Remove the macro VECTOR_OFFSET_START

Commit-ID: e3072805c61167b85a30ceeef606620704db31f7 Gitweb: https://git.kernel.org/tip/e3072805c61167b85a30ceeef606620704db31f7 Author: Dou Liyang AuthorDate: Wed, 25 Apr 2018 10:05:53 +0800 Committer: Ingo Molnar CommitDate: Thu, 26 Apr 2018 07:31:17 +0200 x86/vector: Remove the

[tip:x86/urgent] x86/cpufeatures: Enumerate cldemote instruction

Commit-ID: 9124130573950dcfc06b6a59306edfda2fc33ec7 Gitweb: https://git.kernel.org/tip/9124130573950dcfc06b6a59306edfda2fc33ec7 Author: Fenghua Yu AuthorDate: Mon, 23 Apr 2018 11:29:22 -0700 Committer: Ingo Molnar CommitDate: Thu, 26 Apr 2018

Re: issues with suspend on Dell XPS 13 2-in-1

Hi Dennis, On Wed, 2018-04-25 at 22:06 -0500, Dennis Gilmore wrote: > Hi Srinivas, > > Yes I have latest bios, I have version 1.3.1 that was released on > 18th > of  Feb. Can you try these commands and repeat the test? # cd /sys/kernel/debug/pmc_core/ # for i in {0..32}; do echo $i >

[tip:x86/urgent] x86/cpufeatures: Enumerate cldemote instruction

Commit-ID: 9124130573950dcfc06b6a59306edfda2fc33ec7 Gitweb: https://git.kernel.org/tip/9124130573950dcfc06b6a59306edfda2fc33ec7 Author: Fenghua Yu AuthorDate: Mon, 23 Apr 2018 11:29:22 -0700 Committer: Ingo Molnar CommitDate: Thu, 26 Apr 2018 07:31:12 +0200 x86/cpufeatures: Enumerate

Re: issues with suspend on Dell XPS 13 2-in-1

Hi Dennis, On Wed, 2018-04-25 at 22:06 -0500, Dennis Gilmore wrote: > Hi Srinivas, > > Yes I have latest bios, I have version 1.3.1 that was released on > 18th > of  Feb. Can you try these commands and repeat the test? # cd /sys/kernel/debug/pmc_core/ # for i in {0..32}; do echo $i >

Re: [GIT PULL 00/12] perf/urgent fixes

Merge tag 'perf-urgent-for-mingo-4.17-20180420' of > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/urgent > (2018-04-21 09:38:33 +0200) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git > ta

Re: [GIT PULL 00/12] perf/urgent fixes

rf-urgent-for-mingo-4.17-20180420' of > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/urgent > (2018-04-21 09:38:33 +0200) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git > tags/perf-urgent-fo

Re: [PATCH] dt-bindings: staging: remove a couple of ADC bindings

@Thomas: Do you guys use this ? On 25-04-18, 20:57, Rob Herring wrote: > Remove LPC32xx and SPEAr ADC bindings in staging. They have not been > touched since 2012. > > Cc: Roland Stigge > Cc: Stefan Roese > Cc: Jonathan Cameron > Cc: Viresh

Re: [PATCH] dt-bindings: staging: remove a couple of ADC bindings

@Thomas: Do you guys use this ? On 25-04-18, 20:57, Rob Herring wrote: > Remove LPC32xx and SPEAr ADC bindings in staging. They have not been > touched since 2012. > > Cc: Roland Stigge > Cc: Stefan Roese > Cc: Jonathan Cameron > Cc: Viresh Kumar > Signed-off-by: Rob Herring > --- > Move

Re: [PATCH V3] cpufreq: powernv: Fix the hardlockup by synchronus smp_call in timer interrupt

* Shilpa Bhat [2018-04-25 16:29:31]: > gpstate_timer_handler() uses synchronous smp_call to set the pstate > on the requested core. This causes the below hard lockup: > > [c03fe566b320] [c01d5340] smp_call_function_single+0x110/0x180 > (unreliable) >

Re: [PATCH V3] cpufreq: powernv: Fix the hardlockup by synchronus smp_call in timer interrupt

* Shilpa Bhat [2018-04-25 16:29:31]: > gpstate_timer_handler() uses synchronous smp_call to set the pstate > on the requested core. This causes the below hard lockup: > > [c03fe566b320] [c01d5340] smp_call_function_single+0x110/0x180 > (unreliable) > [c03fe566b390]

Re: [PATCH v14 0/9] Address error and recovery for AER and DPC

On 2018-04-23 20:53, Oza Pawandeep wrote: This patch set brings in error handling support for DPC The current implementation of AER and error message broadcasting to the EP driver is tightly coupled and limited to AER service driver. It is important to factor out broadcasting and other link

Re: [PATCH v14 0/9] Address error and recovery for AER and DPC

On 2018-04-23 20:53, Oza Pawandeep wrote: This patch set brings in error handling support for DPC The current implementation of AER and error message broadcasting to the EP driver is tightly coupled and limited to AER service driver. It is important to factor out broadcasting and other link

Re: Moving unmaintained filesystems to staging

On Thu, Apr 26, 2018 at 07:58:52AM +0300, Nikolay Borisov wrote: > > > On 25.04.2018 23:30, David Sterba wrote: > > On Wed, Apr 25, 2018 at 08:46:02AM -0700, Matthew Wilcox wrote: > >> Recently ncpfs got moved to staging. Also recently, we had some fuzzer > >> developers report bugs in hfs,

Re: Moving unmaintained filesystems to staging

On Thu, Apr 26, 2018 at 07:58:52AM +0300, Nikolay Borisov wrote: > > > On 25.04.2018 23:30, David Sterba wrote: > > On Wed, Apr 25, 2018 at 08:46:02AM -0700, Matthew Wilcox wrote: > >> Recently ncpfs got moved to staging. Also recently, we had some fuzzer > >> developers report bugs in hfs,

Re: [PATCH v1 2/7] serdev: add dev_pm_domain_attach|detach()

On Tue, 2018-04-03 at 12:29 +0200, Marcel Holtmann wrote: > Hi Sean, > > > In order to open up the required power gate before any operation can be > > effectively performed over the serial bus between CPU and serdev, it's > > clearly essential to add common attach functions for PM domains to

Re: [PATCH v1 2/7] serdev: add dev_pm_domain_attach|detach()

On Tue, 2018-04-03 at 12:29 +0200, Marcel Holtmann wrote: > Hi Sean, > > > In order to open up the required power gate before any operation can be > > effectively performed over the serial bus between CPU and serdev, it's > > clearly essential to add common attach functions for PM domains to

linux-next: Tree for Apr 26

Hi all, News: There will be no linux-next release tomorrow. Changes since 20180424: The qcom tree gained a build failure so I used the version from next-20180424. The clk-samsung tree gained a build failure so I used the version from next-20180424. The bpf-next tree gained conflicts against

linux-next: Tree for Apr 26

Hi all, News: There will be no linux-next release tomorrow. Changes since 20180424: The qcom tree gained a build failure so I used the version from next-20180424. The clk-samsung tree gained a build failure so I used the version from next-20180424. The bpf-next tree gained conflicts against

Re: [PATCH V3] cpufreq: powernv: Fix the hardlockup by synchronus smp_call in timer interrupt

On 25-04-18, 16:29, Shilpasri G Bhat wrote: > gpstate_timer_handler() uses synchronous smp_call to set the pstate > on the requested core. This causes the below hard lockup: > > [c03fe566b320] [c01d5340] smp_call_function_single+0x110/0x180 > (unreliable) > [c03fe566b390]

Re: [PATCH V3] cpufreq: powernv: Fix the hardlockup by synchronus smp_call in timer interrupt

On 25-04-18, 16:29, Shilpasri G Bhat wrote: > gpstate_timer_handler() uses synchronous smp_call to set the pstate > on the requested core. This causes the below hard lockup: > > [c03fe566b320] [c01d5340] smp_call_function_single+0x110/0x180 > (unreliable) > [c03fe566b390]

Re: [RFC 05/10] i2c: s3c2410: Remove support for Exynos5440

Hi Krzysztof, On 25.04.2018 05:32, Krzysztof Kozlowski wrote: The Exynos5440 is not actively developed, there are no development boards available and probably there are no real products with it. Remove wide-tree support for Exynos5440. Signed-off-by: Krzysztof Kozlowski

Re: [RFC 05/10] i2c: s3c2410: Remove support for Exynos5440

Hi Krzysztof, On 25.04.2018 05:32, Krzysztof Kozlowski wrote: The Exynos5440 is not actively developed, there are no development boards available and probably there are no real products with it. Remove wide-tree support for Exynos5440. Signed-off-by: Krzysztof Kozlowski looks good,

Re: Linux messages full of `random: get_random_u32 called from`

> Thanks for the report! > > I assume since you're upgrading your own kernel, you must not be > running Chrome OS on your Acer CB3-431 Chromebook (Edgar). Are you > running Chromium --- or some Linux distribution on it? > > Thanks, > > - Ted Correct, I'm

Re: Linux messages full of `random: get_random_u32 called from`

> Thanks for the report! > > I assume since you're upgrading your own kernel, you must not be > running Chrome OS on your Acer CB3-431 Chromebook (Edgar). Are you > running Chromium --- or some Linux distribution on it? > > Thanks, > > - Ted Correct, I'm

Re: Linux messages full of `random: get_random_u32 called from`

On Wed, Apr 25, 2018 at 09:11:08PM -0700, Sultan Alsawaf wrote: > I noticed "systems without sufficient boot randomness" and would like to add > to this. > > With the changes to /dev/random going from 4.16.3 to 4.16.4, my low-spec > Chromebook does not reach > the login screen upon boot (it

Re: Linux messages full of `random: get_random_u32 called from`

On Wed, Apr 25, 2018 at 09:11:08PM -0700, Sultan Alsawaf wrote: > I noticed "systems without sufficient boot randomness" and would like to add > to this. > > With the changes to /dev/random going from 4.16.3 to 4.16.4, my low-spec > Chromebook does not reach > the login screen upon boot (it

Re: Moving unmaintained filesystems to staging

On 25.04.2018 23:30, David Sterba wrote: > On Wed, Apr 25, 2018 at 08:46:02AM -0700, Matthew Wilcox wrote: >> Recently ncpfs got moved to staging. Also recently, we had some fuzzer >> developers report bugs in hfs, which they deem a security hole because >> Ubuntu attempts to automount an

Re: Moving unmaintained filesystems to staging

On 25.04.2018 23:30, David Sterba wrote: > On Wed, Apr 25, 2018 at 08:46:02AM -0700, Matthew Wilcox wrote: >> Recently ncpfs got moved to staging. Also recently, we had some fuzzer >> developers report bugs in hfs, which they deem a security hole because >> Ubuntu attempts to automount an

Re: [Bug 199473] New: pcieport does not scan devices behind PEX switch, while resources are allocated

lspci -vv loaded in bugzilla. I referred to a pci port nr as the nr in an expansion slot On 25-04-18 19:05, Bjorn Helgaas wrote: [Please retain the mailing list cc when replying] On Wed, Apr 25, 2018 at 3:28 AM Janpieter Sollie wrote: Hi Bjorn, I'm at work now,

Re: [Bug 199473] New: pcieport does not scan devices behind PEX switch, while resources are allocated

lspci -vv loaded in bugzilla. I referred to a pci port nr as the nr in an expansion slot On 25-04-18 19:05, Bjorn Helgaas wrote: [Please retain the mailing list cc when replying] On Wed, Apr 25, 2018 at 3:28 AM Janpieter Sollie wrote: Hi Bjorn, I'm at work now, but I saw your mail contained

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

Hi Evan, On Thu, 26 Apr 2018 03:39:25 + Evan Green wrote: > > Guenter and I had a fix for compile test here, which had failures that > looked similar: > > https://lkml.org/lkml/2018/4/18/752 That looks like it could very well be the problem/solution. > I was hoping

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

Hi Evan, On Thu, 26 Apr 2018 03:39:25 + Evan Green wrote: > > Guenter and I had a fix for compile test here, which had failures that > looked similar: > > https://lkml.org/lkml/2018/4/18/752 That looks like it could very well be the problem/solution. > I was hoping to verify myself

Unable to handle kernel paging request in snd_seq_oss_readq_puts

We report the crash: unable to handle kernel paging request in snd_seq_oss_readq_puts This crash has been found in v4.16 using RaceFuzzer (a modified version of Syzkaller), which we describe more at the end of this report. Our analysis shows that the race occurs when invoking two syscalls

Unable to handle kernel paging request in snd_seq_oss_readq_puts

We report the crash: unable to handle kernel paging request in snd_seq_oss_readq_puts This crash has been found in v4.16 using RaceFuzzer (a modified version of Syzkaller), which we describe more at the end of this report. Our analysis shows that the race occurs when invoking two syscalls

[PATCH] iommu/io-pgtable-arm: Use for_each_set_bit to simplify code

We can use for_each_set_bit() to simplify code slightly in the ARM io-pgtable self tests while unmapping. Signed-off-by: YueHaibing --- drivers/iommu/io-pgtable-arm-v7s.c | 5 + drivers/iommu/io-pgtable-arm.c | 5 + 2 files changed, 2 insertions(+), 8

Re: [RFC 01/10] ARM: dts: exynos: Remove Exynos5440

Hi Krzysztof, On 25.04.2018 05:32, Krzysztof Kozlowski wrote: The Exynos5440 (quad-core A15 with GMAC, PCIe, SATA) was targeting server platforms but it did not make it to the market really. There are no development boards with it and probably there are no real products neither. The

[PATCH] iommu/io-pgtable-arm: Use for_each_set_bit to simplify code

We can use for_each_set_bit() to simplify code slightly in the ARM io-pgtable self tests while unmapping. Signed-off-by: YueHaibing --- drivers/iommu/io-pgtable-arm-v7s.c | 5 + drivers/iommu/io-pgtable-arm.c | 5 + 2 files changed, 2 insertions(+), 8 deletions(-) diff --git

Re: [RFC 01/10] ARM: dts: exynos: Remove Exynos5440

Hi Krzysztof, On 25.04.2018 05:32, Krzysztof Kozlowski wrote: The Exynos5440 (quad-core A15 with GMAC, PCIe, SATA) was targeting server platforms but it did not make it to the market really. There are no development boards with it and probably there are no real products neither. The

[PATCH] md: fix two problems with setting the "re-add" device state.

If "re-add" is written to the "state" file for a device which is faulty, this has an effect similar to removing and re-adding the device. It should take up the same slot in the array that it previously had, and an accelerated (e.g. bitmap-based) rebuild should happen. The slot that "it

[PATCH] md: fix two problems with setting the "re-add" device state.

If "re-add" is written to the "state" file for a device which is faulty, this has an effect similar to removing and re-adding the device. It should take up the same slot in the array that it previously had, and an accelerated (e.g. bitmap-based) rebuild should happen. The slot that "it

Re: [RFC 08/10] spi: s3c64xx: samsung: Remove support for Exynos5440

Hi Krzysztof, On 25.04.2018 05:32, Krzysztof Kozlowski wrote: The Exynos5440 is not actively developed, there are no development boards available and probably there are no real products with it. Remove wide-tree support for Exynos5440. Signed-off-by: Krzysztof Kozlowski

Re: [RFC 08/10] spi: s3c64xx: samsung: Remove support for Exynos5440

Hi Krzysztof, On 25.04.2018 05:32, Krzysztof Kozlowski wrote: The Exynos5440 is not actively developed, there are no development boards available and probably there are no real products with it. Remove wide-tree support for Exynos5440. Signed-off-by: Krzysztof Kozlowski Reviewed-by: Andi

Re: [PATCH 05/11] platform: use a dedicated list_head for early devices

Hi Bartosz, I love your patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.17-rc2] [cannot apply to next-20180424] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 05/11] platform: use a dedicated list_head for early devices

Hi Bartosz, I love your patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.17-rc2] [cannot apply to next-20180424] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: Linux messages full of `random: get_random_u32 called from`

I noticed "systems without sufficient boot randomness" and would like to add to this. With the changes to /dev/random going from 4.16.3 to 4.16.4, my low-spec Chromebook does not reach the login screen upon boot (it stays stuck on a black screen) until I provide a source of entropy to the

Re: Linux messages full of `random: get_random_u32 called from`

I noticed "systems without sufficient boot randomness" and would like to add to this. With the changes to /dev/random going from 4.16.3 to 4.16.4, my low-spec Chromebook does not reach the login screen upon boot (it stays stuck on a black screen) until I provide a source of entropy to the

Re: [PATCH v1] kthread/smpboot: Serialize kthread parking against wakeup

On 4/26/2018 1:39 AM, Peter Zijlstra wrote: On Wed, Apr 25, 2018 at 02:03:19PM +0530, Gaurav Kohli wrote: diff --git a/kernel/smpboot.c b/kernel/smpboot.c index 5043e74..c5c5184 100644 --- a/kernel/smpboot.c +++ b/kernel/smpboot.c @@ -122,7 +122,45 @@ static int smpboot_thread_fn(void *data)

Re: [PATCH v1] kthread/smpboot: Serialize kthread parking against wakeup

On 4/26/2018 1:39 AM, Peter Zijlstra wrote: On Wed, Apr 25, 2018 at 02:03:19PM +0530, Gaurav Kohli wrote: diff --git a/kernel/smpboot.c b/kernel/smpboot.c index 5043e74..c5c5184 100644 --- a/kernel/smpboot.c +++ b/kernel/smpboot.c @@ -122,7 +122,45 @@ static int smpboot_thread_fn(void *data)

  1   2   3   4   5   6   7   8   9   10   >