Re: [PATCH] mfd: tps65911-comparator: Fix an off by one bug

On Fri, Apr 20, 2018 at 11:21:50AM +0300, Dan Carpenter wrote: > On Fri, Apr 20, 2018 at 09:09:43AM +0100, Lee Jones wrote: > > On Thu, 19 Apr 2018, Dan Carpenter wrote: > > > > > The tps_comparators[] array is used in two places. We only access the > > > COMP1 (1) and COMP2 (2) elements.

Re: [patch v2] mm, oom: fix concurrent munlock and oom reaper unmap

On Thu 19-04-18 12:34:53, David Rientjes wrote: > On Thu, 19 Apr 2018, Michal Hocko wrote: > > > > exit_mmap() does not block before set_bit(MMF_OOM_SKIP) once it is > > > entered. > > > > Not true. munlock_vma_pages_all might take page_lock which can have > > unpredictable dependences. This is

Re: [PATCH v7 0/5] cpuset: Enable cpuset controller in default hierarchy

On Thu, 2018-04-19 at 09:46 -0400, Waiman Long wrote: > v7: > - Add a root-only cpuset.cpus.isolated control file for CPU isolation. > - Enforce that load_balancing can only be turned off on cpusets with >CPUs from the isolated list. > - Update sched domain generation to allow cpusets with

[PULL 1/1] vfio: ccw: process ssch with interrupts disabled

When we call ssch, an interrupt might already be pending once we return from the START SUBCHANNEL instruction. Therefore we need to make sure interrupts are disabled while holding the subchannel lock until after we're done with our processing. Cc: sta...@vger.kernel.org #v4.12+ Reviewed-by: Dong

