[PATCH v3 3/3] ARM: davinci_all_defconfig: Enable CPUFREQ_DT

From: David Lechner This sets CONFIG_CPUFREQ_DT=m in davinci_all_defconfig. This is used for frequency scaling on device tree boards. Signed-off-by: David Lechner Signed-off-by: Bartosz Golaszewski --- arch/arm/configs/davinci_all_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/

[PATCH 1/3] ARM: visit mach-* and plat-* directories when cleaning

When you run "make clean" for arm, it never visits mach-* or plat-* directories because machine-y and plat-y are just empty. When cleaning, all machine, plat directories are accumulated to machine-, plat-, respectively. So, let's pass them to core- to clean up those directories. Signed-off-by: Ma

[PATCH 2/3] ARM: at91: move platform-specific asm-offset.h to arch/arm/mach-at91

is only generated and included by arch/arm/mach-at91/, so it does not need to reside in the globally visible include/generated/. I moved and renamed it to arch/arm/mach-at91/pm_data-offsets.h since the prefix 'at91_' is just redundant in mach-at91/. Signed-off-by: Masahiro Yamada --- Can this

[PATCH 3/3] ARM: omap2: move platform-specific asm-offset.h to arch/arm/mach-omap2

is only generated and included by arch/arm/mach-omap2/, so it does not need to reside in the globally visible include/generated/. I moved and renamed it to arch/arm/mach-omap2/pm-asm-offsets.h since the prefix 'omap2-' is just redundant in mach-omap2/. Signed-off-by: Masahiro Yamada --- Can th

Re: [PATCH 1/2] x86/mm/KASLR: Fix the wrong calculation of memory region initial size

On 04/06/19 at 06:43am, Borislav Petkov wrote: > On Sat, Apr 06, 2019 at 09:51:19AM +0800, Baoquan He wrote: > > It's KASLR happened in kernel_randomize_memory() of arch/x86/mm/kaslr.c . > > What is "KASLR happened in"? This doesn't make any sense. When you look > at that function, there's a comme

Re: [PATCH] sched/core: expand sched_getaffinity(2) to return number of CPUs

* Alexey Dobriyan: >> >> Patch overloads sched_getaffinity(len=0) to simply return "nr_cpu_ids". >> >> This will make gettting CPU mask require at most 2 system calls >> >> and will eliminate unnecessary code. >> >> >> >> len=0 is chosen so that >> >> * passing zeroes is the simplest thing >> >>

Re: [MD] 4bc034d353: aim7.jobs-per-min -86.0% regression

On Mon, Apr 08 2019, kernel test robot wrote: > Greeting, > > FYI, we noticed a -86.0% regression of aim7.jobs-per-min due to commit: That is expected. The following commit 2bc13b83e6298486371761de503faeffd15b7534 should restore the performance. NeilBrown > > > commit: 4bc034d35377196c8542

[PATCH] ARM: dts: imx6dl-sabreauto: update opp table for auto part

Update i.MX6DL automotive part's opp table according to i.MX6DL automotive datasheet Rev.9, 11/2018, it adds 996MHz set-point support as below: LDO enabled(min value): 996MHz: VDDARM: 1.275V, VDDSOC: 1.175V; 792MHz: VDDARM: 1.150V, VDDSOC: 1.150V; 396MHz: VDDARM: 1.125V, VDDSOC: 1.150V; Adding 25

Re: [PATCH 0/5] Handle MCA banks in a per_cpu way

On Sun, Apr 07, 2019 at 11:13:47PM +, Ghannam, Yazen wrote: > Yazen Ghannam (5): > x86/MCE: Make struct mce_banks[] static > x86/MCE: Handle MCA controls in a per_cpu way > x86/MCE/AMD: Don't cache block addresses on SMCA systems > x86/MCE: Make number of MCA banks per_cpu > x86/MCE:

Re: [PATCH 08/12] arm64: dts: allwinner: h6: Add MMC1 pins

On Sat, Apr 06, 2019 at 01:45:10AM +0200, meg...@megous.com wrote: > From: Ondrej Jirman > > --- > arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi | 9 + > 1 file changed, 9 insertions(+) > > diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi > b/arch/arm64/boot/dts/allwinner/sun50i-

