Re: [PATCH v4 2/7] phy: qcom-qmp: Enable pipe_clk before PHY initialization

Hi, On 4/13/2018 2:08 AM, Stephen Boyd wrote: > Quoting Manu Gautam (2018-04-11 08:37:38) >>> I ask because it may be easier to never expose these clks in Linux, hit >>> the enable bits in the branches during clk driver probe, and then act >>> like they never exist because we don't really use

Re: [PATCH] media: cx231xx: Add support for AverMedia DVD EZMaker 7

Hi, On Mar 26, 2018, at 2:06 PM, Kai-Heng Feng wrote: User reports AverMedia DVD EZMaker 7 can be driven by VIDEO_GRABBER. Add the device to the id_table to make it work. *Gentle ping* I am hoping this patch can get merged in v4.17. Kai-Heng BugLink:

[PATCH] IB: make INFINIBAND_ADDR_TRANS configurable

Allow INFINIBAND without INFINIBAND_ADDR_TRANS. Signed-off-by: Greg Thelen Cc: Tarick Bedeir --- drivers/infiniband/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/infiniband/Kconfig b/drivers/infiniband/Kconfig index

Re: [PATCH] f2fs: enlarge block plug coverage

On 2018/4/13 12:07, Jaegeuk Kim wrote: > On 04/13, Chao Yu wrote: >> On 2018/4/13 9:06, Jaegeuk Kim wrote: >>> On 04/10, Chao Yu wrote: On 2018/4/10 12:10, Jaegeuk Kim wrote: > On 04/10, Chao Yu wrote: >> On 2018/4/10 2:02, Jaegeuk Kim wrote: >>> On 04/08, Chao Yu wrote:

Re: [PATCH] Revert "perf machine: Fix paranoid check in machine__set_kernel_mmap()"

On Thu, Apr 12, 2018 at 07:09:54PM -0500, Kim Phillips wrote: > On Thu, 12 Apr 2018 10:57:56 +0900 > Namhyung Kim wrote: > > > On Wed, Apr 11, 2018 at 07:29:40PM -0500, Kim Phillips wrote: > > > On Thu, 12 Apr 2018 08:31:09 +0900 > > > Namhyung Kim

Re: [PATCH 1/7] sched/core: uclamp: add CPU clamp groups accounting

