Re: [PATCH v1 4/4] ARM: dts: add pwm node for r40.

Hi, On Sun, Jan 14, 2018 at 02:43:39PM +0800, Hao Zhang wrote: > 2018-01-11 20:47 GMT+08:00 Maxime Ripard : > > On Thu, Jan 11, 2018 at 07:34:12PM +0800, hao_zhang wrote: > >> This patch add pwm node for r40. > >> > >> Signed-off-by: hao_zhang

Re: [PATCH] ACPI / LPSS: Do not instiate a platform_dev for devs without a mmio resource

Hi, On 15-01-18 00:36, Rafael J. Wysocki wrote: On Sun, Jan 14, 2018 at 9:01 PM, Hans de Goede wrote: acpi_lpss_create_device() skips handling LPSS devices which do not have a mmio resources in their resource list (typically these devices are disabled by the firmware).

Re: Improve retpoline for Skylake

On 01/12/2018 05:03 PM, Henrique de Moraes Holschuh wrote: > On Fri, 12 Jan 2018, Andi Kleen wrote: >>> Skylake still loses if it takes an SMI, right? >> >> SMMs are usually rare, especially on servers, and are usually >> not very predictible, and even if you have > > FWIW, a data point: SMIs

Re: WARNING in rfkill_alloc

Hi, > RIP: 0010:rfkill_alloc+0x2c0/0x380 net/rfkill/core.c:930 This seems pretty obvious - there's no name given. > wiphy_new_nm+0x159c/0x21d0 net/wireless/core.c:487 > ieee80211_alloc_hw_nm+0x4b4/0x2140 net/mac80211/main.c:531 which is strange, because we try to validate the name here.

Re: [PATCH v4 00/11] Introduce the Counter subsystem

2018-01-01 14:04 GMT+01:00 Jonathan Cameron : > On Mon, 1 Jan 2018 11:16:30 + > Jonathan Cameron wrote: > > Sorry to top post but I just want to add some general comments across > the whole series. > > 1) Basics look good to me. It all fits

[PATCH v4 0/3] ocfs2: add nowait aio support

As you know, VFS layer has introduced non-block aio flag IOCB_NOWAIT, which informs kernel to bail out if an AIO request will block for reasons such as file allocations, or a writeback triggered, or would block while allocating requests while performing direct I/O. Subsequent, pwritev2/preadv2

Re: [PATCH 2/2] extcon: axp288: Only reschedule charger-detection at boot when a SDP is detected

On 2018년 01월 15일 17:36, Hans de Goede wrote: > Hi, > > On 15-01-18 06:22, Chanwoo Choi wrote: >> On 2018년 01월 15일 00:10, Hans de Goede wrote: >>> The only misdetection which can happen at boot due to data-lines mux issues >>> is detecting a non SDP as SDP, so we only need to retry if we detect a

Re: [RFC PATCH 5/9] media: vb2: add support for requests

On 01/15/2018 09:24 AM, Alexandre Courbot wrote: > On Fri, Jan 12, 2018 at 7:49 PM, Hans Verkuil wrote: >> On 12/15/17 08:56, Alexandre Courbot wrote: >>> Add throttling support for buffers when requests are in use on a given >>> queue. Buffers associated to a request are kept

[PATCH v4 3/3] ocfs2: nowait aio support

Return -EAGAIN if any of the following checks fail for direct I/O with nowait flag: Can not get the related locks immediately, Blocks are not allocated at the write location, it will trigger block allocation, this will block IO operations. Signed-off-by: Gang He ---

[PATCH v4 2/3] ocfs2: add ocfs2_overwrite_io function

Add ocfs2_overwrite_io function, which is used to judge if overwrite allocated blocks, otherwise, the write will bring extra block allocation overhead. Reviewed-by: Alex Chen Signed-off-by: Gang He --- fs/ocfs2/extent_map.c | 45

[PATCH v4 1/3] ocfs2: add ocfs2_try_rw_lock and ocfs2_try_inode_lock

Add ocfs2_try_rw_lock and ocfs2_try_inode_lock functions, which will be used in non-block IO scenarios. Reviewed-by: Alex Chen Signed-off-by: Gang He --- fs/ocfs2/dlmglue.c | 21 + fs/ocfs2/dlmglue.h | 4 2 files changed, 25

Re: [PATCH v2] perf trace: Fix missing handling of --call-graph dwarf

On 01/12/2018 09:02 PM, Arnaldo Carvalho de Melo wrote: > Em Fri, Jan 12, 2018 at 01:47:06PM -0300, Arnaldo Carvalho de Melo escreveu: >> There is still room for improvement, I noticed overriding is not working >> for the probe event, investigating it now. > > So, I had to fix this another way to

Re: [PATCH] drm/dsi: Fix improper use of mipi_dsi_device_transfer() return value