Re: [PATCH] intel-lpss: Set the device in reset state when init

On Mon, Apr 08, 2019 at 01:41:58PM +0800, Binbin Wu wrote: > In virtualized setup, when system reboots due to warm > reset interrupt storm is seen. > > Call Trace: > > dump_stack+0x70/0xa5 > __report_bad_irq+0x2e/0xc0 > note_interrupt+0x248/0x290 > ? add_interrupt_randomness+0x30/0x220 > handle_i

Re: [PATCH] pinctrl:intel: Retain HOSTSW_OWN for requested gpio pin

On Mon, Apr 08, 2019 at 12:21:03PM +0800, Chris Chiu wrote: > +static void > +intel_gpio_update_pad_mode(void __iomem *hostown, u32 mask, u32 value) > +{ > + u32 curr = readl(hostown); > + u32 updated = (curr & ~mask) | (value & mask); I think here we should first complain if the expected

Re: [PATCH 1/4] clk: meson: mpll: add init callback and regs

On Fri, 2019-04-05 at 13:43 -0700, Stephen Boyd wrote: > Quoting Michael Turquette (2019-04-05 08:43:40) > > Hi Jerome, > > > > On Fri, Mar 29, 2019 at 3:58 PM Jerome Brunet wrote: > > > On Fri, 2019-03-29 at 15:14 -0700, Stephen Boyd wrote: > > > > > > We actively discourage using init callbacks

Re: [PATCH v3 19/36] thunderbolt: Extend tunnel creation to more than 2 adjacent switches

On Sun, Apr 07, 2019 at 06:54:25PM +0200, Lukas Wunner wrote: > On Thu, Mar 28, 2019 at 03:36:16PM +0300, Mika Westerberg wrote: > > +struct tb_path *tb_path_alloc(struct tb *tb, struct tb_port *src, int > > src_hopid, > > + struct tb_port *dst, int dst_hopid, int link_nr,

Re: Removing pcap? (EZX support in mainline linux)

On Sun, 7 Apr 2019 16:07:41 +0200 Alexandre Belloni wrote: > Hello Antonio, Harald, > Hi everyone, adding Robert to CC as he is listed as the current maintainer of ARM/EZX SMARTPHONES in the MAINTAINERS file. > I've had a look at the PCAP RTC driver because I'm removing a few > deprecated APIs

Applied "spi: pxa2xxx: change "no DMA channels..." msg from debug to warning" to the spi tree

The patch spi: pxa2xxx: change "no DMA channels..." msg from debug to warning 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 in the next 24

Applied "spi: bcm2835aux: Fix build error without CONFIG_DEBUG_FS" to the spi tree

The patch spi: bcm2835aux: Fix build error without CONFIG_DEBUG_FS 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 in the next 24 hours) and

[PATCH] lightnvm: pblk: fix crash in pblk_end_partial_read due to multipage bvecs

From: Hans Holmberg Ever since '07173c3ec276 ("block: enable multipage bvecs")' we need to handle bios with multipage bvecs in pblk. Currently, a multipage bvec results in a crash[1]. Fix this by using bvec iterators in stead of direct bvec indexing. Also add a dcache flush, for the same reason

Applied "spi: tegra114: add dual mode support" to the spi tree

The patch spi: tegra114: add dual mode support 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 in the next 24 hours) and sent to Linus durin

Applied "spi: gpio: Make sure spi_master_put() is called in every error path" to the spi tree

The patch spi: gpio: Make sure spi_master_put() is called in every error path 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 in the next 24

Applied "spi-summary: document set_cs_timing" to the spi tree

The patch spi-summary: document set_cs_timing 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 in the next 24 hours) and sent to Linus during

Applied "spi: gpio: Use devm_spi_register_master()" to the spi tree

The patch spi: gpio: Use devm_spi_register_master() 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 in the next 24 hours) and sent to Linus

Applied "spi: tegra114: add 3 wire transfer mode support" to the spi tree

The patch spi: tegra114: add 3 wire transfer mode support 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 in the next 24 hours) and sent to