Re: [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

On 20 April 2018 at 17:50, Jani Nikula wrote: > On Fri, 20 Apr 2018, Ian W MORRISON wrote: >> I've performed backport testing and some additional analysis as follows: > > What testing did you do beyond booting? Did you run igt? > > BR, > Jani.

[PULL 0/1] vfio-ccw: bug fix

The following changes since commit fae764912153065ea55eda47f834e0764a54df94: s390/signal: cleanup uapi struct sigaction (2018-04-17 10:36:12 +0200) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/vfio-ccw.git tags/vfio-ccw-20180420 for you

Re: [PATCH] sh: mm: Fix unprotected access to struct device

On Tue, Apr 17, 2018 at 03:54:07PM +0200, Thomas Petazzoni wrote: > > dma_alloc_coherent(>dev, memsize, _handle, GFP_KERNEL); > > and one to switch to the WARN_ON + if(dev) model. But I don't really > care either way, so: > > Reviewed-by: Thomas Petazzoni Yes,

Re: [PATCH] mfd: tps65911-comparator: Fix an off by one bug

On Fri, 20 Apr 2018, Dan Carpenter wrote: > On Fri, Apr 20, 2018 at 09:09:43AM +0100, Lee Jones wrote: > > On Thu, 19 Apr 2018, Dan Carpenter wrote: > > > > > The tps_comparators[] array is used in two places. We only access the > > > COMP1 (1) and COMP2 (2) elements. Unfortunately, we're

Re: [PATCH] ARM: tegra: fix ulpi regression on tegra20

Hi Marcel, Am Montag, 19. Februar 2018, 16:12:52 CEST schrieb Marcel Ziswiler: > From: Marcel Ziswiler > > Since commit f8f8f1d04494 ("clk: Don't touch hardware when reparenting > during registration") ULPI has been broken on Tegra20 leading to the > following error

Re: [PATCH v3 0/7] Add tda998x (HDMI) support to atmel-hlcdc

Hi Peter, I've been a bit a pain in the arse for you recently, but please bear with me a bit more, and sorry for jumping late on the band wagon. On Thu, Apr 19, 2018 at 06:27:44PM +0200, Peter Rosin wrote: > Hi! > > I naively thought that since there was support for both nxp,tda19988 (in >

Re: [PATCH 49/61] staging: nvec: simplify getting .drvdata

Am Donnerstag, 19. April 2018, 16:06:19 CEST schrieb Wolfram Sang: > We should get drvdata from struct device directly. Going via > platform_device is an unneeded step back and forth. > > Signed-off-by: Wolfram Sang Acked-by: Marc Dietrich >

Re: [PATCH] mfd: tps65911-comparator: Fix an off by one bug

On Fri, Apr 20, 2018 at 09:39:09AM +0100, Lee Jones wrote: > On Fri, 20 Apr 2018, Dan Carpenter wrote: > > > On Fri, Apr 20, 2018 at 09:09:43AM +0100, Lee Jones wrote: > > > On Thu, 19 Apr 2018, Dan Carpenter wrote: > > > > > > > The tps_comparators[] array is used in two places. We only access

Re: [RFC PATCH] kernel/sched/core: busy wait before going idle

On Fri, 20 Apr 2018 09:44:56 +0200 Peter Zijlstra wrote: > On Sun, Apr 15, 2018 at 11:31:49PM +1000, Nicholas Piggin wrote: > > This is a quick hack for comments, but I've always wondered -- > > if we have a short term polling idle states in cpuidle for performance > > --

Re: [PATCH] serial: imx: enable IMX21_UCR3_RXDMUXSEL for non-dte-mode

On Friday, April 20, 2018 02:13 PM, Uwe Kleine-König wrote: Hello Chris, On Fri, Apr 20, 2018 at 09:07:59AM +0800, Chris Ruehl wrote: Fix a problem introduced with commit e61c38d85b73 ("serial: imx: setup DCEDTE early and ensure DCD and RI irqs to be off") result in non dte-mode imx-uart fail

Re: [PATCHv5] gpio: Remove VLA from gpiolib

Hi Laura, Thanks for your patch! On Fri, Apr 13, 2018 at 11:24 PM, Laura Abbott wrote: > The new challenge is to remove VLAs from the kernel > (see https://lkml.org/lkml/2018/3/7/621) to eventually > turn on -Wvla. > > Using a kmalloc array is the easy way to fix this but

Re: [PATCH resend] usb: chipidea: Don't select EXTCON

Hi Peter On Fri, 20 Apr 2018 01:38:42 + Peter Chen wrote: > > > drivers/usb/chipidea/Kconfig | 1 - > > 1 file changed, 1 deletion(-) > > > > diff --git a/drivers/usb/chipidea/Kconfig b/drivers/usb/chipidea/Kconfig > > index > > 785f0ed037f7..97509172d536 100644 > > ---

[PATCH v2] mfd: tps65911-comparator: Fix an off by one bug

The COMP1 and COMP2 elements are in 0 and 1 respectively so this code is accessing the wrong elements and one space beyond the end of the array. We should be using "id - 1" instead. The "id" variable is never COMP (0) so that code can be removed. Fixes: 6851ad3ab346 ("TPS65911: Comparator: Add

[PATCH 1/1] um: add IRQENTRY and SOFTIRQENTRY points.

This patchs add sections for IRQENTRY and SOFTIRQENTRY. Initially added by below kernel patch for all architecture, but missed in um. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=be7635e7287e0e8013af3c89a6354a9e0182594c We need to add both sections because

RE: [PATCH v2] usb: chipidea: Hook into mux framework to toggle usb switch

> >> @@ -3,6 +3,8 @@ config USB_CHIPIDEA > >>depends on ((USB_EHCI_HCD && USB_GADGET) || (USB_EHCI_HCD && > >> !USB_GADGET) || (!USB_EHCI_HCD && USB_GADGET)) && HAS_DMA > >>select EXTCON > >>select RESET_CONTROLLER > >> + select MULTIPLEXER > >> + select MUX_GPIO > > > > The above

[PATCH v1 1/5] ARM: configs: multi_v7: Add I2C support

This patch adds I2C F7 support to multi_v7_defconfig Signed-off-by: Pierre-Yves MORDRET --- Version history: v1: * Initial --- --- arch/arm/configs/multi_v7_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [PATCH 1/8] drm/mediatek: Use regmap for register access

Hi Philipp, On 11/23/2017 09:54 AM, Philipp Zabel wrote: > Hi Matthias, > > On Tue, 2017-11-14 at 22:41 +0100, Matthias Brugger wrote: >> The mmsys memory space is shared between the drm and the >> clk driver. Use regmap to access it. >> >> Signed-off-by: Matthias Brugger >>

Re: [PATCH v3 5/7] drm/i2c: tda998x: find the drm_device via the drm_connector

Hi Peter, Thank you for the patch. On Thursday, 19 April 2018 19:27:49 EEST Peter Rosin wrote: > This prepares for being a drm_bridge which will not register the > encoder. That makes the connector the better choice. > > Signed-off-by: Peter Rosin Reviewed-by: Laurent

Re: [PATCH] ARM: dts: stm32: add reset binding on stm32mp157c

On 04/20/2018 11:09 AM, gabriel.fernan...@st.com wrote: > From: Gabriel Fernandez > > This patch adds reset binding file. > > Signed-off-by: Gabriel Fernandez > --- > arch/arm/boot/dts/stm32mp157c.dtsi | 1 + > 1 file changed, 1

Re: [PATCH v3 5/5] arm64: dts: renesas: eagle: Enable HDMI output

On Thu, Apr 12, 2018 at 10:14:01AM +0200, Jacopo Mondi wrote: > Enable HDMI output on Renesas R-Car V3M Eagle board. > > The HDMI ouput is enabled connecting the DU LVDS output to the s/ouput/output/ > transparent LVDS converter THC63LVD1024, and successively routing its > RGB output to the

Re: cpu stopper threads and load balancing leads to deadlock

On Tue, Apr 17, 2018 at 03:21:19PM +0100, Matt Fleming wrote: > Hi guys, > > We've seen a bug in one of our SLE kernels where the cpu stopper > thread ("migration/15") is entering idle balance. This then triggers > active load balance. > > At the same time, a task on another CPU triggers a page

Re: [PATCH] bsg referencing bus driver module

On Thu, 2018-04-19 at 15:10 -0700, Anatoliy Glagolev wrote: > Updated: rebased on recent Linux, cc-ed maintainers per instructions > in MAINTAINERS file > > From df939b80d02bf37b21efaaef8ede86cfd39b0cb8 Mon Sep 17 00:00:00 > 2001 > From: Anatoliy Glagolev > Date: Thu,

[tip:x86/urgent] x86/power/64: Fix page-table setup for temporary text mapping

Commit-ID: 05189820da23fc87ee2a7d87c20257f298af27f4 Gitweb: https://git.kernel.org/tip/05189820da23fc87ee2a7d87c20257f298af27f4 Author: Joerg Roedel AuthorDate: Thu, 19 Apr 2018 20:26:00 +0200 Committer: Thomas Gleixner CommitDate: Fri, 20 Apr 2018

Re: [PATCH 1/8] drm/mediatek: Use regmap for register access

Hi Matthias, On Fri, 2018-04-20 at 11:41 +0200, Matthias Brugger wrote: > Hi Philipp, > > On 11/23/2017 09:54 AM, Philipp Zabel wrote: > > Hi Matthias, > > > > On Tue, 2017-11-14 at 22:41 +0100, Matthias Brugger wrote: > > > The mmsys memory space is shared between the drm and the > > > clk

[RFC PATCH 1/2] ACPI / PNP: Don't add "enumeration_by_parent" devices

For ACPI devices with the enumeration_by_parent flag set, we expect the parent device to enumerate the device after the ACPI scan. This patch does partially the same for devices which are enumerated as PNP devices. We still want PNP scan code to create the per-ACPI device PNP device, but hold

[RFC PATCH 2/2] HISI LPC: Add PNP device support

Currently the driver creates an per-ACPI device mfd_cell for child devices. This does not suit devices which are PNP-compatible, as we expect PNP-compatible devices to derive PNP devices. To add PNP device support, we continue to allow the PNP scan code to create the PNP device (which have the

[RFC PATCH 0/2] HISI LPC: Add PNP device support

This patchset adds support for creating PNP devices for devices attached to the HiSilicon LPC host bus. Currently an mfd-cell (platform device) is created per device on the bus for using ACPI-based firmware. As such, we need require a platform driver for these devices. However for PNP-compatible

[PATCH] VFIO: Fix Documentation

From: Dong Bo Signed-off-by: Dong Bo --- Documentation/vfio.txt | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/Documentation/vfio.txt b/Documentation/vfio.txt index ef6a511..f1a4d3c 100644 --- a/Documentation/vfio.txt +++

Re: [PATCH v1 1/5] ARM: configs: multi_v7: Add I2C support

Hi Pierre-Yves, On Fri, Apr 20, 2018 at 11:17 AM, Pierre-Yves MORDRET wrote: > This patch adds I2C F7 support to multi_v7_defconfig > > Signed-off-by: Pierre-Yves MORDRET Thanks for your patch! I think the subject should be "ARM:

[tip:x86/cpu] x86/Centaur: Initialize supported CPU features properly

Commit-ID: 60882cc159e1416fb1d17210de60d4a3ba04e613 Gitweb: https://git.kernel.org/tip/60882cc159e1416fb1d17210de60d4a3ba04e613 Author: David Wang AuthorDate: Fri, 20 Apr 2018 16:29:28 +0800 Committer: Thomas Gleixner CommitDate: Fri, 20 Apr

Re: [PATCHv3 3/8] drm/omap: add support for manually updated displays

Hi Tomi, On 20 April 2018 at 08:09, Tomi Valkeinen wrote: > It's actually not quite clear to me how manual update displays work with > DRM... > > As far as I see, we have essentially two cases: 1) single buffering, > where the userspace must set an area in the fb dirty,

Re: [PATCH v3 0/7] Add tda998x (HDMI) support to atmel-hlcdc

Hello, On Friday, 20 April 2018 11:52:35 EEST jacopo mondi wrote: > Hi Peter, > I've been a bit a pain in the arse for you recently, but please > bear with me a bit more, and sorry for jumping late on the band wagon. > > On Thu, Apr 19, 2018 at 06:27:44PM +0200, Peter Rosin wrote: > > Hi! >

Re: [PATCH 4/8] dma-buf: add peer2peer flag

On Fri, Apr 20, 2018 at 10:58:50AM +0200, Christian König wrote: > > Yes there's a bit a layering violation insofar that drivers really > > shouldn't each have their own copy of "how do I convert a piece of dma > > memory into dma-buf", but that doesn't render the interface a bad idea. > >

Re: [PATCH 8/9] ath10k: use request_firmware_nowarn to load firmware

(adding linux-wireless and ath10k lists) Andres Rodriguez writes: > This reduces the unnecessary spew when trying to load optional firmware: > "Direct firmware load for ... failed with error -2" > > Signed-off-by: Andres Rodriguez > --- >

[PATCH v3 7/7] MIPS: perf: Fix BMIPS5000 system mode counting

When perf is used in system mode, i.e. specifying a set of CPUs to count (perf -a -C cpu), event->cpu is set to the CPU number on which events should be counted. The current BMIPS500 variation of mipsxx_pmu_enable_event only over sets the counter to count the current CPU, so system mode does not

[PATCH 2/2] x86/microcode: Do not exit early from __reload_late()

Vitezslav reported a case where the "Timeout during microcode update!" panic would hit. After a deeper look, it turned out that his .config had CONFIG_HOTPLUG_CPU disabled which practically made save_mc_for_early() a no-op. When that happened, the discovered microcode patch wasn't saved into

[PATCH] ARM: dts: qcom-apq8064: fix gic_irq_domain_translate warnings

Remove the usage of IRQ_TYPE_NONE to fix loud warnings from patch (83a86fbb5b56b "irqchip/gic: Loudly complain about the use of IRQ_TYPE_NONE"). Signed-off-by: Thierry Escande --- arch/arm/boot/dts/qcom-apq8064.dtsi | 52 ++--- 1 file

s390 perf events JSONs query

/pub/scm/linux/kernel/git/next/linux-next.git/commit/tools/perf/pmu-events?h=next-20180420=e9d32c1bf0cd7a98358ec4aa1625bf2b3459b9ac ARM64 chips use this feature. I am not familiar with the s390 arch, but do you think you could also use this feature? Thanks, John

Re: [PATCH v3 7/7] drm/i2c: tda998x: register as a drm bridge

; [also build test ERROR on v4.17-rc1 next-20180420] > > [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/linux/commits/Peter-Rosin/Add-tda998x-HDMI-support-to-atmel

Re: [PATCH] arm64: avoid potential infinity loop in dump_backtrace

On Fri, Apr 20, 2018 at 01:38:33PM +0800, Ji Zhang wrote: > When we dump the backtrace of some tasks there is a potential infinity > loop if the content of the stack changed, no matter the change is > because the task is running or other unexpected cases. > > This patch add stronger check on

Re: [PATCH] treewide: use PHYS_ADDR_MAX to avoid type casting ULLONG_MAX

On 20.04.2018 13:15, Matthew Wilcox wrote: > On Thu, Apr 19, 2018 at 11:42:04PM +0200, Stefan Agner wrote: >> With PHYS_ADDR_MAX there is now a type safe variant for all >> bits set. Make use of it. > > There is? I don't see it in linux-next. The patch "mm/memblock: introduce PHYS_ADDR_MAX" got

Re: [PATCH 2/3] xen netback: add fault injection facility

On 20/04/18 12:47, Stanislav Kinsburskii wrote: > This patch adds wrapper helpers around generic Xen fault inject facility. > The major reason is to keep all the module fault injection directories > in a dedicated subdirectory instead of Xen fault inject root. > > IOW, when using these helpers,

Re: [Xen-devel] [PATCH 0/1] drm/xen-zcopy: Add Xen zero-copy helper DRM driver

On 04/20/2018 10:19 AM, Daniel Vetter wrote: On Wed, Apr 18, 2018 at 11:10:58AM +0100, Roger Pau Monné wrote: On Wed, Apr 18, 2018 at 11:01:12AM +0300, Oleksandr Andrushchenko wrote: On 04/18/2018 10:35 AM, Roger Pau Monné wrote: On Wed, Apr 18, 2018 at 09:38:39AM +0300, Oleksandr

[PATCH] drivers: omap2: Kconfig: make FB_OMAP2_DSS_INIT depend on OF

Commit 7378f1149884 ("media: omap2: omapfb: allow building it with COMPILE_TEST") broke compilation without CONFIG_OF selected. CC drivers/video/fbdev/core/fbmem.o drivers/video/fbdev/omap2/omapfb/dss/omapdss-boot-init.c: In function ‘omapdss_update_prop’:

Re: [PATCH] kernel: event: core: Change return type to vm_fault_t

> I'm fine with the patch, but shouldn't this be part of a larger series / > cocinelle script? > This one is trivial but many others are not. As part of this clean up we have fixed many existing bugs in fault handlers of drivers/ file systems. Also we are replacing existing vm_insert_foo() with

Re: [9/9] nds32: Fix the allmodconfig build. To make sure CONFIG_CPU_LITTLE_ENDIAN is default y

2018-04-20 2:38 GMT+08:00 Guenter Roeck : > On Thu, Apr 19, 2018 at 09:18:15PM +0800, Greentime Hu wrote: >> This way we can build kernel with CONFIG_CPU_LITTLE_ENDIAN=y and allmodconfig >> will be available. >> >> Signed-off-by: Greentime Hu > > As

Re: [PATCH] Documentation: updates for new syscall stub naming convention

On Fri, 20 Apr 2018 07:44:25 +0200 Dominik Brodowski wrote: > For v4.17-rc1, the naming of syscall stubs changed. Update stack > traces and similar instances in the documentation to avoid sources > for confusion. > > Signed-off-by: Dominik Brodowski

Re: [PATCH 1/4] vfio: ccw: fix cleanup if cp_prefetch fails

On 04/20/2018 01:36 PM, Cornelia Huck wrote: On Fri, 20 Apr 2018 12:54:26 +0200 Halil Pasic wrote: ping I think get this fixed. Better sooner than later. [..] Hm, it seems that drowned in other patches... can I get a re-send, please? I guess Dong Jia will

Re: [PATCH 6/9] nds32: Fix the symbols undefined issue by exporting them.

2018-04-20 18:41 GMT+08:00 Christoph Hellwig : >> +++ b/arch/nds32/kernel/stacktrace.c >> @@ -9,6 +9,7 @@ void save_stack_trace(struct stack_trace *trace) >> { >> save_stack_trace_tsk(current, trace); >> } >> +EXPORT_SYMBOL(save_stack_trace); > > All other architectures

Re: [PATCH 0/6] soc: qcom: smem: bug fixes

On 04/10/2018 05:25 PM, Alex Elder wrote: > This series contains mostly bug fixes to the Qualcomm shared memory > ("smem") code. Although the bugs are real, they have most likely > never been observed. > > -Alex Ping? -Alex > > Alex Elder (6): > soc:

Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM

On Thu, 19 Apr 2018, Andrew Morton wrote: > On Thu, 19 Apr 2018 17:19:20 -0400 (EDT) Mikulas Patocka > wrote: > > > > > In order to detect these bugs reliably I submit this patch that changes > > > > kvmalloc to always use vmalloc if CONFIG_DEBUG_VM is turned on. > > > >

Re: [PATCH] KVM: s390: reset crypto attributes for all vcpus

On 20.04.2018 13:59, Janosch Frank wrote: > Thanks, applied. > Well this does not compile, as you use kvm_s390_vcpu_crypto_setup before declaration. Please fix, then I'll take the patch. > > On 19.04.2018 23:13, Tony Krowiak wrote: >> Introduces a new function to reset the crypto attributes

Re: Smatch check for Spectre stuff

On Thu, 19 Apr 2018, Dan Carpenter wrote: > Several people have asked me to write this and I think one person was > maybe working on writing it themselves... > > The point of this check is to find place which might be vulnerable to > the Spectre vulnerability. In the kernel we have the

Re: [RFC PATCH] kernel/sched/core: busy wait before going idle

On Fri, 20 Apr 2018 12:58:27 +0200 Peter Zijlstra wrote: > On Fri, Apr 20, 2018 at 07:01:47PM +1000, Nicholas Piggin wrote: > > On Fri, 20 Apr 2018 09:44:56 +0200 > > Peter Zijlstra wrote: > > > > > On Sun, Apr 15, 2018 at 11:31:49PM +1000,

Re: [PATCH 20/39] afs: simplify procfs code

David Howells wrote: > > Use remove_proc_subtree to remove the whole subtree on cleanup, and > > unwind the registration loop into individual calls. Switch to use > > proc_create_seq where applicable. > > Note that this is likely going to clash with my patch to

Re: [PATCH] KVM: s390: reset crypto attributes for all vcpus

On 20.04.2018 14:26, David Hildenbrand wrote: > On 19.04.2018 23:13, Tony Krowiak wrote: >> Introduces a new function to reset the crypto attributes for all >> vcpus whether they are running or not. Each vcpu in KVM will >> be removed from SIE prior to resetting the crypto attributes in its >> SIE

[PATCH] vfs: Undo an overly zealous MS_RDONLY -> SB_RDONLY conversion

In do_mount() when the MS_* flags are being converted to MNT_* flags, MS_RDONLY got accidentally convered to SB_RDONLY. Undo this change. Fixes: e462ec50cb5f ("VFS: Differentiate mount flags (MS_*) from internal superblock flags") Signed-off-by: David Howells ---

Re: s390 perf events JSONs query

for this arch. Support was added for factoring out common arch events in https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/tools/perf/pmu-events?h=next-20180420=e9d32c1bf0cd7a98358ec4aa1625bf2b3459b9ac ARM64 chips use this feature. I am not familiar with the s390 arch, but do

[PATCH 1/2] clk: meson: mpll: add round closest support

Allow the mpll driver to round the requested rate up if CLK_MESON_MPLL_ROUND_CLOSEST is set and it provides a rate closer to the requested rate. Signed-off-by: Jerome Brunet --- drivers/clk/meson/clk-mpll.c | 25 - drivers/clk/meson/clkc.h | 3

[PATCH 0/2] clk: meson: mpll: add round closest support

ATM, the mpll driver can only round the requested rate down, even if rounding up would have provided a better approximation of the requested rate. This patchset adds a flag to enable rounding to the closest rate possible, even if it means rounding up. The flag is then enabled on the axg platform

[PATCH 2/2] clk: meson: axg: let mpll clocks round closest

Let the mpll dividers achieve the closest rate possible, even if it means rounding the requested rate up. This is done to improve the accuracy of the rates provided by these plls to the audio subsystem Signed-off-by: Jerome Brunet --- drivers/clk/meson/axg.c | 4 1

Re: kernel panics with 4.14.X versions

On Thu 19-04-18 21:37:25, Dexuan Cui wrote: > > From: Jan Kara > > Sent: Thursday, April 19, 2018 13:23 > > Good news guys, Robert has just spotted a bug which looks like what I'd > > expect can cause your lockups / crashes. I've merged his patch to my tree > > and will push it to Linus for -rc3

[PATCH v3 5/7] MIPS: perf: Allocate per-core counters on demand

Previously when performance counters are per-core, rather than per-thread, the number available were divided by 2 on detection, and the counters used by each thread in a core were "swizzled" to ensure separation. However, this solution is suboptimal since it relies on a couple of assumptions: a)

Re: [PATCH 9/9] brcmfmac: use request_firmware_nowait2 to load firmware without warnings

Andres Rodriguez writes: > This reduces the unnecessary spew when trying to load optional firmware: > "Direct firmware load for ... failed with error -2" > > Signed-off-by: Andres Rodriguez > --- >

[PATCH v3 4/7] MIPS: perf: Fix perf with MT counting other threads

When perf is used in non-system mode, i.e. without specifying CPUs to count on, check_and_calc_range falls into the case when it sets M_TC_EN_ALL in the counter config_base. This has the impact of always counting for all of the threads in a core, even when the user has not requested it. For

[PATCH v3 6/7] MIPS: perf: Fold vpe_id() macro into it's one last usage

The vpe_id() macro is now used only in mipsxx_pmu_enable_event when CONFIG_CPU_BMIPS5000 is defined. Fold the one used definition of the macro into it's usage and remove the now unused definitions. Since we know that cpu_has_mipsmt_pertccounters == 0 on BMIPS5000, remove the test on it and just

[PATCH v3 3/7] MIPS: perf: Use correct VPE ID when setting up VPE tracing

There are a couple of FIXME's in the perf code which state that cpu_data[event->cpu].vpe_id reports 0 for both CPUs. This is no longer the case, since the vpe_id is used extensively by SMP CPS. VPE local counting gets around this by using smp_processor_id() instead. As it happens this does work

Re: [PATCH 2/6] dt-bindings: clock: add DDR3 standard speed bins.

Hi Enric, Am Donnerstag, 19. April 2018, 13:30:16 CEST schrieb Enric Balletbo i Serra: > On 19/04/18 13:10, Heiko Stuebner wrote: > > Am Donnerstag, 19. April 2018, 12:40:15 CEST schrieb Enric Balletbo i Serra: > >> DDR3 SDRAM Standard (JESD79-3F) defines some standard speed bins for > >> DDR3

Re: [RFC PATCH] kernel/sched/core: busy wait before going idle

On Fri, Apr 20, 2018 at 07:01:47PM +1000, Nicholas Piggin wrote: > On Fri, 20 Apr 2018 09:44:56 +0200 > Peter Zijlstra wrote: > > > On Sun, Apr 15, 2018 at 11:31:49PM +1000, Nicholas Piggin wrote: > > > This is a quick hack for comments, but I've always wondered -- > > > if

Re: [PATCH] sched/rt: Rework for_each_process_thread() iterations in tg_has_rt_tasks()

On 20/04/18 12:43, Kirill Tkhai wrote: > On 20.04.2018 12:25, Juri Lelli wrote: [...] > > Isn't this however checking against the current (dynamic) number of > > runnable tasks/groups instead of the "static" group membership (which > > shouldn't be affected by a task running state)? > > Ah, you

Re: [PATCH] treewide: use PHYS_ADDR_MAX to avoid type casting ULLONG_MAX

On Thu, Apr 19, 2018 at 11:42:04PM +0200, Stefan Agner wrote: > With PHYS_ADDR_MAX there is now a type safe variant for all > bits set. Make use of it. There is? I don't see it in linux-next.

Re: [PATCH 3/3] xen blkback: add fault injection facility

On 20/04/18 12:47, Stanislav Kinsburskii wrote: > This patch adds wrapper helpers around generic Xen fault inject > facility. > The major reason is to keep all the module fault injection directories > in a dedicated subdirectory instead of Xen fault inject root. > > IOW, when using these helpers,

[PATCH 1/4] ARM: dts: am437x-gp-evm: Correct tps65218 irq type

According to the documentation the interrupt line is active low. The patch will silence the warning from gic_irq_domain_translate(): "Make it clear that broken DTs are... broken" Signed-off-by: Peter Ujfalusi --- arch/arm/boot/dts/am437x-gp-evm.dts | 2 +- 1 file

[PATCH 2/4] ARM: dts: am437x-cm-t43: Correct tps65218 irq type

According to the documentation the interrupt line is active low. The patch will silence the warning from gic_irq_domain_translate(): "Make it clear that broken DTs are... broken" Signed-off-by: Peter Ujfalusi --- arch/arm/boot/dts/am437x-cm-t43.dts | 2 +- 1 file

[PATCH 3/4] ARM: dts: am437x-epos-evm: Correct tps65218 irq type

According to the documentation the interrupt line is active low. The patch will silence the warning from gic_irq_domain_translate(): "Make it clear that broken DTs are... broken" Signed-off-by: Peter Ujfalusi --- arch/arm/boot/dts/am43x-epos-evm.dts | 2 +- 1 file

[PATCH 0/4] ARM: dts: am437x boards: Correct tps65218 irq type

[2.833311] Modules linked in: [2.836417] CPU: 0 PID: 19 Comm: kworker/0:2 Not tainted 4.17.0-rc1-next-20180420-00057-gffd03ee19b9b #182 [2.846113] Hardware name: Generic AM43 (Flattened Device Tree) [2.852073] Workqueue: events deferred_probe_work_func ... Becasue most of the am437x boards had

[PATCH 4/4] ARM: dts: am437x-sk-evm: Correct tps65218 irq type

According to the documentation the interrupt line is active low. The patch will silence the warning from gic_irq_domain_translate(): "Make it clear that broken DTs are... broken" Signed-off-by: Peter Ujfalusi --- arch/arm/boot/dts/am437x-sk-evm.dts | 2 +- 1 file

Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM

On Thu, Apr 19, 2018 at 12:12:38PM -0400, Mikulas Patocka wrote: > Unfortunatelly, some kernel code has bugs - it uses kvmalloc and then > uses DMA-API on the returned memory or frees it with kfree. Such bugs were > found in the virtio-net driver, dm-integrity or RHEL7 powerpc-specific > code.

Re: Smatch check for Spectre stuff

Hi Dan, awesome stuff... So I fear that many are actually things we want to fix. Our policy was to kill the speculation on the first load and not worry if it can be completed with a dependent load/store. Also, many of the reported things (for the ones I looked at) are on slow paths and fixing

Re: [PATCH] KVM: s390: reset crypto attributes for all vcpus

Thanks, applied. On 19.04.2018 23:13, Tony Krowiak wrote: > Introduces a new function to reset the crypto attributes for all > vcpus whether they are running or not. Each vcpu in KVM will > be removed from SIE prior to resetting the crypto attributes in its > SIE state description. After all

Re: [PATCH v3 7/7] drm/i2c: tda998x: register as a drm bridge

On Thu, Apr 19, 2018 at 06:27:51PM +0200, Peter Rosin wrote: > This makes this driver work with all(?) drivers that are not > componentized and instead expect to connect to a panel/bridge. That > said, the only one tested is atmel_hlcdc. > > This hooks the relevant work function previously called

[PATCH v2 2/2] rusage: allow 64-bit times ru_utime/ru_stime

As part of the y2038 system call work, the getrusage/wait4/waitid system calls came up, since they pass time data to user space in 'timeval' format as required by POSIX. This means the existing kernel data structure is no longer compatible with the one from user space once we have a C library

Re: [PATCH bpf-next 1/5] samples/bpf: Fix typo in comment

On Thu, 19 Apr 2018 09:34:02 +0800 Leo Yan wrote: > Fix typo by replacing 'iif' with 'if'. > > Signed-off-by: Leo Yan > --- > samples/bpf/bpf_load.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/samples/bpf/bpf_load.c

Re: [alsa-devel] [PATCH v4 3/3] ALSA: hda: Disabled unused audio controller for Dell platforms with Switchable Graphics

On Fri, 20 Apr 2018 11:44:32 +0200, Kai-Heng Feng wrote: > > Now it's a typical discrete-only system. HDMI audio comes from AMD audio > controller, others from Intel audio controller. > > When SG is enabled, the unused AMD audio contoller still exposes its > sysfs, so userspace still opens the

[PATCH 01/02] net: Export get_proc_net()

Export get_proc_net() so that write() routines attached to net-namespaced proc files can find the network namespace that they're in. Currently, this is only accessible via seqfile routines. This will permit AFS to have a separate cell database per-network namespace and to manage each one

Re: [PATCH v2 0/3] eeprom: at24: last bits of the big refactoring

2018-04-12 17:08 GMT+02:00 Peter Rosin : > On 2018-04-11 16:38, Bartosz Golaszewski wrote: >> This is a follow-up to the big series merged for 4.17. The patches >> contain some bits and pieces that were missing in the last submission >> or depend on some new features merged this

[PATCH 02/02] afs: Implement namespacing

Implement namespacing within AFS, but don't yet let mounts occur outside the init namespace. An additional patch will be required propagate the network namespace across automounts. Signed-off-by: David Howells --- cell.c |4 +- internal.h | 39

Re: [PATCH] treewide: use PHYS_ADDR_MAX to avoid type casting ULLONG_MAX

On Thu, Apr 19, 2018 at 11:42:04PM +0200, Stefan Agner wrote: > With PHYS_ADDR_MAX there is now a type safe variant for all > bits set. Make use of it. > > Patch created using a sematic patch as follows: > > // > @@ > typedef phys_addr_t; > @@ > -(phys_addr_t)ULLONG_MAX > +PHYS_ADDR_MAX > // >

[PATCH][V2] isci: Fix infinite loop in while loop

From: Colin Ian King In the case when the phy_mask is bitwise anded with the phy_index bit is zero the continue statement currently jumps to the next iteration of the while loop and phy_index is never actually incremented, potentially causing an infinite loop if

Re: [PATCH] isci: Fix infinite loop in while loop

On 20/04/18 10:45, James Bottomley wrote: > On Fri, 2018-04-20 at 10:03 +0100, Colin King wrote: >> From: Colin Ian King >> >> In the case when the phy_mask is bitwise anded with the >> phy_index bit is zero the continue statement currently jumps >> to the next iteration

Re: 4.15.17 regression: bisected: timeout during microcode update

On Fri, Apr 20, 2018 at 11:52:20AM +0200, Borislav Petkov wrote: > On Fri, Apr 20, 2018 at 08:20:21AM +0200, Vitezslav Samel wrote: > > ;-) This time it works. > > Good. :-) > > > microcode: __reload_late: CPU1 waiting to exit > > x86/CPU: CPU features have changed after loading microcode,

Re: [PATCH v3 7/7] drm/i2c: tda998x: register as a drm bridge

Hi Peter, Thank you for the patch. On Thursday, 19 April 2018 19:27:51 EEST Peter Rosin wrote: > This makes this driver work with all(?) drivers that are not > componentized and instead expect to connect to a panel/bridge. That > said, the only one tested is atmel_hlcdc. > > This hooks the

[PATCH v2] sched/rt: Rework for_each_process_thread() iterations in tg_has_rt_tasks()

From: Kirill Tkhai tg_rt_schedulable() iterates over all child task groups, while tg_has_rt_tasks() iterates over all linked tasks. In case of systems with big number of tasks, this may take a lot of time. I observed hard LOCKUP on machine with 2+ processes after write

[PATCH] ARM: dts: sun4i: Fix incorrect clocks for displays

Some displays on SUN4i devices wouldn't properly stay on unless 'clk_ignore_unused' is used. Change the duplicate clocks to the probably intended ones. Signed-off-by: Pascal Roeleven --- arch/arm/boot/dts/sun4i-a10.dtsi | 6 +++--- 1 file changed, 3 insertions(+), 3

[PATCH] ARM: dts: sun4i: Fix incorrect clocks for displays

Some displays on SUN4i devices wouldn't properly stay on unless 'clk_ignore_unused' is used. Change the duplicate clocks to the probably intended ones. Signed-off-by: Pascal Roeleven --- arch/arm/boot/dts/sun4i-a10.dtsi | 6 +++--- 1 file changed, 3 insertions(+), 3

Re: [PATCH v3 7/7] drm/i2c: tda998x: register as a drm bridge

On Fri, Apr 20, 2018 at 01:06:49PM +0300, Laurent Pinchart wrote: > Hi Peter, > > Thank you for the patch. > > On Thursday, 19 April 2018 19:27:51 EEST Peter Rosin wrote: > > This makes this driver work with all(?) drivers that are not > > componentized and instead expect to connect to a

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