On 12.01.2018 15:48, Philippe Cornu wrote: > The function mipi_dsi_device_transfer() returns the number of transmitted > or received bytes on success or a negative error code on failure. > > The functions mipi_dsi_shutdown_peripheral(), mipi_dsi_turn_on_peripheral() & >

Re: [PATCHv2 4/7] certs: allow in-kernel access of trusted keys

Hi Dan, The patch needs a description saying what you're doing and why. David

Re: [PATCH v2] arm64: allwinner: a64: orangepi-zero-plus2: add usb otg

在 2018年1月15日星期一 CST 下午4:01:39，Maxime Ripard 写道： > Hi, > > On Fri, Jan 12, 2018 at 02:39:04PM +0530, Jagan Teki wrote: > > Add usb otg support for orangepi-zero-plus2 board: > > - Add usb_otg node with dr_mode as 'otg' > > - USB0-IDDET connected to PA21 > > - VBUS connected through DCIN which

Re: Some linux kernel with KAISER/KPTI patch can't work under qemu + haxm.

FYI, this was fixed by https://www.spinics.net/lists/stable/msg209612.html On Tue, Jan 9, 2018 at 5:36 PM, lepton wrote: > I tried some debug, it seems it crashed after switch CR3: > > > I tried 2 different kernel, so actual crash points are different, but > they have same

Re: [PATCH 0/2] PM / core: genpd fix and pm_runtime_force_suspend|resume() rework

Hi Rafael, On Mon, Jan 15, 2018 at 1:04 AM, Rafael J. Wysocki wrote: > On Sun, Jan 14, 2018 at 10:48 AM, Geert Uytterhoeven > wrote: >> On Sat, Jan 13, 2018 at 1:38 AM, Rafael J. Wysocki >> wrote: >>> On Friday, January 12, 2018

[PATCH] ipmi: Clear smi_info->thread to prevent use-after-free during module unload

Subject:[PATCH] ipmi: Clear smi_info->thread to prevent use-after-free during module unload To: Corey Minyard To: openipmi-develo...@lists.sourceforge.net Cc: linux-kernel@vger.kernel.org Cc: j-nom...@ce.jp.nec.com Cc: k-u...@ct.jp.nec.com Cc: m-yamaz...@ah.jp.nec.com During

Re: [PATCH v10 1/3] lib: Add strongly typed 64bit int_sqrt

On 12 January 2018 at 10:41, David Laight wrote: > From: Crt Mori [mailto:c...@melexis.com] >> Sent: 09 January 2018 15:18 >> >> It has been some time now since this moved. I have decided not to use >> David's implementation because I want to maintain also range above >>

Re: [PATCH] PM / OPP: list_del_rcu should be used in function _remove_list_dev

On 15 January 2018 at 16:03, Greg Kroah-Hartman wrote: > On Mon, Dec 18, 2017 at 10:57:17AM +0100, Greg Kroah-Hartman wrote: >> On Mon, Dec 18, 2017 at 05:37:38PM +0800, Chunyan Zhang wrote: >> > From: Vincent Wang >> > >> > list_del_rcu()

Re: [PATCH v8 7/7] arm64: kvm: handle SError Interrupt by categorization