Applied "spi: bitbang: Introduce spi_bitbang_init()" to the spi tree

The patch spi: bitbang: Introduce spi_bitbang_init() 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 in the next 24 hours) and sent to Linus

Applied "spi: add a method for configuring CS timing" to the spi tree

The patch spi: add a method for configuring CS timing 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 in the next 24 hours) and sent to Linu

Applied "spi: document tx/rx clock delay properties" to the spi tree

The patch spi: document tx/rx clock delay properties 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 in the next 24 hours) and sent to Linus

Applied "ASoC: ab8500: add range to usleep_range" to the regulator tree

The patch ASoC: ab8500: add range to usleep_range has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.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 "regulator: bd718x7: Use rdev_get_id() to get regulator id" to the regulator tree

The patch regulator: bd718x7: Use rdev_get_id() to get regulator id has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

Applied "regulator: s2mpa01: Convert to use simplified DT parsing" to the regulator tree

The patch regulator: s2mpa01: Convert to use simplified DT parsing has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 2

Applied "ASoC: fsl-dma: Switch to SPDX identifier" to the asoc tree

The patch ASoC: fsl-dma: Switch to SPDX identifier 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 Linu

Applied "ASoC: stm32: fix sai driver name initialisation" to the asoc tree

The patch ASoC: stm32: fix sai driver name initialisation 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: [RESENT PATCH] mm/memory_hotplug: Do not unlock when fails to take the device_hotplug_lock

