[PATCH v7 5/6] RISC-V: Remove do_IRQ() function

The only thing do_IRQ() does is call handle_arch_irq function pointer. We can very well call handle_arch_irq function pointer directly from assembly and remove do_IRQ() function hence this patch. Signed-off-by: Anup Patel Reviewed-by: Atish Patra --- arch/riscv/kernel/entry.S | 4 +++-

Re: [f2fs-dev] [PATCH] f2fs: fix retry logic in f2fs_write_cache_pages()

Hi Chao, Can you please help review below diff given by Jaegeuk? If it looks good, I can send a v2. Thanks, On Thu, May 28, 2020 at 12:18:39PM -0700, Jaegeuk Kim wrote: > On 05/28, Chao Yu wrote: > > On 2020/5/28 10:45, Chao Yu wrote: > > > On 2020/5/27 10:20, Sahitya Tummala wrote: > > >> In

[PATCH v7 6/6] RISC-V: Force select RISCV_INTC for CONFIG_RISCV

The RISC-V per-HART local interrupt controller driver is mandatory for all RISC-V system (with/without MMU) hence we force select it for CONFIG_RISCV (just like RISCV_TIMER). Signed-off-by: Anup Patel Reviewed-by: Atish Patra --- arch/riscv/Kconfig | 1 + 1 file changed, 1 insertion(+) diff

[PATCH v7 1/6] RISC-V: self-contained IPI handling routine

Currently, the IPI handling routine riscv_software_interrupt() does not take any argument and also does not perform irq_enter()/irq_exit(). This patch makes IPI handling routine more self-contained by: 1. Passing "pt_regs *" argument 2. Explicitly doing irq_enter()/irq_exit() 3. Explicitly

[PATCH v7 2/6] RISC-V: Rename and move plic_find_hart_id() to arch directory

The plic_find_hart_id() can be useful to other interrupt controller drivers (such as RISC-V local interrupt driver) so we rename this function to riscv_of_parent_hartid() and place it in arch directory along with riscv_of_processor_hartid(). Signed-off-by: Anup Patel Reviewed-by: Atish Patra

[PATCH v7 0/6] New RISC-V Local Interrupt Controller Driver