On Fri, Jan 12, 2018 at 06:05:23PM +, James Morse wrote: > On 15/12/17 03:30, gengdongjiu wrote: > > On 2017/12/7 14:37, gengdongjiu wrote: [...] > > (I recall someone saying migration is needed for any new KVM/cpu features, > but I > can't find the thread) > I don't know of any hard

Re: [PATCH v1 3/4] ARM: dts: add pwm pins for r40.

On Sun, Jan 14, 2018 at 03:07:46PM +0800, Hao Zhang wrote: > 2018-01-11 20:47 GMT+08:00 Maxime Ripard : > > Hi, > > > > On Thu, Jan 11, 2018 at 07:33:23PM +0800, hao_zhang wrote: > >> This patch add pwm pins for r40. > >> > >> Signed-off-by: hao_zhang

Re: [RFC PATCH 0/9] media: base request API support

On 01/15/2018 09:24 AM, Alexandre Courbot wrote: > Hi Hans, > > On Fri, Jan 12, 2018 at 8:45 PM, Hans Verkuil wrote: >> Hi Alexandre, >> >> On 12/15/17 08:56, Alexandre Courbot wrote: >>> Here is a new attempt at the request API, following the UAPI we agreed on in >>> Prague.

Re: possible deadlock (4)

On Mon, Jan 15, 2018 at 9:46 AM, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 2c1cfa49901839136e578ca516a7e230182da024 > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master > compiler: gcc (GCC) 7.1.1

Re: [PATCH v5 0/2] printk: Console owner and waiter logic cleanup

On Sat 2018-01-13 16:31:00, Sergey Senozhatsky wrote: > On (01/12/18 13:55), Petr Mladek wrote: > [..] > > > I'm not fixing console_unlock(), I'm fixing printk(). BTW, all my > > > kernels are CONFIG_PREEMPT (I'm a RT guy), my mind thinks more about > > > PREEMPT kernels than !PREEMPT ones. > > >

Re: revamp vmem_altmap / dev_pagemap handling V3

On Mon, Jan 08, 2018 at 11:44:02AM -0800, Dan Williams wrote: > On Mon, Jan 8, 2018 at 3:26 AM, Christoph Hellwig wrote: > > Any chance to get this fully reviewed and picked up before the > > end of the merge window? > > I'm fine carrying these through the nvdimm tree, but I'd need

Re: [PATCH 30/32] aio: add delayed cancel support

On Thu, Jan 11, 2018 at 10:27:05AM -0500, Jeff Moyer wrote: > Duh, good point. My main concern is that things like usb gadget will > have to deal with races between cancellation and completion on their > own. It would be nice if we had infrastructure for them to use. I'll > have a look through

Re: [PATCH 32/32] aio: implement io_pgetevents

On Fri, Jan 12, 2018 at 03:44:52PM -0500, Jeff Moyer wrote: > Christoph Hellwig writes: > > > This is the io_getevents equivalent of ppoll/pselect and allows to > > properly mix signals and aio completions (especially with IOCB_CMD_POLL) > > and atomically executes the following

Re: [PATCH][next] hwrng: exynos: check for -ve error return from readl_poll_timeout

On Fri, Jan 12, 2018 at 5:30 PM, Colin King wrote: > From: Colin Ian King > > Currently, the return from readl_poll_timeout is being assigned to > a u32 and this is being checked for a -ve return which is always > false since a u32 cannot be

[PATCH] fw_cfg: don't use DMA mapping for fw_cfg device

fw_cfg device does not need IOMMU protection, so use physical addresses always. That's how QEMU implements fw_cfg. Otherwise we'll see call traces during boot when vIOMMU is enabled in guest: [1.018306] [ cut here ] [1.018314] WARNING: CPU: 1 PID: 1 at

Re: [PATCH v2 03/16] pwm: cros-ec: update documentation regarding pwm-cells

On 12.01.2018 20:31, Brian Norris wrote: > On Fri, Jan 12, 2018 at 04:22:50PM +0200, Claudiu Beznea wrote: >> pwm-cells should be at least 2 to provide channel number and period value. > > Nacked-by: Brian Norris > > We don't control the period from the kernel; only

Re: Improve retpoline for Skylake

On Mon, 2018-01-15 at 03:26 -0500, Jon Masters wrote: > > Our numbers on Skylake weren't bad, and there seem to be all kinds of > corner cases, so again, it seems as if IBRS is the safest choice. If only someone were rapidly iterating the IBRS patch set on top of the latest tip, fixing the

RE: [PATCH v2 10/16] remoteproc: add memory device registering in rproc_add_carveout

> -Original Message- > From: Bjorn Andersson [mailto:bjorn.anders...@linaro.org] > Sent: Thursday, December 14, 2017 2:30 AM > To: Loic PALLARDY > Cc: o...@wizery.com; linux-remotep...@vger.kernel.org; linux- > ker...@vger.kernel.org; Arnaud POULIQUEN

Re: WARNING in rfkill_alloc

On Mon, Jan 15, 2018 at 9:57 AM, Johannes Berg wrote: > Hi, > >> RIP: 0010:rfkill_alloc+0x2c0/0x380 net/rfkill/core.c:930 > > This seems pretty obvious - there's no name given. > >> wiphy_new_nm+0x159c/0x21d0 net/wireless/core.c:487 >>

Re: [PATCH 7/7] xtensa: remove arch specific early DT functions

Hi Rob, On Fri, Jan 5, 2018 at 3:20 PM, Rob Herring wrote: > Now that the DT core code handles bootmem arches, we can remove the xtensa > specific early_init_dt_alloc_memory_arch function. The common > early_init_dt_add_memory_arch can be used too now that xtensa switched to >

Re: [BUG 4.15-rc7] IRQ matrix management errors

On Sun, 14 Jan 2018, Keith Busch wrote: > I hoped to have a better report before the weekend, but I've run out of > time and without my machine till next week, so sending what I have and > praying someone more in the know will have a better clue. > > I've a few NVMe drives and occasionally the

Re: LKML admins (syzbot emails are not delivered)

On Thu, Jan 4, 2018 at 4:23 PM, Eric W. Biederman wrote: > Dmitry Vyukov writes: > >> Hi Pavel, >> >> I've answered this question here in full detail. In short, this is >> useful and actionable. >>

Re: [PATCH 0/2] kconfig: 'if' and automatic submenu creation documentation

On Sun, Jan 14, 2018 at 10:00 PM, Sam Ravnborg wrote: > Hi Ulf. > > On Sun, Jan 14, 2018 at 12:33:43PM +0100, Ulf Magnusson wrote: >> These together should make the automatic submenu logic a lot clearer. >> >> Ulf Magnusson (2): >> kconfig: Document 'if' flattening logic >>

Re: [PATCH] bcma: Prevent build of PCI host features in module

Hi Kalle, On 15/01/18 10:07, Kalle Valo wrote: Matt Redfearn writes: Attempting to build bcma.ko with BCMA_DRIVER_PCI_HOSTMODE=y results in a build error due to use of symbols not exported from vmlinux: ERROR: "pcibios_enable_device" [drivers/bcma/bcma.ko] undefined!

Re: [PATCH v1 4/4] ARM: dts: add pwm node for r40.

2018-01-15 16:38 GMT+08:00 Maxime Ripard : > Hi, > > On Sun, Jan 14, 2018 at 02:43:39PM +0800, Hao Zhang wrote: >> 2018-01-11 20:47 GMT+08:00 Maxime Ripard : >> > On Thu, Jan 11, 2018 at 07:34:12PM +0800, hao_zhang wrote: >> >>

Re: [PATCH 2/2] extcon: axp288: Only reschedule charger-detection at boot when a SDP is detected

HI, On 15-01-18 10:08, Chanwoo Choi wrote: On 2018년 01월 15일 17:36, Hans de Goede wrote: Hi, On 15-01-18 06:22, Chanwoo Choi wrote: On 2018년 01월 15일 00:10, Hans de Goede wrote: The only misdetection which can happen at boot due to data-lines mux issues is detecting a non SDP as SDP, so we

Re: [PATCH v13 0/7] cgroup-aware OOM killer

On Fri 12-01-18 14:03:03, David Rientjes wrote: > On Thu, 11 Jan 2018, Roman Gushchin wrote: > > > Summarizing all this, following the hierarchy is good when it reflects > > the "importance" of cgroup's memory for a user, and bad otherwise. > > In generic case with unified hierarchy it's not

Re: [PATCH] tools/lib/traceevent/event-parse: delete pevent_register_function

On Mon, 15 Jan 2018 11:08:34 +0100 Jiri Olsa wrote: > On Mon, Jan 15, 2018 at 12:50:14PM +0800, Wang YanQing wrote: > > After commit 4263cece22e3da94f16fbbcf71ce3807946d3ef3 > > ("perf tools: Stop reading the kallsyms data from perf.data"), > > there is no users of

Re: Applied "ASoC: hdac_hdmi: Ensuring proper setting of output widget power state" to the asoc tree

On Mon, Jan 15, 2018 at 11:42:16AM +0530, Vinod Koul wrote: > On Fri, Jan 12, 2018 at 09:20:12PM +, Mark Brown wrote: > > I've dropped this because it caused a conflict with the topic/hdac-hdmi > > branch - can you please check what's going on there? I merged that into > > the topic/intel

Re: linux-next: manual merge of the kvm tree with Linus' and the tip trees

On Mon, 15 Jan 2018, Stephen Rothwell wrote: > Hi all, > --- a/arch/x86/include/asm/cpufeatures.h > +++ b/arch/x86/include/asm/cpufeatures.h > @@@ -202,11 -201,9 +202,11 @@@ > #define X86_FEATURE_HW_PSTATE ( 7*32+ 8) /* AMD HW-PState */ > #define X86_FEATURE_PROC_FEEDBACK (

Re: [PATCH v2 13/19] udf: prevent bounds-check bypass via speculative execution

On Thu 11-01-18 16:47:35, Dan Williams wrote: > Static analysis reports that 'eahd->appAttrLocation' and > 'eahd->impAttrLocation' may be a user controlled values that are used as > data dependencies for calculating source and destination buffers for > memmove operations. In order to avoid

[PATCH v3 14/16] ARM: dtsi: axp81x: add battery power supply subnode

The X-Powers AXP81X PMIC exposes battery supply various data such as the battery status (charging, discharging, full, dead), current max limit, current current, battery capacity (in percentage), voltage max and min limits, current voltage, and battery capacity (in Ah). This adds the battery power

Re: Applied "ASoC: hdac_hdmi: Ensuring proper setting of output widget power state" to the asoc tree

On Mon, Jan 15, 2018 at 10:30:40AM +, Mark Brown wrote: > On Mon, Jan 15, 2018 at 11:42:16AM +0530, Vinod Koul wrote: > > On Fri, Jan 12, 2018 at 09:20:12PM +, Mark Brown wrote: > > > > I've dropped this because it caused a conflict with the topic/hdac-hdmi > > > branch - can you please

[PATCH v3 10/16] power: supply: axp20x_battery: use data structure instead of ID for

variant specific code We used to use IDs to select a function or a feature depending on the variant. It's easier to maintain the code by adding data structure storing the few differences between variants so that we don't add a pile of if conditions. Let's use this data structure and update the

[PATCH v3 13/16] mfd: axp20x: add battery power supply cell for AXP813

As axp20x-battery-power-supply now supports AXP813, add a cell for it. Signed-off-by: Quentin Schulz Acked-for-MFD-by: Lee Jones --- drivers/mfd/axp20x.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/mfd/axp20x.c

[PATCH v3 12/16] power: supply: axp20x_battery: add support for AXP813

The X-Powers AXP813 PMIC has got some slight differences from AXP20X/AXP22X PMICs: - the maximum voltage supplied by the PMIC is 4.35 instead of 4.36/4.24 for AXP20X/AXP22X, - the constant charge current formula is different, It also has a bit to tell whether the battery percentage returned by

[PATCH v3 07/16] iio: adc: axp20x_adc: add support for AXP813 ADC

The X-Powers AXP813 PMIC is really close to what is already done for AXP20X/AXP22X. There are two pairs of bits to set the rate (one for Voltage and Current measurements and one for TS/GPIO0 voltage measurements) instead of one. The register to set the ADC rates is different from the one for

[PATCH v3 02/16] dt-bindings: iio: adc: add binding for X-Powers AXP PMICs ADC

X-Powers PMICs have several ADC channels that can be used for different purposes, e.g. PMIC internal temperature, battery voltage or AC current. This is the documentation for AXP209, AXP221/223 and AXP813 ADC bindings. Signed-off-by: Quentin Schulz

[PATCH v3 11/16] dt-bindings: power: supply: axp20x: add AXP813 battery DT binding

The AXP813 can have a battery as power supply, so let's add it to the list of compatibles. Signed-off-by: Quentin Schulz Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/power/supply/axp20x_battery.txt | 8 +++ 1 file

[PATCH v3 09/16] mfd: axp20x: probe axp20x_adc driver for AXP813

This makes the axp20x_adc driver probe with platform device id "axp813-adc". Signed-off-by: Quentin Schulz --- drivers/mfd/axp20x.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.c index

Re: INFO: task hung in filemap_fault

Dmitry Vyukov wrote: > On Mon, Jan 8, 2018 at 11:48 AM, Tetsuo Handa > wrote: > > Dmitry Vyukov wrote: > >> >> Hi Tetsuo, > >> >> > >> >> syzbot always re-runs the same workload on a new machine. If it > >> >> manages to reproduce the problem, it provides a

Re: [PATCH v2 2/7] x86/hyper-v: add a function to read both TSC and TSC page value simulateneously

Thomas Gleixner writes: > On Wed, 13 Dec 2017, Vitaly Kuznetsov wrote: > >> This is going to be used from KVM code where we need to get both >> TSC and TSC page value. >> >> When Hyper-V code is compiled out just return rdtsc(), this will allow us >> to avoid ugly ifdefs in

Re: [PATCH 2/3] tracing: make sure the parsed string always terminates with '\0'

On Tue, Jan 09, 2018 at 11:10:22PM -0500, Steven Rostedt wrote: > On Wed, 10 Jan 2018 11:02:06 +0800 > "Du, Changbin" wrote: > > > On Tue, Jan 09, 2018 at 06:02:58PM -0500, Steven Rostedt wrote: > > > On Tue, 9 Jan 2018 17:55:47 +0800 > > > changbin...@intel.com wrote: >

Re: Query: Crash is coming during /prod/PID/stat and do_exit of same task

Hello Gaurav. On 2018-01-09, Kohli, Gaurav wrote: > We are seeing crash in do_task_stat while accessing stack pointer, It > seems same task has already completed do_exit call. > So it seems a race between them: > > Below is the crash trace: > 49750.534377] Kernel BUG at

Re: [PATCH] fw_cfg: don't use DMA mapping for fw_cfg device

Hi On Mon, Jan 15, 2018 at 9:55 AM, Peter Xu wrote: > fw_cfg device does not need IOMMU protection, so use physical addresses > always. That's how QEMU implements fw_cfg. Otherwise we'll see call > traces during boot when vIOMMU is enabled in guest: > > [1.018306]

Re: [PATCH] ACPI / LPSS: Do not instiate a platform_dev for devs without a mmio resource

On Mon, 2018-01-15 at 11:36 +0200, Mika Westerberg wrote: > On Sun, Jan 14, 2018 at 09:01:48PM +0100, Hans de Goede wrote: > > acpi_lpss_create_device() skips handling LPSS devices which do not > > have > > a mmio resources in their resource list (typically these devices are > > disabled by the

[PATCH v2 3/3] tracing: make sure the parsed string always terminates with '\0'

From: Changbin Du Always mark the parsed string with a terminated '\0' even parser expects another input to be parsed. Thus the users needn't append '0' before using parsed string if new input is not given. Signed-off-by: Changbin Du ---

[PATCH v2 2/3] tracing: clear parser->idx if parser gets nothing

From: Changbin Du If only spaces was got in that cycle, we should clear parser->idx to make trace_parser_loaded() return false. Signed-off-by: Changbin Du --- kernel/trace/trace.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

Re: [PATCH v5 0/2] printk: Console owner and waiter logic cleanup

On Mon 2018-01-15 11:17:43, Petr Mladek wrote: > PS: Sergey, you have many good points. The printk-stuff is very > complex and we could spend years discussing the perfect solution. BTW: One solution that comes to my mind is based on ideas already mentioned in this thread: void

Re: [PATCH v3 11/13] arm64: Implement branch predictor hardening for affected Cortex-A CPUs

Hi Suzuki, On 09/01/18 16:12, Suzuki K Poulose wrote: > On 08/01/18 17:32, Will Deacon wrote: >> Cortex-A57, A72, A73 and A75 are susceptible to branch predictor aliasing >> and can theoretically be attacked by malicious code. >> >> This patch implements a PSCI-based mitigation for these CPUs

[PATCH v2 0/3] tracing: Fix the parser when processing strings w/ or w/o terminated '\0'

From: Changbin Du I found there are some problems in the tracing parser when I investiage the root cause of issues mentioned in below patch. https://patchwork.kernel.org/patch/10132953/ This serials can fix them. Changbin Du (3): tracing: detect the string termination

[PATCH] s390: fix setgid16/setuid16 handling of -1

For some reason, the implementation of these two 16-bit ID system calls used cast instead of low2highgid/low2highuid macros for converting [GU]IDs, which leads to incorrect handling of value of -1 (which ought to be considered invalid). Discovered by strace test suite. Signed-off-by: Eugene

[PATCH v2 1/3] tracing: detect the string termination character when parsing user input string

From: Changbin Du The usersapce can give a '\0' terminated C string in the input buffer. Before this change, trace_get_user() will return a parsed string "\0" in below case which is not expected (expects it skip all inputs) and cause the caller failed.

[PATCH v3 16/16] ARM: dtsi: axp81x: remove IP name from DT node name

The DT node should be named after its functionality and not after the IP it's defining. Signed-off-by: Quentin Schulz --- arch/arm/boot/dts/axp81x.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/axp81x.dtsi

[PATCH v3 05/16] ARM: dtsi: axp22x: add node for ADC

This adds a DT node for the ADC of the PMIC so that there can be consumers of its IIO channels declaring their consumptions via DT. Signed-off-by: Quentin Schulz --- arch/arm/boot/dts/axp22x.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git

[PATCH v3 06/16] mfd: axp20x: make AXP209/22x cells probe their ADC via DT

This makes AXP209 and AXP22x ADCs probe first via DT and then by fallback via platform. Signed-off-by: Quentin Schulz --- drivers/mfd/axp20x.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.c

[PATCH -next] firmware: arm_sdei: Fix return value check in sdei_present_dt()

In case of error, the function of_platform_device_create() returns NULL pointer not ERR_PTR(). The IS_ERR() test in the return value check should be replaced with NULL test. Fixes: 677a60bd2003 ("firmware: arm_sdei: Discover SDEI support via ACPI") Signed-off-by: Wei Yongjun

[PATCH v3 08/16] ARM: dtsi: axp81x: add node for ADC

This adds a DT node for the ADC of the PMIC so that there can be consumers of its IIO channels declaring their consumptions via DT. Signed-off-by: Quentin Schulz --- arch/arm/boot/dts/axp81x.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git

Re: [PATCH v12 1/3] lib: Add strongly typed 64bit int_sqrt

On Wed, 2018-01-10 at 09:37 +0100, Crt Mori wrote: > Shouldn't I rather make it > > if (x <= ULONG_MAX) > return int_sqrt((unsigned long) x); With this change: (I believe done in v13) and as requested by Crt Mori in a private email: Acked-by: Joe Perches

[PATCH v3 15/16] ARM: dtsi: sun8i: a711: enable battery power supply subnode

The TBS A711 has an AXP813 PMIC and a soldered battery, thus, we enable the battery power supply subnode in its Device Tree. Signed-off-by: Quentin Schulz --- arch/arm/boot/dts/sun8i-a83t-tbs-a711.dts | 4 1 file changed, 4 insertions(+) diff --git

RE: [PATCH v2 0/8] Remoteproc cleanups

> -Original Message- > From: Bjorn Andersson [mailto:bjorn.anders...@linaro.org] > Sent: Saturday, January 06, 2018 12:58 AM > To: Ohad Ben-Cohen ; Bjorn Andersson > > Cc: linux-remotep...@vger.kernel.org; linux-kernel@vger.kernel.org; Loic >

[PATCH v3 00/16] add support for AXP813 ADC and battery power supply

The AXP813 PMIC is relatively close to the already supported AXP20X and AXP22X. It provides three different power outputs: battery, AC and USB, and measures a few different things: temperature, power supply status, current current and voltage supplied, maximum current limit, battery capacity, min

[PATCH v3 01/16] iio: adc: axp20x_adc: put ADC rate setting in a per-variant function

To prepare for a new comer that set a different register with different values, move rate setting in a function that is specific to each AXP variant. Signed-off-by: Quentin Schulz --- drivers/iio/adc/axp20x_adc.c | 18 +++--- 1 file changed, 11

Re: [PATCH -next] firmware: arm_sdei: Fix return value check in sdei_present_dt()

Hi Wei, On 15/01/18 10:41, Wei Yongjun wrote: > In case of error, the function of_platform_device_create() returns > NULL pointer not ERR_PTR(). The IS_ERR() test in the return value > check should be replaced with NULL test. Bother, so it does! Thanks for catching this. Acked-by: James Morse

[PATCH v3 04/16] ARM: dtsi: axp209: add node for ADC

This adds a DT node for the ADC of the PMIC so that there can be consumers of its IIO channels declaring their consumptions via DT. Signed-off-by: Quentin Schulz --- arch/arm/boot/dts/axp209.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git

[PATCH v3 03/16] iio: adc: axp20x_adc: make it possible to probe from DT

To prepare for a future patch that will add a DT node for the ADC, make axp20x_adc able to probe from DT and get the per-variant data from of_device_id.data since platform_device_id.driver_data won't be set when probing by DT. Leave the ability to probe via platform for driver compatibility with

Re: Regression due to "PCI: Do not allocate more buses than available in parent"

Hi Fabio, On Fri, Jan 12, 2018 at 01:17:26PM -0200, Fabio Estevam wrote: > Hi Sebastian, > > On Fri, Jan 12, 2018 at 1:07 PM, Sebastian Reichel > wrote: > > Hi, > > > > I have an ARM/DT based system [0], that no longer finds its ethernet cards > > behind a

[PATCH 1/1] vfio-ccw: update documentation

The vfio-ccw documentation comes from the cover letter of the original patch submission, which shows in some parts. Give it some love; in particular: - Remove/rework statements that make sense in a cover letter, but not in regular documentation. - Fix some typos. - Describe the current

Re: [PATCH v2 4/7] x86/hyper-v: redirect reenlightment notifications on CPU offlining

Thomas Gleixner writes: > On Wed, 13 Dec 2017, Vitaly Kuznetsov wrote: >> +static int hv_cpu_die(unsigned int cpu) >> +{ >> +struct hv_reenlightenment_control re_ctrl; >> +int i; >> +static DEFINE_SPINLOCK(lock); >> + >> +if (hv_reenlightenment_cb == NULL) >>

[PATCH 0/1] vfio-ccw: start updating vfio-ccw.txt

Hi, I started to look at vfio-ccw more closely again last week, and as there will likely be some changes in the near future, I thought I'd send out this doc patch at least (the file certainly can take more updates, and I have some minor-but-not-yet-tested code changes locally). Also pushed out

Re: [PATCH v3 1/3] clk: tegra: Mark HCLK, SCLK and EMC as critical

On 10.01.2018 16:59, Dmitry Osipenko wrote: > Machine dies if HCLK, SCLK or EMC is disabled. Hence mark these clocks > as critical. > > Signed-off-by: Dmitry Osipenko > Acked-by: Peter De Schrijver > --- > > Change log: > v2: Fixed accidentally

Re: [PATCH] serial: 8250_dw: Avoid overflow in dw8250_set_termios

On 13/01/18 11:59, Nuno Gonçalves wrote: > Dear Ed, > > Thanks. > > Tested-by: Nuno Goncalves > > I just would like to report a aditional issue I find, which I am not > sure if it is intend behaviour or not. If I set bauds 1152000, > 150, 200, 250, 300, I always

Re: [PATCH 2/2] x86/microcode/intel: Extend BDW late-loading with platform id and LLC check

On Mon, 15 Jan 2018, Jia Zhang wrote: > For more details, see erratum BDF90 in document #334165 (Intel Xeon > Processor E7-8800/4800 v4 Product Family Specification Update) from > September 2017. For the record, this erratum may well affect some E5v4 as well. Anything with a LLC/core ratio >= 2.5

Re: warning: '______f' is static but declared in inline function in

On Sat, 13 Jan 2018 22:03:40 -0800 Randy Dunlap wrote: > -- orig/kernel/trace/Kconfig > +++ next/kernel/trace/Kconfig > @@ -355,7 +355,7 @@ config PROFILE_ANNOTATED_BRANCHES > on if you need to profile the system's use of these macros. > > config

Re: [PATCH v2] arm64: allwinner: a64: orangepi-zero-plus2: add usb otg

Hi, On Fri, Jan 12, 2018 at 02:39:04PM +0530, Jagan Teki wrote: > Add usb otg support for orangepi-zero-plus2 board: > - Add usb_otg node with dr_mode as 'otg' > - USB0-IDDET connected to PA21 > - VBUS connected through DCIN which always on > > Tested mass storage function. > > Signed-off-by:

Re: [PATCH] PM / OPP: list_del_rcu should be used in function _remove_list_dev

On Mon, Dec 18, 2017 at 10:57:17AM +0100, Greg Kroah-Hartman wrote: > On Mon, Dec 18, 2017 at 05:37:38PM +0800, Chunyan Zhang wrote: > > From: Vincent Wang > > > > list_del_rcu() should be used to replace list_del() in the function > > _remove_list_dev(), since the opp is a rcu protected

Re: [PATCH v2] arm64: allwinner: a64: orangepi-zero-plus2: add usb otg

在 2018年1月15日星期一 CST 下午4:01:39，Maxime Ripard 写道： > Hi, > > On Fri, Jan 12, 2018 at 02:39:04PM +0530, Jagan Teki wrote: > > Add usb otg support for orangepi-zero-plus2 board: > > - Add usb_otg node with dr_mode as 'otg' > > - USB0-IDDET connected to PA21 > > - VBUS connected through DCIN which

Re: Some linux kernel with KAISER/KPTI patch can't work under qemu + haxm.

FYI, this was fixed by https://www.spinics.net/lists/stable/msg209612.html On Tue, Jan 9, 2018 at 5:36 PM, lepton wrote: > I tried some debug, it seems it crashed after switch CR3: > > > I tried 2 different kernel, so actual crash points are different, but > they have same pattern. It crashed

Dear Talented

Dear Talented, I am Talent Scout For BLUE SKY FILM STUDIO, Present Blue sky Studio a Film Corporation Located in the United State, is Soliciting for the Right to use Your Photo/Face and Personality as One of the Semi -Major Role/ Character in our Upcoming ANIMATED Stereoscope 3D Movie-The Story

Re: [PATCH v3] nl80211: take RCU read lock when calling ieee80211_bss_get_ie()

On Mon, 2018-01-15 at 08:12 +0100, Dominik Brodowski wrote: > As ieee80211_bss_get_ie() derefences an RCU to return ssid_ie, both > the call to this function and any operation on this variable need > protection by the RCU read lock. > > Fixes: 44905265bc15 ("nl80211: don't expose wdev->ssid for

[PATCH] ipmi: Clear smi_info->thread to prevent use-after-free during module unload

Subject:[PATCH] ipmi: Clear smi_info->thread to prevent use-after-free during module unload To: Corey Minyard To: openipmi-develo...@lists.sourceforge.net Cc: linux-kernel@vger.kernel.org Cc: j-nom...@ce.jp.nec.com Cc: k-u...@ct.jp.nec.com Cc: m-yamaz...@ah.jp.nec.com During code inspection, I

Re: [PATCH 0/2] PM / core: genpd fix and pm_runtime_force_suspend|resume() rework

Hi Rafael, On Mon, Jan 15, 2018 at 1:04 AM, Rafael J. Wysocki wrote: > On Sun, Jan 14, 2018 at 10:48 AM, Geert Uytterhoeven > wrote: >> On Sat, Jan 13, 2018 at 1:38 AM, Rafael J. Wysocki >> wrote: >>> On Friday, January 12, 2018 3:31:09 PM CET Geert Uytterhoeven wrote: On Fri, Jan 12,

Re: [PATCH v10 1/3] lib: Add strongly typed 64bit int_sqrt

On 12 January 2018 at 10:41, David Laight wrote: > From: Crt Mori [mailto:c...@melexis.com] >> Sent: 09 January 2018 15:18 >> >> It has been some time now since this moved. I have decided not to use >> David's implementation because I want to maintain also range above >> 2^62 > > The last version

Re: WARNING in wiphy_register

Hi syzbot maintainers, Thanks for the report. > hwsim_new_radio_nl+0x5b7/0x7c0 drivers/net/wireless/mac80211_hwsim.c:3152 > genl_family_rcv_msg+0x7b7/0xfb0 net/netlink/genetlink.c:599 > genl_rcv_msg+0xb2/0x140 net/netlink/genetlink.c:624 You're getting into the kernel via generic netlink

Re: [RFC PATCH 4/9] videodev2.h: Add request field to v4l2_buffer

On Fri, Jan 12, 2018 at 7:22 PM, Hans Verkuil wrote: > On 12/15/17 08:56, Alexandre Courbot wrote: >> From: Hans Verkuil >> >> When queuing buffers allow for passing the request ID that >> should be associated with this buffer. >> >> Signed-off-by: Hans Verkuil >> [acour...@chromium.org: make

<    9   10   11   12   13   14   15   16   17   18   >