On Mon, Apr 08, 2019 at 12:07:17PM +0800, zhong jiang wrote: > When adding the memory by probing memory block in sysfs interface, there is an > obvious issue that we will unlock the device_hotplug_lock when fails to takes > it. > > That issue was introduced in Commit 8df1d0e4a265 > ("mm/memory_ho

Applied "ASoC: mpc5200_dma: Switch to SPDX identifier" to the asoc tree

The patch ASoC: mpc5200_dma: Switch to SPDX identifier 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: mpc5200_psc_ac97: Switch to SPDX identifier" to the asoc tree

The patch ASoC: mpc5200_psc_ac97: Switch to SPDX identifier 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 sen

Applied "ASoC: p1022_rdk: Switch to SPDX identifier" to the asoc tree

The patch ASoC: p1022_rdk: Switch to SPDX identifier 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 Li

Re: [PATCH] mm/memory_hotplug: Do not unlock when fails to take the device_hotplug_lock

://github.com/0day-ci/linux/commits/zhong-jiang/mm-memory_hotplug-Do-not-unlock-when-fails-to-take-the-device_hotplug_lock/20190408-142325 config: x86_64-randconfig-x007-201914 (attached as .config) compiler: gcc-7 (Debian 7.3.0-1) 7.3.0 reproduce: # save the attached .config to linux build tree

Applied "ASoC: wm1133-ev1: Switch to SPDX identifier" to the asoc tree

The patch ASoC: wm1133-ev1: Switch to SPDX identifier 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 L

Applied "ASoC: phycore-ac97: Switch to SPDX identifier" to the asoc tree

The patch ASoC: phycore-ac97: Switch to SPDX identifier 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: bytcht_es8316: Add quirk for the Teclast X98+ II" to the asoc tree

The patch ASoC: Intel: bytcht_es8316: Add quirk for the Teclast X98+ II 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 ho

RE: [PATCH 1/2] dt-bindings: rtc: add battery-low-hw-alarm property

HI, > On 06/04/2019 01:07:13-0500, Rob Herring wrote: > > On Wed, Apr 03, 2019 at 04:52:44PM +0200, Flavio Suligoi wrote: > > > Some RTC devices have a battery-low automatic detection circuit. > > > The battery-low event is usually reported with: > > > > > > - a bit change in a RTC status register

Re: [PATCH V2 19/20] DT bindings: spi: document tx/rx clock delay properties

On Thu, Apr 04, 2019 at 05:14:18PM -0700, Sowjanya Komatineni wrote: > Tegra SPI controller has TX and RX trimmers to tuning the delay of > SPI master clock with respect to the data. Please use subject lines matching the style for the subsystem. This makes it easier for people to identify relevan

[REGRESSION] AppArmor module parameter layout changed with c5459b829b716

Hi A recent commit changed how `/sys/module/apparmor/parameters/enabled` looks. It was "Y"/"N" before, now it is an integer. I *think* the commit that changed this was: commit c5459b829b716dafd226ad270f25c9a3050f7586 Author: Kees Cook Date: Thu Sep 13 22:28:48 2018 -0700 LSM: Plumb visibi

Re: shmem_recalc_inode: unable to handle kernel NULL pointer dereference

On 08.04.2019 9:05, Hugh Dickins wrote: On Fri, 5 Apr 2019, Konstantin Khlebnikov wrote: On 05.04.2019 5:12, Hugh Dickins wrote: Hi Alex, could you please give the patch below a try? It fixes a problem, but I'm not sure that it's your problem - please let us know. I've not yet written up the c

Re: WARN_ON_ONCE() hit at kernel/events/core.c:330

On 4/4/19 3:03 PM, Peter Zijlstra wrote: > On Thu, Apr 04, 2019 at 01:09:09PM +0200, Peter Zijlstra wrote: > >> That is not entirely the scenario I talked about, but *groan*. >> >> So what I meant was: >> >> CPU-0 CPU-n >> >> __schedule()

Re: [PATCH] soundwire: fix pm_runtime_get_sync return code checks

> On 5 Apr 2019, at 17:04, Pierre-Louis Bossart > wrote: > > On 4/5/19 2:26 AM, Jan Kotas wrote: >> >> >> ret = pm_runtime_get_sync(slave->bus->dev); >> -if (ret < 0) >> +if (ret < 0 && ret != -EACCES) >> > There was a patch submitted on 3/28 by Srinivas Kandagatla who sugges

Re: [PATCH] s390/mm: Silence compiler warning when compiling without CONFIG_PGSTE

On 07.04.19 14:55, Thomas Huth wrote: > If CONFIG_PGSTE is not set (e.g. when compiling without KVM), GCC complains: > > CC arch/s390/mm/pgtable.o > arch/s390/mm/pgtable.c:413:15: warning: ‘pmd_alloc_map’ defined but not > used [-Wunused-function] > static pmd_t *pmd_alloc_map(struct mm_s

Re: [RESENT PATCH] mm/memory_hotplug: Do not unlock when fails to take the device_hotplug_lock

On 08.04.19 06:07, zhong jiang wrote: > When adding the memory by probing memory block in sysfs interface, there is an > obvious issue that we will unlock the device_hotplug_lock when fails to takes > it. > > That issue was introduced in Commit 8df1d0e4a265 > ("mm/memory_hotplug: make add_memory(

Re: [RFC PATCH 2/9] cpufreq: qcom: Re-organise kryo cpufreq to use it for other nvmem based qcom socs

Hi Niklas, On 4/4/2019 10:39 AM, Niklas Cassel wrote: > From: Sricharan R > > The kryo cpufreq driver reads the nvmem cell and uses that data to > populate the opps. There are other qcom cpufreq socs like krait which > does similar thing. Except for the interpretation of the read data, > rest of

[net] 97cdcf37b5: BUG:using__this_cpu_read()in_preemptible[#]code:systemd-timesyn

FYI, we noticed the following commit (built with gcc-7): commit: 97cdcf37b57e3f204be3000b9eab9686f38b4356 ("net: place xmit recursion in softnet data") https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master in testcase: trinity with following parameters: runtime: 300s

Re: Regression in suspend-to-ram (TPM related) with 5.1-rc1 (BISECTED)

On Sun, Apr 7, 2019 at 10:53 PM Martin Kepplinger wrote: > > On 21.03.19 14:41, Jarkko Sakkinen wrote: > > On Tue, Mar 19, 2019 at 04:03:37PM -0700, Paul Zimmerman wrote: > >> So I bisected this down to: > >> > >> # first bad commit: [a3fbfae82b4cb3ff9928e29f34c64d0507cad874] tpm: > >> take TPM ch

<    3   4   5   6   7   8