On Mon, Apr 09, 2018 at 05:56:09PM +0100, Patrick Bellasi wrote: > +static inline void uclamp_cpu_get(struct task_struct *p, int cpu, int > clamp_id) > +{ > + struct uclamp_cpu *uc_cpu = _rq(cpu)->uclamp[clamp_id]; > +static inline void uclamp_cpu_put(struct task_struct *p, int cpu, int >

Re: KMSAN: uninit-value in __netif_receive_skb_core

On Fri, Apr 13, 2018 at 10:20 AM, Toshiaki Makita wrote: > On 2018/04/12 17:03, Dmitry Vyukov wrote: >> On Thu, Apr 12, 2018 at 10:01 AM, syzbot >> wrote: >>> Hello, >>> >>> syzbot hit the following crash on

Re: [PATCH v2] block: do not use interruptible wait anywhere

Hi Alan, On Thu, 2018-04-12 at 19:11 +0100, Alan Jenkins wrote: > # dd if=/dev/sda of=/dev/null iflag=direct & \ > while killall -SIGUSR1 dd; do sleep 0.1; done & \ > echo mem > /sys/power/state ; \ > sleep 5; killall dd # stop after 5 seconds Can you please also add a regression test to

Re: [PATCH 1/7] sched/core: uclamp: add CPU clamp groups accounting

On Mon, Apr 09, 2018 at 05:56:09PM +0100, Patrick Bellasi wrote: > +static inline void uclamp_task_update(struct rq *rq, struct task_struct *p) > +{ > + int cpu = cpu_of(rq); > + int clamp_id; > + > + /* The idle task does not affect CPU's clamps */ > + if (unlikely(p->sched_class

Re: [PATCH v3 2/2] vfio: platform: Add generic DT reset support

Hi Geert, Philipp, On 12/04/18 18:02, Geert Uytterhoeven wrote: > Hi Philipp, > > On Thu, Apr 12, 2018 at 4:10 PM, Philipp Zabel wrote: >> On Thu, 2018-04-12 at 15:12 +0200, Geert Uytterhoeven wrote: >>> On Thu, Apr 12, 2018 at 2:36 PM, Sinan Kaya

[PATCH v3] gpio: dwapb: Add support for 1 interrupt per port A GPIO

The DesignWare GPIO IP can be configured for either 1 interrupt or 1 per GPIO in port A, but the driver currently only supports 1 interrupt. See the DesignWare DW_apb_gpio Databook description of the 'GPIO_INTR_IO' parameter. This change allows the driver to work with up to 32 interrupts, it will

[PATCH] MIPS: dts: Boston: Fix PCI bus dtc warnings:

dtc recently (v1.4.4-8-g756ffc4f52f6) added PCI bus checks. Fix the warnings now emitted: arch/mips/boot/dts/img/boston.dtb: Warning (pci_bridge): /pci@1000: missing bus-range for PCI bridge arch/mips/boot/dts/img/boston.dtb: Warning (pci_bridge): /pci@1200: missing bus-range for PCI

Re: [PATCH v3 1/2] vfio: platform: Fix reset module leak in error path

Hi Geert, On 11/04/18 11:15, Geert Uytterhoeven wrote: > If the IOMMU group setup fails, the reset module is not released. > > Fixes: b5add544d677d363 ("vfio, platform: make reset driver a requirement by > default") > Signed-off-by: Geert Uytterhoeven > Reviewed-by:

Re: [PATCH v2] vfio: platform: Make printed error messages more consistent

Hi Geert,On 10/04/18 16:54, Geert Uytterhoeven wrote: > - Capitalize the first word of error messages, > - Unwrap statements that fit on a single line, > - Use "VFIO" instead of "vfio" as the error message prefix. > > Signed-off-by: Geert Uytterhoeven >

Re: [GIT PULL] Thermal management updates for v4.17-rc1

On Friday, April 13, 2018 01:39:05 PM Zhang Rui wrote: > Hi, Eduardo, > > On 四, 2018-04-12 at 21:08 -0700, Eduardo Valentin wrote: > > Hello, > > > > On Thu, Apr 12, 2018 at 09:55:19AM -0700, Linus Torvalds wrote: > > > > > > On Wed, Apr 11, 2018 at 10:08 PM, Zhang Rui > >

Re: [PATCH v3 2/2] vfio: platform: Add generic DT reset support

Hi Eric, On Fri, Apr 13, 2018 at 10:52 AM, Auger Eric wrote: > On 12/04/18 18:02, Geert Uytterhoeven wrote: >> On Thu, Apr 12, 2018 at 4:10 PM, Philipp Zabel >> wrote: >>> On Thu, 2018-04-12 at 15:12 +0200, Geert Uytterhoeven wrote: On Thu,

Re: [PATCH v1 0/2] kexec: Remove "weak" annotations from headers

Hi Bjorn, There are changes I have made to solve 5-level conflict with kexec/kdump and also interface unification task, they will involve x86 64 only changes on these functions, I don't think we need remove them if without any obvious impact or error reported. Thanks Baoquan On 04/13/18 at

Re: [GIT PULL] Thermal management updates for v4.17-rc1

On Friday, April 13, 2018 11:19:40 AM Daniel Lezcano wrote: > On 13/04/2018 11:08, Bartlomiej Zolnierkiewicz wrote: > > On Friday, April 13, 2018 11:00:43 AM Daniel Lezcano wrote: > >> On 13/04/2018 10:55, Bartlomiej Zolnierkiewicz wrote: > >>> On Friday, April 13, 2018 01:39:05 PM Zhang Rui

Re: [PATCH 1/7] sched/core: uclamp: add CPU clamp groups accounting

On Mon, Apr 09, 2018 at 05:56:09PM +0100, Patrick Bellasi wrote: > +static inline void uclamp_cpu_get(struct task_struct *p, int cpu, int > clamp_id) > +{ > + struct uclamp_cpu *uc_cpu = _rq(cpu)->uclamp[clamp_id]; > + int clamp_value; > + int group_id; > + > + /* Get task's

Re: [PATCH v2 1/2] dmaengine: stm32-mdma: align TLEN and buffer length on burst

Hi Robin On 04/11/2018 05:14 PM, Robin Murphy wrote: > On 11/04/18 15:44, Pierre-Yves MORDRET wrote: >> Both buffer Transfer Length (TLEN if any) and transfer size have to be >> aligned on burst size (burst beats*bus width). >> >> Signed-off-by: Pierre-Yves MORDRET >>

Re: [PATCH] mm: vmalloc: Remove double execution of vunmap_page_range

On 04/13/2018 02:46 PM, Chintan Pandya wrote: > Unmap legs do call vunmap_page_range() irrespective of > debug_pagealloc_enabled() is enabled or not. So, remove > redundant check and optional vunmap_page_range() routines. vunmap_page_range() tears down the page table entries and does not really

Re: WARNING: bad unlock balance in xfs_iunlock

On Fri, Apr 6, 2018 at 6:10 PM, Darrick J. Wong wrote: > On Fri, Apr 06, 2018 at 07:38:44AM +1000, Dave Chinner wrote: >> On Thu, Apr 05, 2018 at 08:54:50PM +0200, Dmitry Vyukov wrote: >> > On Tue, Apr 3, 2018 at 6:38 AM, Dave Chinner wrote: >> > >

Re: [GIT PULL] Thermal management updates for v4.17-rc1

On Fri, Apr 13, 2018 at 01:39:05PM +0800, Zhang Rui wrote: > Hi, Eduardo, > > On 四, 2018-04-12 at 21:08 -0700, Eduardo Valentin wrote: > > Hello, > > > > On Thu, Apr 12, 2018 at 09:55:19AM -0700, Linus Torvalds wrote: > > > > > > On Wed, Apr 11, 2018 at 10:08 PM, Zhang Rui

Re: [PATCH] powerpc/sparse: fix plain integer as NULL pointer warning

Hi Mathieu, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on powerpc/next] [also build test WARNING on v4.16 next-20180413] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

Re: [GIT PULL] Thermal management updates for v4.17-rc1

On 13/04/2018 12:41, Bartlomiej Zolnierkiewicz wrote: > On Friday, April 13, 2018 12:30:04 PM Daniel Lezcano wrote: >> On 13/04/2018 11:28, Bartlomiej Zolnierkiewicz wrote: >> >> [ ... ] >> > It is okay to return 0 because this code-path (the default one) will be > never hit by the driver

Re: KMSAN: uninit-value in __netif_receive_skb_core

On 2018/04/12 17:03, Dmitry Vyukov wrote: > On Thu, Apr 12, 2018 at 10:01 AM, syzbot > wrote: >> Hello, >> >> syzbot hit the following crash on https://github.com/google/kmsan.git/master >> commit >> e2ab7e8abba47a2f2698216258e5d8727ae58717

Re: [GIT PULL] Thermal management updates for v4.17-rc1

On 13/04/2018 10:55, Bartlomiej Zolnierkiewicz wrote: > On Friday, April 13, 2018 01:39:05 PM Zhang Rui wrote: >> Hi, Eduardo, >> >> On 四, 2018-04-12 at 21:08 -0700, Eduardo Valentin wrote: >>> Hello, >>> >>> On Thu, Apr 12, 2018 at 09:55:19AM -0700, Linus Torvalds wrote: On Wed, Apr 11,

[PATCH v2] selftests: add headers_install to lib.mk

If the kernel headers aren't installed we can't build all the tests. Add a new make target rule 'khdr' in the file lib.mk to generate the kernel headers and that gets include for every test-dir Makefile that includes lib.mk If the testdir in turn have its own sub-dirs the top_srcdir needs to be

Re: [PATCH] kernel/resource: refine find_next_iomem_res() a little

Hello every one, Someone would like to take a look at this? On Tue, Mar 27, 2018 at 06:46:06AM +0800, Wei Yang wrote: >This patch does several refine for find_next_iomem_res() > > * use first_level_children_only directly > * remove some local variables > * use resrouce_clip() >

Re: [GIT PULL] Thermal management updates for v4.17-rc1

On Friday, April 13, 2018 11:00:43 AM Daniel Lezcano wrote: > On 13/04/2018 10:55, Bartlomiej Zolnierkiewicz wrote: > > On Friday, April 13, 2018 01:39:05 PM Zhang Rui wrote: > >> Hi, Eduardo, > >> > >> On 四, 2018-04-12 at 21:08 -0700, Eduardo Valentin wrote: > >>> Hello, > >>> > >>> On Thu, Apr

Re: [GIT PULL] Thermal management updates for v4.17-rc1

On 13/04/2018 11:08, Bartlomiej Zolnierkiewicz wrote: > On Friday, April 13, 2018 11:00:43 AM Daniel Lezcano wrote: >> On 13/04/2018 10:55, Bartlomiej Zolnierkiewicz wrote: >>> On Friday, April 13, 2018 01:39:05 PM Zhang Rui wrote: Hi, Eduardo, On 四, 2018-04-12 at 21:08 -0700,

Re: [PATCH v2 00/13] kernel/locking: qspinlock improvements

On Wed, Apr 11, 2018 at 07:01:07PM +0100, Will Deacon wrote: > * Spin for a bounded duration while lock is observed in the > pending->locked transition FWIW, I updated my model [1] to include the bounded handover loop and, as expected, it passes the liveness check (well, assuming fairness

Re: [PATCH] vfio: platform: Fix using devices in PM Domains

Hi Geert, On 13/04/18 11:19, Geert Uytterhoeven wrote: > Hi Eric, > > On Fri, Apr 13, 2018 at 11:14 AM, Auger Eric wrote: >> On 11/04/18 11:24, Geert Uytterhoeven wrote: >>> If a device is part of a PM Domain (e.g. power and/or clock domain), its >>> power state is

Re: [PATCH v3 2/2] vfio: platform: Add generic DT reset support

Hi Philipp, On 13/04/18 11:22, Philipp Zabel wrote: [..] > That also means it is impossible to use just one of the devices that > share a reset line for vfio individually, while the other ones are still > in use by the host. Currently the reset line is a shared resource > similar to the iommu for

Re: [PATCH 4/5] dmaengine: sprd: Add Spreadtrum DMA configuration

On Fri, Apr 13, 2018 at 02:41:48PM +0800, Baolin Wang wrote: > On 13 April 2018 at 14:36, Vinod Koul wrote: > > On Fri, Apr 13, 2018 at 02:17:34PM +0800, Baolin Wang wrote: > > > >> > Agreed, users only care about grabbing a channel, setting a descriptor > >> > and > >> >

Re: [PATCH] mm: vmalloc: Remove double execution of vunmap_page_range

On 4/13/2018 3:29 PM, Anshuman Khandual wrote: On 04/13/2018 02:46 PM, Chintan Pandya wrote: Unmap legs do call vunmap_page_range() irrespective of debug_pagealloc_enabled() is enabled or not. So, remove redundant check and optional vunmap_page_range() routines. vunmap_page_range() tears

Re: [GIT PULL] Thermal management updates for v4.17-rc1

On Fri, Apr 13, 2018 at 03:08:03AM -0700, Eduardo Valentin wrote: > On Fri, Apr 13, 2018 at 01:39:05PM +0800, Zhang Rui wrote: > > Hi, Eduardo, > > > > On 四, 2018-04-12 at 21:08 -0700, Eduardo Valentin wrote: > > > Hello, > > > > > > On Thu, Apr 12, 2018 at 09:55:19AM -0700, Linus Torvalds

Re: [GIT PULL] Thermal management updates for v4.17-rc1

On 13/04/2018 11:28, Bartlomiej Zolnierkiewicz wrote: [ ... ] >>> It is okay to return 0 because this code-path (the default one) will be >>> never hit by the driver (probe makes sure of it) - the default case is >>> here is just to silence compilation errors.. >> >> The init function is making

Re: [PATCH] mm: vmalloc: Remove double execution of vunmap_page_range

On 4/13/2018 4:10 PM, Anshuman Khandual wrote: On 04/13/2018 03:47 PM, Chintan Pandya wrote: On 4/13/2018 3:29 PM, Anshuman Khandual wrote: On 04/13/2018 02:46 PM, Chintan Pandya wrote: Unmap legs do call vunmap_page_range() irrespective of debug_pagealloc_enabled() is enabled or not. So,

Applied "ASoC: TSCS42xx: Add CCF support to get sysclk" to the asoc tree

The patch ASoC: TSCS42xx: Add CCF support to get sysclk has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

Applied "ASoC: TSCS42xx: Shorten lines and other cleanup" to the asoc tree

The patch ASoC: TSCS42xx: Shorten lines and other cleanup has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

Re: [PATCH] sound: soc: intel: bxt_da7219_max98357a: Replace GFP_ATOMIC with GFP_KERNEL in broxton_audio_probe

On Fri, Apr 13, 2018 at 06:54:15PM +0800, Jia-Ju Bai wrote: > I looked at previous related patches, and find the subject should be "ASoC: > Intel: " > I will follow it in my future patches. Right, that's it for these thanks. > Do I need to send V2 patches? No, it's OK - I already applied

Applied "ASoC: TSCS42xx: Cleanup private data members" to the asoc tree

The patch ASoC: TSCS42xx: Cleanup private data members has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Re: [PATCH] sound: soc: intel: bxt_da7219_max98357a: Replace GFP_ATOMIC with GFP_KERNEL in broxton_audio_probe

On 2018/4/13 18:41, Mark Brown wrote: On Mon, Apr 09, 2018 at 06:46:21PM +0800, Jia-Ju Bai wrote: broxton_audio_probe() is never called in atomic context. This function is only set as ".probe" in "struct platform_driver". Please submit patches using subject lines reflecting the style for the

Applied "spi: spi-topcliff-pch: Replace GFP_ATOMIC with GFP_KERNEL in pch_spi_handle_dma" to the spi tree

The patch spi: spi-topcliff-pch: Replace GFP_ATOMIC with GFP_KERNEL in pch_spi_handle_dma has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime

Applied "ASoC: intel: skl_rt286: Replace GFP_ATOMIC with GFP_KERNEL in skylake_audio_probe" to the asoc tree

The patch ASoC: intel: skl_rt286: Replace GFP_ATOMIC with GFP_KERNEL in skylake_audio_probe has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually

Applied "ASoC: intel: skl_nau88l25_ssm4567: Replace GFP_ATOMIC with GFP_KERNEL in skylake_audio_probe" to the asoc tree

The patch ASoC: intel: skl_nau88l25_ssm4567: Replace GFP_ATOMIC with GFP_KERNEL in skylake_audio_probe has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree

Applied "ASoC: trace: remove snd_soc_codec" to the asoc tree

The patch ASoC: trace: remove snd_soc_codec has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Re: [PATCH] memcg: Remove memcg_cgroup::id from IDR on mem_cgroup_css_alloc() failure

On Fri 13-04-18 12:35:22, Kirill Tkhai wrote: > On 13.04.2018 11:55, Michal Hocko wrote: > > On Thu 12-04-18 17:52:04, Kirill Tkhai wrote: > > [...] > >> @@ -4471,6 +4477,7 @@ mem_cgroup_css_alloc(struct cgroup_subsys_state > >> *parent_css) > >> > >>return >css; > >> fail: > >> +

Re: [PATCH v1 0/2] kexec: Remove "weak" annotations from headers

Hi Bjorn, in recent patches AKASHI [1] and I [2] made some changes to the declarations you are touching and already removed some of the weak statements. The patches got accepted on linux-next and will (hopefully) be pulled for v4.17. So you should prepare for some merge conflicts. Nevertheless

Re: [PATCH] vfio: platform: Fix using devices in PM Domains

Hi Geert, On 11/04/18 11:24, Geert Uytterhoeven wrote: > If a device is part of a PM Domain (e.g. power and/or clock domain), its > power state is managed using Runtime PM. Without Runtime PM, the device > may not be powered up, causing subtle failures, crashes, or system > lock-ups when the

[PATCH] mm: vmalloc: Remove double execution of vunmap_page_range

Unmap legs do call vunmap_page_range() irrespective of debug_pagealloc_enabled() is enabled or not. So, remove redundant check and optional vunmap_page_range() routines. Signed-off-by: Chintan Pandya --- mm/vmalloc.c | 23 +-- 1 file changed, 1

Re: [PATCH] vfio: platform: Fix using devices in PM Domains

Hi Eric, On Fri, Apr 13, 2018 at 11:14 AM, Auger Eric wrote: > On 11/04/18 11:24, Geert Uytterhoeven wrote: >> If a device is part of a PM Domain (e.g. power and/or clock domain), its >> power state is managed using Runtime PM. Without Runtime PM, the device >> may not be

Re: [PATCH v2 2/2] dmaengine: stm32-mdma: Fix incomplete Hw descriptors allocator

Hi Vinod, On Fri, Apr 13, 2018 at 12:09 PM, Vinod Koul wrote: > On Fri, Apr 13, 2018 at 10:39:48AM +0200, Geert Uytterhoeven wrote: >> On Fri, Apr 13, 2018 at 6:02 AM, Vinod Koul wrote: >> > On Wed, Apr 11, 2018 at 04:44:39PM +0200, Pierre-Yves

Re: [GIT PULL] Thermal management updates for v4.17-rc1

On Friday, April 13, 2018 12:30:04 PM Daniel Lezcano wrote: > On 13/04/2018 11:28, Bartlomiej Zolnierkiewicz wrote: > > [ ... ] > > >>> It is okay to return 0 because this code-path (the default one) will be > >>> never hit by the driver (probe makes sure of it) - the default case is > >>> here

Re: [PATCH] mm: vmalloc: Remove double execution of vunmap_page_range

On 04/13/2018 03:47 PM, Chintan Pandya wrote: > > > On 4/13/2018 3:29 PM, Anshuman Khandual wrote: >> On 04/13/2018 02:46 PM, Chintan Pandya wrote: >>> Unmap legs do call vunmap_page_range() irrespective of >>> debug_pagealloc_enabled() is enabled or not. So, remove >>> redundant check and

[PATCH] configfs: inherit file and directory owners

All entries in configfs are currently owned by root, regardless of context. Instead, this preserves the current ownership, allowing userspace to choose who has permissions to configure the system through any particular configfs subsystem. This means anyone who can create a group will now have the

Re: [PATCH 1/7] sched/core: uclamp: add CPU clamp groups accounting

On 13-Apr 12:22, Peter Zijlstra wrote: > On Fri, Apr 13, 2018 at 10:26:48AM +0200, Peter Zijlstra wrote: > > On Mon, Apr 09, 2018 at 05:56:09PM +0100, Patrick Bellasi wrote: > > > +static inline void uclamp_cpu_get(struct task_struct *p, int cpu, int > > > clamp_id) > > > +{ > > > + struct

Re: [PATCH] thermal/drivers/exynos_tmu: Fix warnings in temp_to_code / code_to_temp

On Friday, April 13, 2018 01:00:09 PM Daniel Lezcano wrote: > The latest driver cleanup introduced a compilation warning > > drivers/thermal/samsung/exynos_tmu.c: In function ‘exynos_get_temp’: > drivers/thermal/samsung/exynos_tmu.c:931:37: warning: ‘temp’ may be used > uninitialized in this

Re: [PATCH v2 1/2] dmaengine: stm32-mdma: align TLEN and buffer length on burst

On 13/04/18 10:45, Pierre Yves MORDRET wrote: Hi Robin On 04/11/2018 05:14 PM, Robin Murphy wrote: On 11/04/18 15:44, Pierre-Yves MORDRET wrote: Both buffer Transfer Length (TLEN if any) and transfer size have to be aligned on burst size (burst beats*bus width). Signed-off-by: Pierre-Yves

Re: [PATCH] mm: vmalloc: Remove double execution of vunmap_page_range

On Fri 13-04-18 16:15:26, Chintan Pandya wrote: > > > On 4/13/2018 4:10 PM, Anshuman Khandual wrote: > > On 04/13/2018 03:47 PM, Chintan Pandya wrote: > > > > > > > > > On 4/13/2018 3:29 PM, Anshuman Khandual wrote: > > > > On 04/13/2018 02:46 PM, Chintan Pandya wrote: > > > > > Unmap legs do

Re: [PATCH 1/7] sched/core: uclamp: add CPU clamp groups accounting

On 13-Apr 11:46, Peter Zijlstra wrote: > On Mon, Apr 09, 2018 at 05:56:09PM +0100, Patrick Bellasi wrote: > > +static inline void uclamp_cpu_get(struct task_struct *p, int cpu, int > > clamp_id) > > +{ > > + struct uclamp_cpu *uc_cpu = _rq(cpu)->uclamp[clamp_id]; > > + int clamp_value; > > +

Re: [PATCH] memcg: Remove memcg_cgroup::id from IDR on mem_cgroup_css_alloc() failure

On Thu 12-04-18 17:52:04, Kirill Tkhai wrote: [...] > @@ -4471,6 +4477,7 @@ mem_cgroup_css_alloc(struct cgroup_subsys_state > *parent_css) > > return >css; > fail: > + mem_cgroup_id_remove(memcg); > mem_cgroup_free(memcg); > return ERR_PTR(-ENOMEM); > } The only path

Re: [PATCH v3 02/12] KVM: arm/arm64: Document KVM_VGIC_V3_ADDR_TYPE_REDIST_REGION

On 13 April 2018 at 09:20, Eric Auger wrote: > We introduce a new KVM_VGIC_V3_ADDR_TYPE_REDIST_REGION attribute in > KVM_DEV_ARM_VGIC_GRP_ADDR group. It allows userspace to provide the > base address and size of a redistributor region > > Compared to

Re: [PATCH] sched: support dynamiQ cluster

On Thu, Apr 12, 2018 at 08:22:11PM +0200, Peter Zijlstra wrote: > On Tue, Apr 10, 2018 at 02:19:50PM +0100, Morten Rasmussen wrote: > > As said above, I see your point about completion time might suffer in > > some cases for low utilization tasks, but I don't see how you can fix > > that

Re: [PATCH v3 2/2] vfio: platform: Add generic DT reset support

Hi Geert, On Thu, 2018-04-12 at 18:02 +0200, Geert Uytterhoeven wrote: > Hi Philipp, > > On Thu, Apr 12, 2018 at 4:10 PM, Philipp Zabel wrote: > > On Thu, 2018-04-12 at 15:12 +0200, Geert Uytterhoeven wrote: > > > On Thu, Apr 12, 2018 at 2:36 PM, Sinan Kaya

Re: [PATCH 1/7] sched/core: uclamp: add CPU clamp groups accounting

On Mon, Apr 09, 2018 at 05:56:09PM +0100, Patrick Bellasi wrote: > +struct uclamp_group { > + /* Utilization clamp value for tasks on this clamp group */ > + int value; > + /* Number of RUNNABLE tasks on this clamp group */ > + int tasks; > +}; > +struct uclamp_cpu { > + /*

Re: [PATCH] memcg: Remove memcg_cgroup::id from IDR on mem_cgroup_css_alloc() failure

On 13.04.2018 11:55, Michal Hocko wrote: > On Thu 12-04-18 17:52:04, Kirill Tkhai wrote: > [...] >> @@ -4471,6 +4477,7 @@ mem_cgroup_css_alloc(struct cgroup_subsys_state >> *parent_css) >> >> return >css; >> fail: >> +mem_cgroup_id_remove(memcg); >> mem_cgroup_free(memcg); >>

Re: [PATCH 1/7] sched/core: uclamp: add CPU clamp groups accounting

On Fri, Apr 13, 2018 at 11:30:05AM +0200, Peter Zijlstra wrote: > On Mon, Apr 09, 2018 at 05:56:09PM +0100, Patrick Bellasi wrote: > > +struct uclamp_group { > > + /* Utilization clamp value for tasks on this clamp group */ > > + int value; > > + /* Number of RUNNABLE tasks on this clamp

[PATCH 0/2] drm: Make it compilable without CONFIG_HDMI and CONFIG_I2C

By enabling the DRM code for virtio-gpu on S390, you currently also get all the code that is enabled by CONFIG_HDMI and CONFIG_I2C automatically. This is quite ugly, since on S390, there is no HDMI and no I2C. Thus it would be great if the DRM code could also be compiled without CONFIG_HDMI and

[PATCH 1/2] drm: Move CONFIG_HDMI-dependent code to a separate file

Selecting CONFIG_HDMI for S390 is inappropriate - there is no real graphic hardware on this architecture. The drm subsystem is only enabled here for using the virtual graphics card "virtio-gpu". So it should be possible to compile the drm subsystem also without CONFIG_DRM. Let's move the related

[PATCH 2/2] drm: Make the DRM code compilable without CONFIG_I2C

Selecting CONFIG_HDMI for S390 is inappropriate - there is no real graphic hardware on this architecture. The drm subsystem is only enabled here for using the virtual graphics card "virtio-gpu". So it should be possible to compile the drm subsystem also without CONFIG_I2C. Tweak the Makefile to

[PATCH] percpu_counter: Remove debug_object_free call twice

During percpu_counter destroy, debug_object_free is calling twice which may create race. So removing once instance of call from debug_percpu_counter_deactivate. Signed-off-by: Gaurav Kohli diff --git a/lib/percpu_counter.c b/lib/percpu_counter.c index c72577e..68ad030

Re: sparc/ppc/arm compat siginfo ABI regressions: sending SIGFPE via kill() returns wrong values in si_pid and si_uid

On Thu, Apr 12, 2018 at 10:22:15AM -0700, Linus Torvalds wrote: > On Thu, Apr 12, 2018 at 10:20 AM, Russell King - ARM Linux > wrote: > > > > This file was created to contain FPE_FIXME, by the "signal/arm: Document > > conflicts with SI_USER and SIGFPE" commit so if we're

[PATCH] x86/tsc: fix 64bit divisor be truncated in calc_hpet_ref

From ba3d2fb699c4d8ee61b05d7e70be48b9c4e22baf Mon Sep 17 00:00:00 2001 From: Xiaoming Gao Date: Fri, 13 Apr 2018 17:05:18 +0800 Subject: [PATCH] x86/tsc: fix 64bit divisor be truncated in calc_hpet_ref the HPET frequency got larger on intel skylake, thus could cause tmp

Re: [PATCH] memory-model: fix cheat sheet typo

On Thu, Apr 12, 2018 at 02:18:36PM -0700, Paul E. McKenney wrote: > On Thu, Apr 12, 2018 at 01:21:55PM +0200, Andrea Parri wrote: > > > > The litmus test that first comes to my mind when I think of cumulativity > > (at least, 'cumulativity' as intended in LKMM) is: > > > >

Re: [PATCH v2 2/2] dmaengine: stm32-mdma: Fix incomplete Hw descriptors allocator

On Fri, Apr 13, 2018 at 10:39:48AM +0200, Geert Uytterhoeven wrote: > Hi Vinod, > > On Fri, Apr 13, 2018 at 6:02 AM, Vinod Koul wrote: > > On Wed, Apr 11, 2018 at 04:44:39PM +0200, Pierre-Yves MORDRET wrote: > > > >> struct stm32_mdma_desc { > >> struct virt_dma_desc

Re: [PATCH 0/2] tools/memory-model: Model 'smp_store_mb()'

On Thu, Apr 12, 2018 at 02:06:27PM -0700, Paul E. McKenney wrote: > On Thu, Apr 12, 2018 at 02:22:48PM +0200, Andrea Parri wrote: > > Hi, > > > > This (tiny) series adds 'smp_store_mb()' to the model (patch 1/2), and > > it fixes a stylistic discrepancy in 'linux-kernel.def (patch 2/2). > > I

Re: [PATCH 1/7] sched/core: uclamp: add CPU clamp groups accounting

On Fri, Apr 13, 2018 at 10:26:48AM +0200, Peter Zijlstra wrote: > On Mon, Apr 09, 2018 at 05:56:09PM +0100, Patrick Bellasi wrote: > > +static inline void uclamp_cpu_get(struct task_struct *p, int cpu, int > > clamp_id) > > +{ > > + struct uclamp_cpu *uc_cpu = _rq(cpu)->uclamp[clamp_id]; > > >

[GIT PULL V2] Thermal SoC management updates for v4.17-rc1

Hello Rui, Please find thermal-soc changes for v4.17-rc1 as follows. - New i.MX7 thermal sensor - Mediatek driver now supports MT7622 SoC - Removal of min max cpu cooling dt property Differences in V2: - Reordered the patches to drop exynos changes for now until we get agreement on the fix on

Re: [GIT PULL] Thermal management updates for v4.17-rc1

On Friday, April 13, 2018 03:08:03 AM Eduardo Valentin wrote: > On Fri, Apr 13, 2018 at 01:39:05PM +0800, Zhang Rui wrote: > > Hi, Eduardo, > > > > On 四, 2018-04-12 at 21:08 -0700, Eduardo Valentin wrote: > > > Hello, > > > > > > On Thu, Apr 12, 2018 at 09:55:19AM -0700, Linus Torvalds wrote: >

Re: [PATCH] sound: soc: intel: bxt_da7219_max98357a: Replace GFP_ATOMIC with GFP_KERNEL in broxton_audio_probe

On Mon, Apr 09, 2018 at 06:46:21PM +0800, Jia-Ju Bai wrote: > broxton_audio_probe() is never called in atomic context. > This function is only set as ".probe" in "struct platform_driver". Please submit patches using subject lines reflecting the style for the subsystem. This makes it easier for

Re: [PATCH 4/5] dmaengine: sprd: Add Spreadtrum DMA configuration

On 13 April 2018 at 18:11, Vinod Koul wrote: > On Fri, Apr 13, 2018 at 02:41:48PM +0800, Baolin Wang wrote: >> On 13 April 2018 at 14:36, Vinod Koul wrote: >> > On Fri, Apr 13, 2018 at 02:17:34PM +0800, Baolin Wang wrote: >> > >> >> > Agreed, users

Applied "ASoC: intel: bxt_da7219_max98357a: Replace GFP_ATOMIC with GFP_KERNEL in broxton_audio_probe" to the asoc tree

The patch ASoC: intel: bxt_da7219_max98357a: Replace GFP_ATOMIC with GFP_KERNEL in broxton_audio_probe has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree

Applied "ASoC: max9860: switch to using .probe_new" to the asoc tree

The patch ASoC: max9860: switch to using .probe_new has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "ASoC: intel: skl_nau88l25_max98357a: Replace GFP_ATOMIC with GFP_KERNEL in skylake_audio_probe" to the asoc tree

The patch ASoC: intel: skl_nau88l25_max98357a: Replace GFP_ATOMIC with GFP_KERNEL in skylake_audio_probe has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree

Applied "ASoC: intel: cht_bsw_max98090_ti: Replace GFP_ATOMIC with GFP_KERNEL in snd_cht_mc_probe" to the asoc tree

The patch ASoC: intel: cht_bsw_max98090_ti: Replace GFP_ATOMIC with GFP_KERNEL in snd_cht_mc_probe has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree

Applied "ASoC: intel: bxt_rt298: Replace GFP_ATOMIC with GFP_KERNEL in broxton_audio_probe" to the asoc tree

The patch ASoC: intel: bxt_rt298: Replace GFP_ATOMIC with GFP_KERNEL in broxton_audio_probe has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually

Applied "ASoC: atmel_ssc_dai: fix spelling mistake: "Stoping" -> "Stopping"" to the asoc tree

The patch ASoC: atmel_ssc_dai: fix spelling mistake: "Stoping" -> "Stopping" has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

[PATCH] thermal/drivers/exynos_tmu: Fix warnings in temp_to_code / code_to_temp

The latest driver cleanup introduced a compilation warning drivers/thermal/samsung/exynos_tmu.c: In function ‘exynos_get_temp’: drivers/thermal/samsung/exynos_tmu.c:931:37: warning: ‘temp’ may be used uninitialized in this function [-Wmaybe-uninitialized] *temp = code_to_temp(data, value) *

Re: [PATCH] memcg: Remove memcg_cgroup::id from IDR on mem_cgroup_css_alloc() failure

On 13.04.2018 14:02, Michal Hocko wrote: > On Fri 13-04-18 12:35:22, Kirill Tkhai wrote: >> On 13.04.2018 11:55, Michal Hocko wrote: >>> On Thu 12-04-18 17:52:04, Kirill Tkhai wrote: >>> [...] @@ -4471,6 +4477,7 @@ mem_cgroup_css_alloc(struct cgroup_subsys_state *parent_css)

Re: [PATCH] mmap.2: MAP_FIXED is okay if the address range has been reserved

On Fri, Apr 13, 2018 at 8:49 AM, Michal Hocko wrote: > On Fri 13-04-18 08:43:27, Michael Kerrisk wrote: > [...] >> So, you mean remove this entire paragraph: >> >> For cases in which the specified memory region has not been >> reserved using an

Re: [PATCH v7 11/26] of: base: Add of_get_cpu_state_node() to get idle states for a CPU node

On Thu, Apr 12, 2018 at 6:14 AM, Ulf Hansson wrote: > The CPU's idle state nodes are currently parsed at the common cpuidle DT > library, but also when initializing back-end data for the arch specific CPU > operations, as in the PSCI driver case. > > To avoid open-coding,

Re: Build error for samples/bpf/ due to commit d0266046ad54 ("x86: Remove FAST_FEATURE_TESTS")

On Fri, Apr 13, 2018 at 03:22:37PM +0200, Jesper Dangaard Brouer wrote: > Hi Peter, > > Your commit d0266046ad54 ("x86: Remove FAST_FEATURE_TESTS") broke build > for several samples/bpf programs. I'm unsure what the best way forward > is to unbreak these... > > The issue is that these samples

[PATCH] cifs: smb2ops: Fix NULL check in smb2_query_symlink

The current code null checks variable err_buf, which is always null when it is checked, hence utf16_path is free'd and the function returns -ENOENT everytime it is called, making it impossible for the execution path to reach the following code: err_buf = err_iov.iov_base; Fix this by null

Re: [PATCH v6 01/11] dt-bindings: firmware: Add bindings for ZynqMP firmware

On Tue, Apr 10, 2018 at 12:38:37PM -0700, Jolly Shah wrote: > From: Rajan Vaja > > Add documentation to describe Xilinx ZynqMP firmware driver > bindings. Firmware driver provides an interface to firmware > APIs. Interface APIs can be used by any driver to communicate > to

[PATCH] drm/vmwgfx: Fix scatterlist unmapping

dma_unmap_sg() should be called with the same number of entries originally passed to dma_map_sg(), not the number it returned, which may be fewer. Admittedly this driver probably never runs on non-coherent architectures where getting that wrong could lead to data loss, but it's always good to be

[PATCH 2/3] USB: musb: host: prevent core phy initialisation

Set the new HCD flag which prevents USB core from trying to manage our phys. This is needed to be able to associate the controller platform device with the glue device device-tree node on the BBB which uses legacy USB phys. Otherwise, the generic phy lookup in usb_phy_roothub_init() and thus HCD

[PATCH 0/3] USB: musb: dsps: phy fix and DT-topology support

I've been carrying a patch out-of-tree since my work on improving the USB device-tree support which is needed to be able to describe USB topologies for musb based controllers. This patch, which associates the platform controller device with the glue device device-tree node, did not play well with

[PATCH 3/3] USB: musb: dsps: propagate device-tree node

To be able to use DSPS-based controllers with device-tree descriptions of the USB topology, we need to associate the glue device's device-tree node with the child controller device. Note that this can also be used to eventually let USB core manage generic phys. Also note that the other glue

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