This patchset provides a new RISC-V Local Interrupt Controller Driver for managing per-CPU local interrupts. The overall approach is inspired from the way per-CPU local interrupts are handled by Linux ARM64 and ARM GICv3 driver. It is a major re-write over perviously submitted version. (Refer,

Build regressions/improvements in v5.7

Below is the list of build error/warning regressions/improvements in v5.7[1] compared to v5.6[2]. Summarized: - build errors: +4/-8 - build warnings: +51/-253 JFYI, when comparing v5.7[1] to v5.7-rc7[3], the summaries are: - build errors: +0/-0 - build warnings: +0/-0 Note that there

[PATCH platform-next v1 1/8] platform/mellanox: mlxreg-hotplug: Use capability register for attribute creation

Create the 'sysfs' attributes according to configuration provided through the capability register, which purpose is to indicate the actual number of the components within the particular group. Such components could be, for example the FAN or power supply units. The motivation is to avoid adding a

[PATCH platform-next v1 3/8] platform_data/mlxreg: Add support for complex attributes

Add new field 'regnum' to the structure 'mlxreg_core_data' to specify the number of registers occupied by multi-register attribute. Signed-off-by: Vadim Pasternak --- include/linux/platform_data/mlxreg.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/linux/platform_data/mlxreg.h

[PATCH platform-next v1 5/8] platform/mellanox: mlxreg-io: Add support for complex attributes

Add support for attributes composed from few registers. Such attributes could occupy from 2 to 4 sequential registers. For word size register space complex attribute can occupy up to two register, for byte size - up to four. These attributes can carry, for example, CPLD or FPGA versioning, power

[PATCH platform-next v1 6/8] Documentation/ABI: Add new attribute for mlxreg-io sysfs interfaces

Add documentation for the new attributes for exposing CPLDs part numbers and CPLD minor versions. Signed-off-by: Vadim Pasternak --- Documentation/ABI/stable/sysfs-driver-mlxreg-io | 17 + 1 file changed, 17 insertions(+) diff --git

[PATCH platform-next v1 0/8] platform/x86: Add new features for Mellanox systems

The patchset adds new features for the existing Mellanox systems. Patch #1 allows to configure number of hotplug 'sysfs' attributes for the particular system class according to the hardware data for the specific system from this class, instead of configuring it

[PATCH platform-next v1 7/8] platform_data/mlxreg: Add presence register field for FAN devices

Add new field 'reg_prsnt' to the structure 'mlxreg_core_data' to provide the number FAN drawers equpped within the system. The purpose is to allow mapping between FAN drawers and FAN rotors (tachometer), since FAN drawer can be eqipped with a few rotors. Signed-off-by: Vadim Pasternak ---

[PATCH platform-next v1 8/8] platform/x86: mlx-platform: Extend FAN platform data description

Extend FAN platform data with register presence field. Add register present entry per rotor (tachometer) description tuple. The purpose is to allow indication of FAN presence. Signed-off-by: Vadim Pasternak --- drivers/platform/x86/mlx-platform.c | 13 + 1 file changed, 13

Re: [PATCH] misc: atmel-ssc: lock with mutex instead of spinlock

> Uninterruptible context is not needed in the driver and causes lockdep > warning because of mutex taken in of_alias_get_id(). Was a spin lock taken? > Convert the lock to mutex to avoid the issue. Would you like to add the tag “Fixes” to the commit message? Regards, Markus

[PATCH platform-next v1 4/8] platform/x86: mlx-platform: Add more definitions for system attributes

Add new attributes for the all type systems specifying for each equipped CPLD device, the CPLD part number and the CPLD minor version of the device: 'cpld{n}_pn' and 'cpld{n}_version_min'. This information is to be used for mathcing the current CPLD image and for making decision if image upgrade

[PATCH platform-next v1 2/8] platform/mellanox: mlxreg-hotplug: Add environmental data to uevent

Send "udev" event with environmental data in order to allow handling "ENV{}" variables in "udev" rules. Signed-off-by: Vadim Pasternak --- drivers/platform/mellanox/mlxreg-hotplug.c | 27 +-- 1 file changed, 25 insertions(+), 2 deletions(-) diff --git

Re: [f2fs-dev] [PATCH] f2fs: fix retry logic in f2fs_write_cache_pages()

Hi Chao, Can you please help review the diff given by Jaegeuk below? If it looks good, I can post a v2. Thanks, On Thu, May 28, 2020 at 12:18:39PM -0700, Jaegeuk Kim wrote: > On 05/28, Chao Yu wrote: > > On 2020/5/28 10:45, Chao Yu wrote: > > > On 2020/5/27 10:20, Sahitya Tummala wrote: > > >>

Re: [PATCH v8 3/8] PM / EM: update callback structure and add device pointer

On 5/29/20 6:43 PM, Daniel Lezcano wrote: On 27/05/2020 11:58, Lukasz Luba wrote: The Energy Model framework is going to support devices other that CPUs. In order to make this happen change the callback function and add pointer to a device as an argument. Update the related users to use new

Re: [PATCH RFCv2 9/9] arm64: Support async page fault

On 31/05/20 14:44, Marc Zyngier wrote: >> >> Is there an ARM-approved way to reuse the S2 fault syndromes to detect >> async page faults? > > It would mean being able to set an ESR_EL2 register value into ESR_EL1, > and there is nothing in the architecture that would allow that, I understand

[PATCH] afs: Fix memory leak in afs_put_sysnames()

sysnames should be freed after refcnt being decreased to zero in afs_put_sysnames(). Besides, it would be better set net->sysnames to 'NULL' after net->sysnames being released if afs_put_sysnames() aims on an afs_sysnames object. Signed-off-by: Zhihao Cheng Cc: # v4.17+ Fixes: 6f8880d8e681557

Re: [PATCH RFC] seccomp: Implement syscall isolation based on memory areas

> On May 30, 2020, at 5:26 PM, Gabriel Krisman Bertazi > wrote: > > Andy Lutomirski writes: > On May 29, 2020, at 11:00 PM, Gabriel Krisman Bertazi wrote: >>> >>> Modern Windows applications are executing system call instructions >>> directly from the application's code without

Re: arm64: Register modification during syscall entry/exit stop

On Sun, May 31, 2020 at 12:20:51PM -0400, Keno Fischer wrote: > > Can't PTRACE_SYSEMU be emulated by using PTRACE_SYSCALL, cancelling the > > syscall at the syscall enter stop, then modifying the regs at the > > syscall exit stop? > > Yes, it can. The idea behind SYSEMU is to be able to save half

Re: arm64: Register modification during syscall entry/exit stop

On Mon, Jun 1, 2020 at 5:14 AM Dave Martin wrote: > Can you explain why userspace would write a changed value for x7 > but at the same time need that new to be thrown away? The discarding behavior is the primary reason things aren't completely broken at the moment. If it read the wrong x7 value

Re: [RFC v1 2/3] drivers: nvmem: Add driver for QTI qfprom-efuse support

On 26/05/2020 23:31, Doug Anderson wrote: Hi, On Fri, May 22, 2020 at 4:18 AM Srinivas Kandagatla wrote: On 21/05/2020 22:28, Doug Anderson wrote: Hi, On Thu, May 21, 2020 at 8:56 AM Srinivas Kandagatla wrote: On 21/05/2020 16:10, Doug Anderson wrote: On 20/05/2020 23:48, Doug

Re: next-20200515: Xorg killed due to "OOM"

On Sun 31-05-20 14:16:01, Pavel Machek wrote: > On Thu 2020-05-28 14:07:50, Michal Hocko wrote: > > On Thu 28-05-20 14:03:54, Pavel Machek wrote: > > > On Thu 2020-05-28 11:05:17, Michal Hocko wrote: > > > > On Tue 26-05-20 11:10:54, Pavel Machek wrote: > > > > [...] > > > > > [38617.276517]

[GIT PULL] x86/microcode for 5.8

Hi Linus, just a single fix this time. Please pull, thx. --- The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136: Linux 5.7-rc1 (2020-04-12 12:35:55 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git

Re: [RFC][PATCH] ASoC: qcom: q6asm-dai: kCFI fix

On 29/05/2020 22:38, John Stultz wrote: Fixes the following kCFI crash seen on db845c, caused by the function prototypes not matching the callback function prototype. [ 82.585661] Unable to handle kernel NULL pointer dereference at virtual address 0001 [ 82.595387] Mem abort

Re: [PATCH v25 03/16] dt: bindings: lp50xx: Introduce the lp50xx family of RGB drivers

Hi Pavel and Dan, On 5/31/20 9:06 PM, Pavel Machek wrote: Hi! + There can only be one instance of the ti,led-bank + property for each device node. This is a required node is the LED + modules are to be backed. I don't understand the second sentence. Pretty sure it

Re: [PATCH v6 3/6] irqchip: RISC-V per-HART local interrupt controller driver

Hi Anup, On Mon, Jun 1, 2020 at 12:09 PM Anup Patel wrote: > > On Sun, May 31, 2020 at 4:23 PM Marc Zyngier wrote: > > > > On 2020-05-31 11:06, Anup Patel wrote: > > > On Sun, May 31, 2020 at 3:03 PM Marc Zyngier wrote: > > >> > > >> On 2020-05-31 06:36, Anup Patel wrote: > > >> > On Sat, May

Re: [PATCH v2] devres: keep both device name and resource name in pretty name

Hi Sergei, On Mon, 1 Jun 2020 at 10:51, Sergei Shtylyov wrote: > > Hello! > > On 31.05.2020 21:07, Vladimir Oltean wrote: > > > From: Vladimir Oltean > > > > Sometimes debugging a device is easiest using devmem on its register > > map, and that can be seen with /proc/iomem. But some device

Re: [RFC PATCH v5 1/6] dt-bindings: exynos-bus: Add documentation for interconnect properties

Hi Chanwoo, On 31.05.2020 02:01, Chanwoo Choi wrote: > On Sat, May 30, 2020 at 1:32 AM Sylwester Nawrocki > wrote: >> >> Add documentation for new optional properties in the exynos bus nodes: >> samsung,interconnect-parent, #interconnect-cells. >> These properties allow to specify the SoC

Re: arm64: Register modification during syscall entry/exit stop

On Mon, Jun 1, 2020 at 5:23 AM Dave Martin wrote: > > > Can't PTRACE_SYSEMU be emulated by using PTRACE_SYSCALL, cancelling the > > > syscall at the syscall enter stop, then modifying the regs at the > > > syscall exit stop? > > > > Yes, it can. The idea behind SYSEMU is to be able to save half

RE: [PATCH V3 2/3] arm64: dts: imx8m: add mu node

> From: Peng Fan > Sent: Monday, June 1, 2020 4:20 PM > > Add mu node to let A53 could communicate with M Core. > > Signed-off-by: Peng Fan Reviewed-by: Dong Aisheng Regards Aisheng

[RFC PATCH 1/3] dt-bindings: Add ARM PSA FF binding for non-secure VM partitions

Add devicetree bindings for a Arm PSA FF-A compliant non-secure partition at virtual interface(VMs). Signed-off-by: Sudeep Holla --- .../devicetree/bindings/arm/arm,psa-ffa.txt | 47 +++ 1 file changed, 47 insertions(+) create mode 100644

[RFC PATCH 3/3] firmware: Add example PSA FF-A non-secure VM partition

This is just an example non-secure VM partition to show how to create the device and use the PSA FF-A interface APIs. Signed-off-by: Sudeep Holla --- drivers/firmware/arm_psa_ffa/Kconfig | 7 +++ drivers/firmware/arm_psa_ffa/Makefile| 1 + drivers/firmware/arm_psa_ffa/partition.c | 71

[RFC PATCH 0/3] firmware: Add support for PSA FF-A interface

Hi All, Sorry for posting in the middle of merge window and I must have done this last week itself. This is not the driver I had thought about posting last week. After I started cleaning up and looking at Will's KVM prototype[1] for PSA FF-A (previously known as SPCI), I got more doubts on

[RFC PATCH 2/3] firmware: Add support for PSA FF-A transport for VM partitions

Initial support for PSA FF-A interface providing APIs for non-secure VM partitions. Signed-off-by: Sudeep Holla --- drivers/firmware/Kconfig | 1 + drivers/firmware/Makefile | 1 + drivers/firmware/arm_psa_ffa/Kconfig | 15 ++ drivers/firmware/arm_psa_ffa/Makefile

Re: [PATCH v7 3/6] irqchip: RISC-V per-HART local interrupt controller driver

On 2020-06-01 10:15, Anup Patel wrote: The RISC-V per-HART local interrupt controller manages software interrupts, timer interrupts, external interrupts (which are routed via the platform level interrupt controller) and other per-HART local interrupts. We add a driver for the RISC-V local

Re: [PATCH v7 4/6] clocksource/drivers/timer-riscv: Use per-CPU timer interrupt

On 2020-06-01 10:15, Anup Patel wrote: Instead of directly calling RISC-V timer interrupt handler from RISC-V local interrupt conntroller driver, this patch implements RISC-V timer interrupt as a per-CPU interrupt using per-CPU APIs of Linux IRQ subsystem. Signed-off-by: Anup Patel

Re: [PATCH v2] devres: keep both device name and resource name in pretty name

On Mon, Jun 01, 2020 at 12:36:08PM +0300, Vladimir Oltean wrote: > Hi Sergei, > > On Mon, 1 Jun 2020 at 10:51, Sergei Shtylyov > wrote: > > > > Hello! > > > > On 31.05.2020 21:07, Vladimir Oltean wrote: > > > > > From: Vladimir Oltean > > > > > > Sometimes debugging a device is easiest using

[tip: sched/core] sched: Fix smp_call_function_single_async() usage for ILB

The following commit has been merged into the sched/core branch of tip: Commit-ID: 19a1f5ec699954d21be10f74ff71c2a7079e99ad Gitweb: https://git.kernel.org/tip/19a1f5ec699954d21be10f74ff71c2a7079e99ad Author:Peter Zijlstra AuthorDate:Tue, 26 May 2020 18:10:58 +02:00

[tip: locking/core] locking: Introduce local_lock()

The following commit has been merged into the locking/core branch of tip: Commit-ID: 91710728d1725de51d06b40674abf6e860d592c7 Gitweb: https://git.kernel.org/tip/91710728d1725de51d06b40674abf6e860d592c7 Author:Thomas Gleixner AuthorDate:Wed, 27 May 2020 22:11:13 +02:00

[tip: sched/core] smp: Optimize flush_smp_call_function_queue()

The following commit has been merged into the sched/core branch of tip: Commit-ID: 52103be07d8b08311955f8c30e535c2dda290cf4 Gitweb: https://git.kernel.org/tip/52103be07d8b08311955f8c30e535c2dda290cf4 Author:Peter Zijlstra AuthorDate:Tue, 26 May 2020 18:10:59 +02:00

[tip: sched/core] irq_work, smp: Allow irq_work on call_single_queue

The following commit has been merged into the sched/core branch of tip: Commit-ID: 4b44a21dd640b692d4e9b12d3e37c24825f90baa Gitweb: https://git.kernel.org/tip/4b44a21dd640b692d4e9b12d3e37c24825f90baa Author:Peter Zijlstra AuthorDate:Tue, 26 May 2020 18:11:02 +02:00

[tip: locking/core] zram: Allocate struct zcomp_strm as per-CPU memory

The following commit has been merged into the locking/core branch of tip: Commit-ID: ed19f19256be2949af1ab5634e62178d30a355c2 Gitweb: https://git.kernel.org/tip/ed19f19256be2949af1ab5634e62178d30a355c2 Author:Sebastian Andrzej Siewior AuthorDate:Wed, 27 May 2020 22:11:18

[tip: sched/core] sched/headers: Split out open-coded prototypes into kernel/sched/smp.h

The following commit has been merged into the sched/core branch of tip: Commit-ID: 1f8db4150536431b031585ecc2a6793f69245de2 Gitweb: https://git.kernel.org/tip/1f8db4150536431b031585ecc2a6793f69245de2 Author:Ingo Molnar AuthorDate:Thu, 28 May 2020 11:01:34 +02:00

[tip: locking/core] radix-tree: Use local_lock for protection

The following commit has been merged into the locking/core branch of tip: Commit-ID: cfa6705d89b6562f79c40c249f8d94073c4276e4 Gitweb: https://git.kernel.org/tip/cfa6705d89b6562f79c40c249f8d94073c4276e4 Author:Sebastian Andrzej Siewior AuthorDate:Wed, 27 May 2020 22:11:14

[tip: sched/core] smp: Move irq_work_run() out of flush_smp_call_function_queue()

The following commit has been merged into the sched/core branch of tip: Commit-ID: afaa653c564da38c0b34c4baba31e88c46a8764c Gitweb: https://git.kernel.org/tip/afaa653c564da38c0b34c4baba31e88c46a8764c Author:Peter Zijlstra AuthorDate:Tue, 26 May 2020 18:11:00 +02:00

[tip: sched/core] smp: Optimize send_call_function_single_ipi()

The following commit has been merged into the sched/core branch of tip: Commit-ID: b2a02fc43a1f40ef4eb2fb2b06357382608d4d84 Gitweb: https://git.kernel.org/tip/b2a02fc43a1f40ef4eb2fb2b06357382608d4d84 Author:Peter Zijlstra AuthorDate:Tue, 26 May 2020 18:11:01 +02:00

[GIT PULL] EDAC for 5.8

Hi Linus, please pull the EDAC queue which accumulated this time around. Thx. --- The following changes since commit 3d77e6a8804abcc0504c904bd6e5cdf3a5cf8162: Linux 5.7 (2020-05-31 16:49:15 -0700) are available in the Git repository at:

[tip: locking/core] squashfs: Make use of local lock in multi_cpu decompressor

The following commit has been merged into the locking/core branch of tip: Commit-ID: fd56200a16c72c7c3ec3e54e06160dfaa5b8dee8 Gitweb: https://git.kernel.org/tip/fd56200a16c72c7c3ec3e54e06160dfaa5b8dee8 Author:Julia Cartwright AuthorDate:Wed, 27 May 2020 22:11:16 +02:00

Re: arm64: Register modification during syscall entry/exit stop

On Mon, Jun 01, 2020 at 05:23:01AM -0400, Keno Fischer wrote: > On Mon, Jun 1, 2020 at 5:14 AM Dave Martin wrote: > > Can you explain why userspace would write a changed value for x7 > > but at the same time need that new to be thrown away? > > The discarding behavior is the primary reason

[tip: sched/core] sched: Add rq::ttwu_pending

The following commit has been merged into the sched/core branch of tip: Commit-ID: 126c2092e5c8b28623cb890cd2930aa292410676 Gitweb: https://git.kernel.org/tip/126c2092e5c8b28623cb890cd2930aa292410676 Author:Peter Zijlstra AuthorDate:Tue, 26 May 2020 18:11:03 +02:00

[tip: sched/core] sched: Replace rq::wake_list

The following commit has been merged into the sched/core branch of tip: Commit-ID: a148866489fbe243c936fe43e4525d8dbfa0318f Gitweb: https://git.kernel.org/tip/a148866489fbe243c936fe43e4525d8dbfa0318f Author:Peter Zijlstra AuthorDate:Tue, 26 May 2020 18:11:04 +02:00

[tip: locking/core] zram: Use local lock to protect per-CPU data

The following commit has been merged into the locking/core branch of tip: Commit-ID: 19f545b6e07f753c4dc639c2f0ab52345733b6a8 Gitweb: https://git.kernel.org/tip/19f545b6e07f753c4dc639c2f0ab52345733b6a8 Author:Mike Galbraith AuthorDate:Wed, 27 May 2020 22:11:19 +02:00

[tip: locking/core] connector/cn_proc: Protect send_msg() with a local lock

The following commit has been merged into the locking/core branch of tip: Commit-ID: 3e92fd7bd2b8418b53cb7304855b8b69bedbe2b4 Gitweb: https://git.kernel.org/tip/3e92fd7bd2b8418b53cb7304855b8b69bedbe2b4 Author:Mike Galbraith AuthorDate:Wed, 27 May 2020 22:11:17 +02:00

[tip: locking/core] mm/swap: Use local_lock for protection

The following commit has been merged into the locking/core branch of tip: Commit-ID: b01b214136ac3e4746b7f76c0f204ae4b445 Gitweb: https://git.kernel.org/tip/b01b214136ac3e4746b7f76c0f204ae4b445 Author:Ingo Molnar AuthorDate:Wed, 27 May 2020 22:11:15 +02:00

Re: [PATCH 2/3] mfd: madera: Fix minor formatting issues

On Mon, Jun 01, 2020 at 06:24:33AM +0100, Lee Jones wrote: > On Fri, 29 May 2020, Charles Keepax wrote: > > Still needs a commit log. > > > Signed-off-by: Charles Keepax > > --- > > drivers/mfd/madera-core.c| 12 ++-- > > drivers/mfd/madera-i2c.c | 1 - > >

Re: [RFC PATCH v5 2/6] interconnect: Add generic interconnect driver for Exynos SoCs

Cc: Rob, devicetree ML On 31.05.2020 02:13, Chanwoo Choi wrote: > On Sat, May 30, 2020 at 1:34 AM Sylwester Nawrocki > wrote: >> >> This patch adds a generic interconnect driver for Exynos SoCs in order >> to provide interconnect functionality for each "samsung,exynos-bus" >> compatible device.

[PATCH v3] devres: keep both device name and resource name in pretty name

From: Vladimir Oltean Sometimes debugging a device is easiest using devmem on its register map, and that can be seen with /proc/iomem. But some device drivers have many memory regions. Take for example a networking switch. Its memory map used to look like this in /proc/iomem:

Re: [BOOTLOADER SPECIFICATION RFC] The bootloader log format for TrenchBoot and others

On Fri, May 29, 2020 at 10:11:40AM -0700, Andy Lutomirski wrote: > > On May 29, 2020, at 4:30 AM, Daniel Kiper wrote: > > > > Hey, > > > > Below you can find my rough idea of the bootloader log format which is > > generic thing but initially will be used for TrenchBoot work. I discussed > > this

Re: arm64: Register modification during syscall entry/exit stop

On Mon, Jun 01, 2020 at 05:40:28AM -0400, Keno Fischer wrote: > On Mon, Jun 1, 2020 at 5:23 AM Dave Martin wrote: > > > > Can't PTRACE_SYSEMU be emulated by using PTRACE_SYSCALL, cancelling the > > > > syscall at the syscall enter stop, then modifying the regs at the > > > > syscall exit stop? >

[PATCH] Documentation/CodingStyle: Fix duplicate "are" typo

The improved paragraph about line lengths contains a sentence with a duplicate word: there is one "are" at the end of a line, followed by a second one at the beginning of the next line. Drop the first one, as that one is part of the longest line. Fixes: bdc48fa11e46f867

Re: [PATCH] OPP: Check for bandwidth values before creating icc paths

On 2020-06-01 12:43, Viresh Kumar wrote: On 01-06-20, 12:09, Sibi Sankar wrote: On 2020-06-01 09:37, Viresh Kumar wrote: > On 29-05-20, 19:47, Sibi Sankar wrote: > > opp_np needs to be subjected > > to NULL check as well. > > No, it isn't. It should already be valid and is set by the OPP core.

Re: [EXTERNAL] Re: [PATCH v4] perf inject --jit: Remove //anon mmap events

On 06/01/20 16:53 PM, Ian Rogers wrote: > On Sun, May 31, 2020 at 11:17 PM Nick Gasson wrote: >> >> On 05/28/20 17:32 PM, Ian Rogers wrote: >> > >> > So on tip/perf/core with: >> > 1c0cd2dbb993 perf jvmti: Fix jitdump for methods without debug info >> > 3ce17c1e52f4 perf jvmti: remove redundant

Re: [PATCH v3] devres: keep both device name and resource name in pretty name

On Mon, Jun 01, 2020 at 12:58:26PM +0300, Vladimir Oltean wrote: > From: Vladimir Oltean > > Sometimes debugging a device is easiest using devmem on its register > map, and that can be seen with /proc/iomem. But some device drivers have > many memory regions. Take for example a networking

Re: [RFC PATCH v5 3/6] PM / devfreq: exynos-bus: Add registration of interconnect child device

Cc: Rob, devicetree ML On 31.05.2020 01:57, Chanwoo Choi wrote: > On Sat, May 30, 2020 at 1:33 AM Sylwester Nawrocki > wrote: >> >> This patch adds registration of a child platform device for the exynos >> interconnect driver. It is assumed that the interconnect provider will >> only be needed

Re: [PATCH] ata: omit superfluous error message

Hi, On 4/20/20 3:53 PM, Tang Bin wrote: > In the probe function, when get irq failed, the function > platform_get_irq() logs an error message, so remove > redundant message here. platform_get_irq() doesn't log an error message for -EPROBE_DEFER case so the conversion shouldn't be done

Re: [PATCH v3] devres: keep both device name and resource name in pretty name

Hi Greg, On Mon, 1 Jun 2020 at 13:04, Greg KH wrote: > > On Mon, Jun 01, 2020 at 12:58:26PM +0300, Vladimir Oltean wrote: > > From: Vladimir Oltean > > > > Sometimes debugging a device is easiest using devmem on its register > > map, and that can be seen with /proc/iomem. But some device

Дорогой друг, Меня зовут Барроберт Андерсон. Я адвокат и частный менеджер по работе с клиентами покойному клиенту. В 2015 году мой клиент по имени Мистер Карлос, скончался, причина, по которой я связа

Re: [PATCH] OPP: Check for bandwidth values before creating icc paths

On 01-06-20, 15:30, Sibi Sankar wrote: > Yeah dev_pm_opp_add/dev_pm_opp_set_clkname > or pretty much any api doing a > dev_pm_opp_get_opp_table without > a opp_table node associated with > it will run into this issue. Not sure if what you wrote now is correct, the problem shouldn't happen from

RE: [PATCH] pinctrl: freescale: imx: Fix an error handling path in 'imx_pinctrl_probe()'

> From: Christophe JAILLET > Sent: Sunday, May 31, 2020 4:50 AM > > 'pinctrl_unregister()' should not be called to undo > 'devm_pinctrl_register_and_init()', it is already handled by the framework. > > This simplifies the error handling paths of the probe function. > The 'imx_free_resources()'

Re: [PATCHv5 2/3] optee: use uuid for sysfs driver entry

On Fri, 29 May 2020 at 13:57, Maxim Uvarov wrote: > > OP-TEE device names for sysfs need to be unique > and it's better if they will mean something. UUID for name > looks like good solution: > /sys/bus/tee/devices/optee-ta- > I think this description is a little vague here which fails to explain

[rcu:dev.2020.05.26b 56/70] kernel/rcu/refperf.c:389: undefined reference to `__umoddi3'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2020.05.26b head: 795279db1396bf66621fa3f343fa990fe543b89e commit: 756c011f78747dc49a1e79a521fd77093849586b [56/70] refperf: Allow decimal nanoseconds config: m68k-randconfig-r024-20200601 (attached as .config

Re: [PATCH] mmc: rtsx: Add SD Express mode support for RTS5261

+linux-mmc On Mon, 1 Jun 2020 at 09:34, 冯锐 wrote: > > > > > On Tue, 19 May 2020 at 11:18, 冯锐 wrote: > > > > > > > On Tue, 28 Apr 2020 at 05:44, 冯锐 wrote: > > > > > > > > > > > > > > > > > On Mon, Apr 27, 2020 at 11:41 AM 冯锐 > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > On Sun,

Re: [PATCH v3] devres: keep both device name and resource name in pretty name

On Mon, Jun 01, 2020 at 01:13:16PM +0300, Vladimir Oltean wrote: > Hi Greg, > > On Mon, 1 Jun 2020 at 13:04, Greg KH wrote: > > > > On Mon, Jun 01, 2020 at 12:58:26PM +0300, Vladimir Oltean wrote: > > > From: Vladimir Oltean > > > > > > Sometimes debugging a device is easiest using devmem on

Re: [PATCH v2] tty: xilinx_uartps: Fix missing id assignment to the console

On 30. 05. 20 14:06, Jan Kiszka wrote: > On 04.05.20 16:27, Michal Simek wrote: >> From: Shubhrajyoti Datta >> >> When serial console has been assigned to ttyPS1 (which is serial1 alias) >> console index is not updated property and pointing to index -1 (statically >> initialized) which ends up in

Re: [PATCH] OPP: Check for bandwidth values before creating icc paths

On 2020-06-01 15:45, Viresh Kumar wrote: On 01-06-20, 15:30, Sibi Sankar wrote: Yeah dev_pm_opp_add/dev_pm_opp_set_clkname or pretty much any api doing a dev_pm_opp_get_opp_table without a opp_table node associated with it will run into this issue. Not sure if what you wrote now is correct,

drivers/net/dsa/bcm_sf2_cfp.c:890:21: sparse: sparse: incorrect type in argument 1 (different base types)

-20200601 (attached as .config) compiler: gcc-9 (Debian 9.3.0-13) 9.3.0 reproduce: # apt-get install sparse # sparse version: v0.6.1-243-gc100a7ab-dirty git checkout 8b3abe304c5f1057b7bac70fd5576dfa67e3e2b3 # save the attached .config to linux build tree make W=1 C=1

Re: [PATCH v2 2/2] nvmem: add ONIE NVMEM cells support

On Mon, Jun 01, 2020 at 10:13:05AM +0100, Srinivas Kandagatla wrote: > > > On 01/06/2020 10:03, Vadym Kochan wrote: > > > > + > > > > + nvmem = of_nvmem_device_get(np, NULL); > > > > + if (IS_ERR(nvmem)) > > > > + return PTR_ERR(nvmem); > > > > + > > > TBH, this looks

[tip:x86/entry 2/19] include/xen/interface/hvm/hvm_op.h:29:5: error: unknown type name 'domid_t'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/entry head: 5980d208e5ef28455e9e8b08f6250b443a2f0893 commit: 28447ea4154239025044381144f849ff749ee9ef [2/19] xen: Move xen_setup_callback_vector() definition to include/xen/hvm.h config: x86_64-rhel-7.6 (attached as

Re: [PATCH v2 0/4] Introduce the Counter character device interface

On Sun, 31 May 2020 13:14:06 -0400 William Breathitt Gray wrote: > On Sun, May 31, 2020 at 04:18:13PM +0100, Jonathan Cameron wrote: > > On Sun, 24 May 2020 13:54:39 -0400 > > William Breathitt Gray wrote: > > > After giving this some more thought, I believe human-readable sysfs > > >

Re: [PATCH 0/2] video: fbdev: fix error handling, convert to pin_user_pages*()

On Mon, Jun 1, 2020 at 1:00 AM John Hubbard wrote: > On 2020-05-31 14:11, Andy Shevchenko wrote: > > ... > > JFYI, we have history.git starting from v0.01. > > > OK, thanks for that note. According to that history.git [1], > then: drivers/video/pvr2fb.c had get_user_pages_fast() support added

Re: [PATCH v2 1/4] iio: chemical: scd30: add core driver

On Sun, 31 May 2020 21:21:52 +0200 Tomasz Duszynski wrote: > On Sun, May 31, 2020 at 10:58:40AM +0100, Jonathan Cameron wrote: > > On Sat, 30 May 2020 23:36:27 +0200 > > Tomasz Duszynski wrote: > > > > > Add Sensirion SCD30 carbon dioxide core driver. > > > > > > Signed-off-by: Tomasz

Re: [PATCH] staging: qlge: qlge_main.c: fixed spaces coding style issues

On Mon, 1 Jun 2020 14:19:47 +0900 Benjamin Poirier wrote: > On 2020-05-29 17:17 +0200, Jil Rouceau wrote: > > Fixed the missing spaces before and after binary operators. > > > > Signed-off-by: Jil Rouceau > > This patch does not apply cleanly. I think your base tree is missing > commit

Re: [PATCH] video: uvesafb: use true,false for bool variables

Hi, On 4/22/20 9:18 AM, Jason Yan wrote: > Fix the following coccicheck warning: > > drivers/video/fbdev/uvesafb.c:48:12-17: WARNING: Assignment of 0/1 to > bool variable > drivers/video/fbdev/uvesafb.c:1827:3-13: WARNING: Assignment of 0/1 to > bool variable >

Re: [PATCH v2] devres: keep both device name and resource name in pretty name

On Mon, Jun 1, 2020 at 12:13 AM Vladimir Oltean wrote: > On Mon, 1 Jun 2020 at 00:05, Andy Shevchenko > wrote: > > On Sunday, May 31, 2020, Vladimir Oltean wrote: > >> Sometimes debugging a device is easiest using devmem on its register > >> map, and that can be seen with /proc/iomem. But

Re: [PATCHv1 00/19] Improve SBS battery support

Hi Sebastian, On 13.05.2020 20:55, Sebastian Reichel wrote: > This patchset improves support for SBS compliant batteries. Due to > the changes, the battery now exposes 32 power supply properties and > (un)plugging it generates a backtrace containing the following message > without the first patch

Re: [PATCH v2 00/33] iommu: Move iommu_group setup to IOMMU core code

On Fri May 29 20, Jerry Snitselaar wrote: On Tue Apr 14 20, Joerg Roedel wrote: Hi, here is the second version of this patch-set. The first version with some more introductory text can be found here: https://lore.kernel.org/lkml/20200407183742.4344-1-j...@8bytes.org/ Changes v1->v2:

Re: [PATCH v2] devres: keep both device name and resource name in pretty name

On Mon, 1 Jun 2020 at 13:39, Andy Shevchenko wrote: > > On Mon, Jun 1, 2020 at 12:13 AM Vladimir Oltean wrote: > > On Mon, 1 Jun 2020 at 00:05, Andy Shevchenko > > wrote: > > > On Sunday, May 31, 2020, Vladimir Oltean wrote: > > > >> Sometimes debugging a device is easiest using devmem on its

[PATCH v2] staging: qlge: qlge_main.c: fixed spaces coding style issues

Fixed the missing spaces before and after binary operators. Signed-off-by: Jil Rouceau --- Changes in v2: - Based tree changed from Linus' to linux-next. drivers/staging/qlge/qlge_main.c | 18 +- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git

Re: [PATCHv5 1/3] optee: do drivers initialization before and after tee-supplicant run

On Fri, 29 May 2020 at 13:57, Maxim Uvarov wrote: > > Some drivers (like ftpm) can operate only after tee-supplicant > runs because of tee-supplicant provides things like storage > services. This patch splits probe of non tee-supplicant dependable > drivers to the early stage, and after

[PATCH v3 1/5] scsi: ufs-mediatek: Fix imprecise waiting time for ref-clk control

Currently ref-clk control timeout is implemented by Jiffies. However jiffies is not accurate enough thus "false timeout" may happen. Use more accurate delay mechanism instead, for example, ktime. Signed-off-by: Stanley Chu Reviewed-by: Andy Teng Reviewed-by: Avri Altman ---

[PATCH v3 3/5] scsi: ufs-mediatek: Introduce low-power mode for device power supply

Allow device power supply to enter low-power mode if device will do nothing to save more power. Signed-off-by: Stanley Chu Reviewed-by: Pengshun Zhao --- drivers/scsi/ufs/ufs-mediatek.c | 21 + 1 file changed, 21 insertions(+) diff --git a/drivers/scsi/ufs/ufs-mediatek.c

[PATCH v3 2/5] scsi: ufs-mediatek: Do not gate clocks if auto-hibern8 is not entered yet

There are some chances that link enters hibern8 lately by auto-hibern8 scheme during the clock-gating flow. Clocks shall not be gated if link is still active otherwise host or device may hang. Fix this by returning error code to the caller __ufshcd_setup_clocks() to skip gating clocks there if

[PATCH v3 4/5] scsi: ufs-mediatek: Fix unbalanced clock on/off

MediaTek UFS clocks are separated to two parts and controlled by different modules: ufs-mediatek and phy-ufs-mediatek. If both Auto-Hibern8 and clk-gating feature are enabled, mphy power control is not balanced thus unbalanced control also happens to the clocks probed by phy-ufs-mediatek module.

Re: [PATCH v3 0/2] usb: xhci: Load Raspberry Pi 4 VL805's firmware

On Tue, 2020-05-05 at 18:26 +0200, Nicolas Saenz Julienne wrote: > Newer revisions of the RPi4 need their xHCI chip, VL805, firmware to be > loaded explicitly. Earlier versions didn't need that as they where using > an EEPROM for that purpose. This series takes care of setting up the > relevant

[PATCH v3 0/5] scsi: ufs-mediatek: Fix clk-gating and introduce low-power mode for vccq2

Hi, This series fixes clk-gating issues and introduces low-power mode for vccq2 in MediaTek platforms. v2 -> v3: - Fix (add back) linkoff support in patch [4] since previous version incorrectly removed linkoff support v1 -> v2: - Add patch [4] and [5] Stanley Chu (5): scsi:

[PATCH v3 5/5] scsi: ufs-mediatek: Allow unbound mphy

Allow unbound MPHY module since not every MediaTek UFS platform needs specific MPHY control. Signed-off-by: Stanley Chu Reviewed-by: Peter Wang --- drivers/scsi/ufs/ufs-mediatek.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/drivers/scsi/ufs/ufs-mediatek.c

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