Re: [tip:x86/cache] x86/resctrl: Initialize a new resource group with default MBA values

Hi Boris, I found a nitpick - an unnecessary newline at the end of the patch. Please help double check. Thank you. On 4/18/2019 6:14, tip-bot for Xiaochen Shen wrote: Commit-ID: 47820e73f5b3a1fdb8ebd1219191edc96e0c85c1 Gitweb: https://git.kernel.org/tip/47820e73f5b3a1fdb8ebd1219191edc96e0c

Re: [PATCH] serial: Fix using plain integer instead of Null pointer

Hi, On 2019/04/18 15:40, Greg Kroah-Hartman wrote: On Thu, Apr 18, 2019 at 03:21:25PM +0900, Sugaya Taichi wrote: Fix build warning that using plain integer as Null pointer. This is reported by kbuild test robot. Fixes: ba44dc043004 ("serial: Add Milbeaut serial control") Signed-off-by: Sugaya

Re: [PATCH] x86: kvm: hyper-v: deal with buggy TLB flush requests from WS2012

Vitaly Kuznetsov writes: > It was reported that with some special Multi Processor Group configuration, > e.g: > bcdedit.exe /set groupsize 1 > bcdedit.exe /set maxgroup on > bcdedit.exe /set groupaware on > for a 16-vCPU guest WS2012 shows BSOD on boot when PV TLB flush mechanism > is in use.

stm class: Fix possible double free

The function stm_register_device() calls put_device(&stm->dev) to release allocated memory (in stm_device_release()) on error paths. However, after that, the freed memory stm is released again, resulting in a double free bug. There is a similar issue in the function stm_source_register_device. This

Re: [PATCH] nvme: determine the number of IO queues

On Thu, 2019-04-18 at 14:21 +0800, Aaron Ma wrote: > On 4/18/19 1:33 AM, Maxim Levitsky wrote: > > On Wed, 2019-04-17 at 20:32 +0300, Maxim Levitsky wrote: > > > On Wed, 2019-04-17 at 22:12 +0800, Aaron Ma wrote: > > > > Some controllers support limited IO queues, when over set > > > > the number,

Re: [tip:x86/cache] x86/resctrl: Initialize a new resource group with default MBA values

On Thu, Apr 18, 2019 at 03:03:35PM +0800, Xiaochen Shen wrote: > In my opinion, this newline is unnecessary. Thank you. See commit message: > [ bp: Add newlines between code blocks for better readability. ] And I didn't add enough. That code is too crammed. For example, the new __init_one_rdt

Re: linux-next: manual merge of the phy-next tree with the qcom tree

On 18/04/2019 07:29, Stephen Rothwell wrote: > Today's linux-next merge of the phy-next tree got a conflict in: > > Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt > > between commit: > > 369b89366a3d ("dt-bindings: phy-qcom-qmp: Tweak qcom,msm8998-qmp-ufs-phy") > > from the qcom tr

[PATCH] f2fs: Force type conversion from __le32 to u32

This patch forces type conversion from __le32 to u32 to prevent sparse warnings like: warning: restricted __le32 degrades to integer dir.c: fscrypt_fname_disk_to_usr takes a hash of type u32 as it's second arg but de->hash_code is of type __le32. node.c NULL_ADDR is of type u32 but block_addr is

Re: [PATCH] pinctrl: mediatek: Add MT8516 Pinctrl driver

Hi, Fabien After reusing the eint_regs common, the result looks good to me On Tue, Apr 16, 2019 at 1:33 AM Fabien Parent wrote: > > This commit adds the pinctrl driver for the MediaTek's MT8516 SoC. > > Signed-off-by: Fabien Parent Acked-by: Sean Wang > --- > > v2: > * Don't assign a

[REGRESSION 5.0.x] Windows XP broken on KVM

Hi, we've got a regression report on the recent 5.0.x kernel, starting from 5.0.6, where Windows XP can't boot on KVM any longer. The culprit seems to be the patch KVM: x86: update %rip after emulating IO with the upstream commit 45def77ebf79e2e8942b89ed79294d97ce914fa0. Reverting this alone f

[PATCH] perf stat: display cvs output for --null runs

Adding support to display CVS values for --null runs as requested by Ingo. It's only for --null run so it does not mess up with standard CVS output. For single --null run in CSV mode perf displays elapsed time: $ perf stat --null -x ';' true 0.000496 For multiple --null run in CSV mode perf

Re: [PATCH] x86/mm/mem_encrypt: fix a crash with kmemleak_scan

On Tue, Apr 16, 2019 at 08:38:30PM -0400, Qian Cai wrote: > kmemleak_init() will register the data/bss sections (only register > .data..ro_after_init if not within .data) and then kmemleak_scan() will scan > those address and dereference them looking for pointer referencing. If > free_init_pages()

Re: [PATCH v2] panic: add an option to replay all the printk message in buffer

On Thu 2019-04-18 09:00:14, Sergey Senozhatsky wrote: > I think that PANIC_PRINT_ALL_PRINTK_MSG is a debugging option; a quite > specific one. So people who ask the kernel to PANIC_PRINT_ALL_PRINTK_MSG > they know what they are doing, and we probably will not cofuse anyone. > After all, we don't pr

Re: [PATCH] x86_64: Disabling read-implies-exec when the stack is executable

On Wed, May 11, 2016 at 5:45 AM Hector Marco-Gisbert wrote: > > The READ_IMPLIES_EXEC personality was removed in 2005 for 64-bit processes, > (commit a3cc2546a54361b86b73557df5b85c4fc3fc27c3 form history.git). > > But it's still possible to have all readable areas with EXEC permissions by > settin

[PATCH] wireless: Use offsetof instead of custom macro.

Use offsetof to calculate offset of a field to take advantage of compiler built-in version when possible, and avoid UBSAN warning when compiling with Clang: == UBSAN: Undefined behaviour in net/wireless/wext-core.c:525:14 member acces

Re: [REGRESSION 5.0.x] Windows XP broken on KVM

On Thu, Apr 18, 2019 at 09:38:52AM +0200, Takashi Iwai wrote: > Hi, > > we've got a regression report on the recent 5.0.x kernel, starting > from 5.0.6, where Windows XP can't boot on KVM any longer. > > The culprit seems to be the patch >KVM: x86: update %rip after emulating IO > with the up

Re: [RFC PATCH v2] perf/x86: make perf callchain work without CONFIG_FRAME_POINTER

On Wed, Apr 17, 2019 at 10:44:33PM +0800, Kairui Song wrote: > Despite it's hacky, it seems not necessary to dump every register. And > is there a straight way to get caller's regs in the trace point? It > seems more trouble some. Or if we just use the regs inside the > tracepoint, but it would nee

Re: [REGRESSION 5.0.x] Windows XP broken on KVM

On 18/04/19 09:38, Takashi Iwai wrote: > Hi, > > we've got a regression report on the recent 5.0.x kernel, starting > from 5.0.6, where Windows XP can't boot on KVM any longer. > > The culprit seems to be the patch >KVM: x86: update %rip after emulating IO > with the upstream commit 45def77eb

Re: [PATCH v4 2/2] x86/boot/KASLR: skip the specified crashkernel region

On Thu, Apr 18, 2019 at 12:06 AM Borislav Petkov wrote: > > On Wed, Apr 17, 2019 at 01:53:37PM +0800, Pingfan Liu wrote: > > Take __parse_crashkernel()->parse_crashkernel_simple() for example. If > > no offset given, then it still return 0, but crash_base is dangling. Sorry for misleading, I made

Re: linux-next: manual merge of the phy-next tree with the qcom tree

Hi Marc, On Thu, 18 Apr 2019 09:35:44 +0200 Marc Gonzalez wrote: > > It is not clear to me what I could/should have done differently to avoid > the conflict? Nothing really, it will need to be fixed up when these trees are merged into Linus' tree (or some other tree along the way). It is not a

Re: [PATCH-tip 0/2] locking/rwsem: Rwsem rearchitecture part 2 follow-up patches

* Waiman Long wrote: > As the part2 patches are still being actively modified, it doesn't look > like it will make the next merge window. I am fine with postponing it > to 5.3. However, I would like to request the merging of just patch 1 of > the part 2 patchset. It fixes a locking selftest

Re: [PATCH v2 3/3] thermal: cpu_cooling: Migrate to using the EM framework

On Thursday 18 Apr 2019 at 09:23:23 (+0530), Viresh Kumar wrote: > On 17-04-19, 10:43, Quentin Perret wrote: > > static struct thermal_cooling_device * > > __cpufreq_cooling_register(struct device_node *np, > > - struct cpufreq_policy *policy, u32 capacitance) > > +

Re: Issues with i.MX SPI DMA transfers

On 2019-04-18 at 06:30 +, Igor Plyatov wrote: > WARNING: This email was created outside of NXP. DO NOT CLICK links or > attachments unless you recognize the sender and know the content is > safe. > > > > Dear Robin, > > > > > Hi Igor, > >   Did you meet any issue with my latest patch?

Re: [REGRESSION 5.0.x] Windows XP broken on KVM

On Thu, 18 Apr 2019 09:53:28 +0200, Greg Kroah-Hartman wrote: > > On Thu, Apr 18, 2019 at 09:38:52AM +0200, Takashi Iwai wrote: > > Hi, > > > > we've got a regression report on the recent 5.0.x kernel, starting > > from 5.0.6, where Windows XP can't boot on KVM any longer. > > > > The culprit se

[tip:locking/core] locking/rwsem: Prevent unneeded warning during locking selftest

Commit-ID: 26536e7c242e2b0f73c25c46fc50d2525ebe400b Gitweb: https://git.kernel.org/tip/26536e7c242e2b0f73c25c46fc50d2525ebe400b Author: Waiman Long AuthorDate: Sat, 13 Apr 2019 13:22:44 -0400 Committer: Ingo Molnar CommitDate: Sun, 14 Apr 2019 11:09:35 +0200 locking/rwsem: Prevent unne

Re: stm class: Fix possible double free

On 4/18/2019 12:52 PM, Pan Bian wrote: The function stm_register_device() calls put_device(&stm->dev) to release allocated memory (in stm_device_release()) on error paths. However, after that, the freed memory stm is released again, resulting in a double free bug. There is a similar issue in th

Re: [PATCH 19/24] dt-bindings: spi: spi-mt65xx: add support for MT8516

On Tue, Apr 16, 2019 at 10:25 AM lei liu wrote: > > On Tue, 2019-04-16 at 09:55 +0200, Matthias Brugger wrote: > > > > On 23/03/2019 22:16, Fabien Parent wrote: > > > Add binding documentation of spi-mt65xx for MT8516 SoC. > > > > > > Signed-off-by: Fabien Parent > > > --- > > > Documentation/de

Re: [PATCH] ntp: Allow TAI-UTC offset to be set to zero

On Wed, Apr 17, 2019 at 11:00:23AM +0200, Ondrej Mosnacek wrote: > On Wed, Apr 17, 2019 at 10:48 AM Miroslav Lichvar wrote: > > Change the ADJ_TAI check to accept zero as a valid TAI-UTC offset in > > order to allow setting it back to the initial value. > Thanks for sending the patch! Maybe you (

[tip:x86/asm] x86/build/vdso: Add FORCE to the build rule of %.so

Commit-ID: 3c454f47e67bf5a65dc892cd50221a7de695870f Gitweb: https://git.kernel.org/tip/3c454f47e67bf5a65dc892cd50221a7de695870f Author: Masahiro Yamada AuthorDate: Wed, 3 Apr 2019 17:30:12 +0900 Committer: Ingo Molnar CommitDate: Thu, 18 Apr 2019 10:05:34 +0200 x86/build/vdso: Add FORC

Re: [PATCH 1/1] pinctrl: Add alternative way for specifying register bases

Hi, Light I knew your idea, but the patch really depends on a separate patch about the update of the corresponding dt-binding document for your newly added properties. You can find out dt-binding document pinctrl-mt8183.txt in linux-pinctrl.git branch for-next that is just being merged two weeks a

Re: [PATCH 0/5] mm: reparent slab memory on cgroup removal

Hello Roman, On Wed, Apr 17, 2019 at 02:54:29PM -0700, Roman Gushchin wrote: > There is however a significant problem with reparenting of slab memory: > there is no list of charged pages. Some of them are in shrinker lists, > but not all. Introducing of a new list is really not an option. True, i

Re: [PATCH] x86_64: Disabling read-implies-exec when the stack is executable

On Thu, 18 Apr 2019, Kees Cook wrote: > On Wed, May 11, 2016 at 5:45 AM Hector Marco-Gisbert wrote: > *thread necromancy* > > I'd still like to see this get landed. READ_IMPLIES_EXEC is way too > powerful (it impacts, for example, mmap() regions of device driver > memory, forcing drivers to not b

linux-next: Tree for Apr 18

Hi all, News: there will be no linux-next release on Friday, Monday or Thursday April 25. Changes since 20190417: The bpf-next tree gained a build failure for which I applied a patch. The drm tree still had its build failure for which I disabled a driver. The fix is in the drm-misc tree where I

Re: [PATCH 19/24] dt-bindings: spi: spi-mt65xx: add support for MT8516

On Thu, 2019-04-18 at 10:05 +0200, Fabien Parent wrote: > On Tue, Apr 16, 2019 at 10:25 AM lei liu wrote: > > > > On Tue, 2019-04-16 at 09:55 +0200, Matthias Brugger wrote: > > > > > > On 23/03/2019 22:16, Fabien Parent wrote: > > > > Add binding documentation of spi-mt65xx for MT8516 SoC. > > > >

[PATCH 4/4] crypto: sun4i-ss: fallback when length is not multiple of blocksize

sun4i-ss does not handle requests when length are not a multiple of blocksize. This patch adds a fallback for that case. Fixes: 6298e948215f ("crypto: sunxi-ss - Add Allwinner Security System crypto accelerator") Signed-off-by: Corentin Labbe --- drivers/crypto/sunxi-ss/sun4i-ss-cipher.c | 57 +

Re: Support for 2D engines/blitters in V4L2 and DRM

On Wed, Apr 17, 2019 at 08:10:15PM +0200, Paul Kocialkowski wrote: > Hi Nicolas, > > I'm detaching this thread from our V4L2 stateless decoding spec since > it has drifted off and would certainly be interesting to DRM folks as > well! > > For context: I was initially talking about writing up supp

Re: [tip:x86/cache] x86/resctrl: Initialize a new resource group with default MBA values

Hi Boris, On 4/18/2019 15:28, Borislav Petkov wrote: On Thu, Apr 18, 2019 at 03:03:35PM +0800, Xiaochen Shen wrote: In my opinion, this newline is unnecessary. Thank you. See commit message: [ bp: Add newlines between code blocks for better readability. ] I got this commit message an

Re: [PATCH v4 07/16] locking/rwsem: Implement lock handoff to prevent lock starvation

On Wed, Apr 17, 2019 at 12:39:19PM -0400, Waiman Long wrote: > On 04/17/2019 04:05 AM, Peter Zijlstra wrote: > > So what is wrong with the below? > > > > --- a/include/linux/sched/wake_q.h > > +++ b/include/linux/sched/wake_q.h > > @@ -51,6 +51,11 @@ static inline void wake_q_init(struct wa > >

Re: [tip:x86/cache] x86/resctrl: Initialize a new resource group with default MBA values

On Thu, Apr 18, 2019 at 04:20:57PM +0800, Xiaochen Shen wrote: > Should I submit a separate fixing patch for __init_one_rdt_domain()? You don't have to send a separate patch just for removing an excessive newline. Simply next time someone is touching the code around there, that newline can be remo

Re: [PATCH 04/12] dma-buf: add optional invalidate_mappings callback v5

Am 18.04.19 um 10:08 schrieb Daniel Vetter: > On Wed, Apr 17, 2019 at 09:13:22PM +0200, Christian König wrote: >> Am 17.04.19 um 21:07 schrieb Daniel Vetter: >>> On Tue, Apr 16, 2019 at 08:38:33PM +0200, Christian König wrote: Each importer can now provide an invalidate_mappings callback.

ext4: avoid drop reference to iloc.bh twice

The reference to iloc.bh has been dropped in ext4_mark_iloc_dirty. However, the reference is dropped again if error occurs during ext4_handle_dirty_metadata, which may result in use-after-free bugs. Fixes: fb265c9cb49e("ext4: add ext4_sb_bread() to disambiguate ENOMEM cases") Signed-off-by: Pan B

[PATCH v2 2/2] arm64: dts: allwinner: a64-oceanic-5205-5inmfd: Enable GT911 CTP

Goodix GT911 CTP is bound with Oceanic 5205 5inMFD board. The CTP connected to board with, - SDA, SCK from i2c0 - GPIO-LD0 as AVDD28 supply - PH4 gpio as interrupt pin - PH11 gpio as reset pin - X axis is inverted - Y axis is inverted Signed-off-by: Jagan Teki --- Changes for v2: - drop i2c1, bi

[PATCH v2 1/2] arm64: dts: allwinner: a64-amarula-relic: Add GT5663 CTP node

Add Goodix GT5663 capacitive touch controller node on Amarula A64-Relic board. The CTP connected to board with, - SDA, SCK from i2c1 - GPIO-LD0 as AVDD28 supply - PH4 gpio as interrupt pin - PH8 gpio as reset pin - X axis is inverted - Y axis is inverted Signed-off-by: Jagan Teki --- Changes for

[PATCH 1/2] arm64: dts: allwinner: a64: Add pinmux setting for CSI MCLK on PE1

Some camera modules have the SoC feeding a master clock to the sensor instead of having a standalone crystal. This clock signal is generated from the clock control unit and output from the CSI MCLK function of pin PE1. Add a pinmux setting for it for camera sensors to reference. Signed-off-by: Ja

[PATCH 2/2] arm64: dts: allwinner: a64-amarula-relic: Add OV5640 camera node

Amarula A64-Relic board by default bound with OV5640 camera, so add support for it with below pin information. - PE13, PE12 via i2c-gpio bitbanging - CLK_CSI_MCLK as external clock - PE1 as external clock pin muxing - ALDO1 as AVDD supply - DLDO3 as DOVDD supply - ELDO3 as DVDD supply - PE14 gpio

Re: [PATCH v4 08/16] locking/rwsem: Make rwsem_spin_on_owner() return owner state

On Wed, Apr 17, 2019 at 02:29:02PM -0400, Waiman Long wrote: > On 04/17/2019 08:47 AM, Peter Zijlstra wrote: > >> > >> enum owner_state { > >>OWNER_NULL = 1 << 0, > >>OWNER_WRITER= 1 << 1, > >>OWNER_READER= 1 << 2, > >>OWNER_NONSPINNABLE = 1

[tip:x86/urgent] x86/mm/KASLR: Fix the size of the direct mapping section

Commit-ID: ec3937107ab43f3e8b2bc9dad95710043c462ff7 Gitweb: https://git.kernel.org/tip/ec3937107ab43f3e8b2bc9dad95710043c462ff7 Author: Baoquan He AuthorDate: Thu, 4 Apr 2019 10:03:13 +0800 Committer: Borislav Petkov CommitDate: Thu, 18 Apr 2019 10:42:58 +0200 x86/mm/KASLR: Fix the siz

Re: [PATCH v4 09/16] locking/rwsem: Ensure an RT task will not spin on reader

On Wed, Apr 17, 2019 at 02:47:07PM -0400, Waiman Long wrote: > >> @@ -566,13 +573,28 @@ static bool rwsem_optimistic_spin(struct > >> rw_semaphore *sem) > >>} > >> > >>/* > >> - * When there's no owner, we might have preempted between the > >> - * owne

Re: [PATCH v2 2/3] dmaengine: imx-sdma: Only check ratio on parts that support 1:1

Acked-by: Robin Gong On 2019-03-29 at 15:21 +, Angus Ainslie (Purism) wrote: > On imx8mq B0 chip, AHB/SDMA clock ratio 2:1 can't be supported, > since SDMA clock ratio has to be increased to 250Mhz, AHB can't reach > to 500Mhz, so use 1:1 instead. > > To limit this change to the imx8mq for no

Re: [PATCH v4 11/16] locking/rwsem: Enable readers spinning on writer

On Wed, Apr 17, 2019 at 01:34:01PM -0400, Waiman Long wrote: > On 04/17/2019 09:56 AM, Peter Zijlstra wrote: > > On Sat, Apr 13, 2019 at 01:22:54PM -0400, Waiman Long wrote: > >> @@ -549,7 +582,7 @@ static noinline enum owner_state > >> rwsem_spin_on_owner(struct rw_semaphore *sem) > >>return

Re: [PATCH v2] panic: add an option to replay all the printk message in buffer

Hi Petr, On Thu, Apr 18, 2019 at 09:45:52AM +0200, Petr Mladek wrote: > On Thu 2019-04-18 09:00:14, Sergey Senozhatsky wrote: > > I think that PANIC_PRINT_ALL_PRINTK_MSG is a debugging option; a quite > > specific one. So people who ask the kernel to PANIC_PRINT_ALL_PRINTK_MSG > > they know what t

Re: [PATCH v2] staging: greybus: power_supply: use struct_size() helper

Oi Gustavo, Thanks for the patch, and the rebasing. On Wed 17 Apr 2019 at 19:44, Gustavo A. R. Silva wrote: Make use of the struct_size() helper instead of an open-coded version in order to avoid any potential type mistakes, in particular in the context in which this code is being used. So, r

Re: [PATCH v4 11/16] locking/rwsem: Enable readers spinning on writer

On Wed, Apr 17, 2019 at 01:45:10PM -0400, Waiman Long wrote: > On 04/17/2019 09:58 AM, Peter Zijlstra wrote: > > On Sat, Apr 13, 2019 at 01:22:54PM -0400, Waiman Long wrote: > >> +/* > >> + * Try to acquire read lock before the reader is put on wait queue. > >> + * Lock acquisition isn't allowed if

Re: [PATCH v1] perf record: collect user registers set jointly with dwarf stacks

On 17.04.2019 21:47, Arnaldo Carvalho de Melo wrote: > Em Wed, Apr 17, 2019 at 08:45:08PM +0300, Alexey Budankov escreveu: >> Hi Arnaldo, >> >> On 17.04.2019 18:48, Arnaldo Carvalho de Melo wrote: >>> On April 17, 2019 11:40:02 AM GMT-03:00, Jiri Olsa wrote: On Wed, Apr 17, 2019 at 11:35:42AM

Re: [v2 RFC PATCH 0/9] Another Approach to Use PMEM as NUMA Node

On Wed 17-04-19 13:43:44, Yang Shi wrote: [...] > And, I'm wondering whether this optimization is also suitable to general > NUMA balancing or not. If there are convincing numbers then this should be a preferable way to deal with it. Please note that the number of promotions is not the only metric

[PATCH v1 3/4] Bluetooth: btmtksdio: Fix hdev->stat.byte_rx accumulation

From: Sean Wang Accumulate hdev->stat.byte_rx only for valid packets as btmtkuart doing. Signed-off-by: Sean Wang --- drivers/bluetooth/btmtksdio.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/bluetooth/btmtksdio.c b/drivers/bluetooth/btmtksdio.c index 9c123a

[patch V2 19/29] lockdep: Simplify stack trace handling

Replace the indirection through struct stack_trace by using the storage array based interfaces and storing the information is a small lockdep specific data structure. Signed-off-by: Thomas Gleixner --- include/linux/lockdep.h |9 +++-- kernel/locking/lockdep.c | 44 +++

[patch V2 27/29] lib/stackdepot: Remove obsolete functions

No more users of the struct stack_trace based interfaces. Signed-off-by: Thomas Gleixner Acked-by: Alexander Potapenko --- include/linux/stackdepot.h |4 lib/stackdepot.c | 20 2 files changed, 24 deletions(-) --- a/include/linux/stackdepot.h +++ b/inc

[patch V2 15/29] dm persistent data: Simplify stack trace handling

Replace the indirection through struct stack_trace with an invocation of the storage array based interface. This results in less storage space and indirection. Signed-off-by: Thomas Gleixner Cc: dm-de...@redhat.com Cc: Mike Snitzer Cc: Alasdair Kergon --- drivers/md/persistent-data/dm-block-ma

[patch V2 22/29] tracing: Make ftrace_trace_userstack() static and conditional

It's only used in trace.c and there is absolutely no point in compiling it in when user space stack traces are not supported. Signed-off-by: Thomas Gleixner Cc: Steven Rostedt --- kernel/trace/trace.c | 14 -- kernel/trace/trace.h |8 2 files changed, 8 insertions(+),

[PATCH v1 4/4] Bluetooth: btmtksdio: Add runtime PM support to SDIO based Bluetooth

From: Sean Wang Add runtime PM support to btmtksdio. With this way, there will be the benefit of the device entering the more power saving state once it is been a while data traffic is idle. Signed-off-by: Sean Wang --- drivers/bluetooth/btmtksdio.c | 144 ++ 1

[patch V2 26/29] stacktrace: Remove obsolete functions

No more users of the struct stack_trace based interfaces. Remove them. Remove the macro stubs for !CONFIG_STACKTRACE as well as they are pointless because the storage on the call sites is conditional on CONFIG_STACKTRACE already. No point to be 'smart'. Signed-off-by: Thomas Gleixner --- includ

Re: [PATCH v3 0/3] Fix jack detection for Chromebook Pixel

On Mon, Apr 15, 2019 at 01:45:56PM -0600, Fletcher Woodruff wrote: > Headphone/mic jack detection doesn't work on the Chromebook Pixel 2015. > > This patch changes the irq implementation to support polarity flipping > and fixes the configuration code so that correct GPIO pins are read > from ACPI.

[PATCH v1 0/4] Add a couple of enhancements to btmtksdio

From: Sean Wang First three are all minor changes and the final one adds a runtime pm support to enter a lower power state for decreasing power dissipation when there is idle traffic in SDIO transport for a while. Sean Wang (4): Bluetooth: btmtksdio: Drop newline with bt_dev logging macros B

[PATCH v1 1/4] Bluetooth: btmtksdio: Drop newline with bt_dev logging macros

From: Sean Wang bt_dev logging macros already include a newline at each output so drop these unnecessary additional newlines in the driver. Signed-off-by: Sean Wang --- drivers/bluetooth/btmtksdio.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/bluetooth/btm

[PATCH v1 2/4] Bluetooth: btmtksdio: Add a bit definition for CHLPCR

From: Sean Wang Add a register bit definition about CHLPCR bit 8 because the bit is quite different in the meaning between reading and writing that bit. The patch adds a definition particularly for the bit read to avoid the confusion about using write definition to read the bit. Signed-off-by:

Re: [PATCH] ntp: Allow TAI-UTC offset to be set to zero

On Thu, 18 Apr 2019, Miroslav Lichvar wrote: > On Wed, Apr 17, 2019 at 11:00:23AM +0200, Ondrej Mosnacek wrote: > > On Wed, Apr 17, 2019 at 10:48 AM Miroslav Lichvar > > wrote: > > > Change the ADJ_TAI check to accept zero as a valid TAI-UTC offset in > > > order to allow setting it back to the i

Re: [PATCH v4 11/16] locking/rwsem: Enable readers spinning on writer

On Wed, Apr 17, 2019 at 01:51:24PM -0400, Waiman Long wrote: > On 04/17/2019 10:05 AM, Peter Zijlstra wrote: > > On Sat, Apr 13, 2019 at 01:22:54PM -0400, Waiman Long wrote: > >> @@ -650,6 +686,33 @@ __rwsem_down_read_failed_common(struct rw_semaphore > >> *sem, int state) > >>struct rwsem_wai

[PATCH] mfd: intel_quark_i2c_gpio: Adjust IOT2000 matching

From: Su Bao Cheng Since there are more IOT2040 variants with identical hardware but different asset tags, the asset tag matching should be adjusted to support them. For the board name "SIMATIC IOT2000", currently there are 2 types of hardware, IOT2020 and IOT2040. Both are identical regarding t

[PATCH] serial: 8250_exar: Adjust IOT2000 matching

From: Su Bao Cheng Since there are more IOT2040 variants with identical hardware but different asset tags, the asset tag matching should be adjusted to support them. As only the IOT2040 variants have the Exar chip on board, matching on their board name is enough. In the future there will be no o

[GIT PULL] afs: Fixes

Hi Linus, Could you pull these afs fixes please? There are five: (1) Stop using the deprecated get_seconds(). (2) Don't make tracepoint strings const as the section they go in isn't read-only. (3) Differentiate failure due to unmarshalling from other failure cases - we shouldn't a

Re: [PATCH V2 0/3] Introduce Thermal Pressure

On Wednesday 17 Apr 2019 at 20:29:32 (+0200), Ingo Molnar wrote: > > * Thara Gopinath wrote: > > > > > On 04/17/2019 01:36 AM, Ingo Molnar wrote: > > > > > > * Thara Gopinath wrote: > > > > > >> The test results below shows 3-5% improvement in performance when > > >> using the third solution

[PATCH 0/2] gpio: sch: Interrupt support

See patches for details. Two things I'm not 100% sure about: - Should we enable interrupts for all sch variants the driver support, or only the Quark where I was able to validate it (and where I found documentation for)? - Is there a better way to hook into the SCI? Yes, GPIO events will

[PATCH 1/2] gpio: sch: Remove write-only core_base

From: Jan Kiszka Signed-off-by: Jan Kiszka --- drivers/gpio/gpio-sch.c | 5 - 1 file changed, 5 deletions(-) diff --git a/drivers/gpio/gpio-sch.c b/drivers/gpio/gpio-sch.c index c333046d02b8..fb143f28c386 100644 --- a/drivers/gpio/gpio-sch.c +++ b/drivers/gpio/gpio-sch.c @@ -23,7 +23,6 @@

[PATCH 2/2] gpio: sch: Add interrupt support

From: Jan Kiszka Validated on the Quark platform, this adds interrupt support on rising and/or falling edges. Signed-off-by: Jan Kiszka --- drivers/gpio/gpio-sch.c | 142 +--- 1 file changed, 135 insertions(+), 7 deletions(-) diff --git a/drivers/gp

Re: fs/proc: Crash observed in next_tgid (fs/proc/base.c)

NB: it is preferable to avoid top-posting here. On 17/04/2019 18:58, Jitendra Sharma wrote: > Kernel version: 4.14.83 NB2: 4.14.83 is obsolete, as it stands 2255 patches behind the tip of linux-4.14.y (though only 4 patches in fs/proc). NB3: 4.14 is 108499(!!) patches behind v5.1-rc5 (latest re

Re: [PATCH v1] ARM: tegra: cpuidle: Handle tick broadcasting within cpuidle core on Tegra20/30

On Sun, Feb 24, 2019 at 06:21:14PM +0300, Dmitry Osipenko wrote: > Tegra20/30 drivers do not handle the tick_broadcast_enter() error which > potentially could happen when CPU timer isn't permitted to be stopped. > Let's just move out the broadcasting to the CPUIDLE core by setting the > respective

Re: [PATCH v3 2/3] HID: quirks: Fix keyboard + touchpad on Lenovo Miix 630 for DT

On Mon, Apr 15, 2019 at 6:11 PM Jeffrey Hugo wrote: > > Following up on commit 2bafa1e96254 ("HID: quirks: Fix keyboard + touchpad > on Lenovo Miix 630"), the devicetree (DT) identifier for the combo keyboard > + touchpad device is "elan,combo400-i2c", which differs from the ACPI ID, > thus if we

Re: [PATCH v1 2/4] clone: add CLONE_PIDFD

On Wed, Apr 17, 2019 at 04:22:54PM +0200, Oleg Nesterov wrote: > On 04/16, Christian Brauner wrote: > > > > + if (clone_flags & CLONE_PIDFD) { > > + retval = pidfd_create(pid, &pidfdf); > > + if (retval < 0) > > + goto bad_fork_free_pid; > > + pidfd

Re: [PATCH v1 0/4] memory: tegra: Fix memory arbitration programming

On Fri, Apr 12, 2019 at 01:12:46AM +0300, Dmitry Osipenko wrote: > Hello, this series properly addresses the bugged memory arbitration > programming and in result the previous suspend-resume workaround change > is reverted as it was not entirely correct. > > Dmitry Osipenko (4): > memory: tegra:

[RESEND PATCH v5 2/3] pwm: stm32-lp: Add power management support

Add suspend/resume PM sleep ops. When going to low power, enforce the PWM channel isn't active. Let the PWM consumers disable it during their own suspend sequence. Only perform a check here, and handle the pinctrl states. See [1]. [1] https://lkml.org/lkml/2019/2/5/770 Signed-off-by: Fabrice Gasni

Re: [PATCH v1] ARM: dts: tegra30: Add ACTMON node

On Fri, Apr 12, 2019 at 01:30:42AM +0300, Dmitry Osipenko wrote: > Add ACTMON node to the Tegra30's device-tree. > > Signed-off-by: Dmitry Osipenko > --- > arch/arm/boot/dts/tegra30.dtsi | 11 +++ > 1 file changed, 11 insertions(+) Applied to for-5.2/arm/dt, thanks. Thierry signature

[PATCH v2] nds32: remove unused generic-y += cmpxchg-local.h

NDS32 is the only architecture that creates , which is not included by anyone. Signed-off-by: Masahiro Yamada --- Changes in v2: - Fix a typo in commit log arch/nds32/include/asm/Kbuild | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/nds32/include/asm/Kbuild b/arch/nds32/include/asm/

Re: [PATCH v2] block: bio_map_user_iov should not be limited to BIO_MAX_PAGES

On 18/04/19 11:29, Ming Lei wrote: > On Thu, Apr 18, 2019 at 10:42:21AM +0200, Paolo Bonzini wrote: >> On 18/04/19 04:19, Ming Lei wrote: >>> Hi Paolo, >>> >>> On Wed, Apr 17, 2019 at 01:52:07PM +0200, Paolo Bonzini wrote: Because bio_kmalloc uses inline iovecs, the limit on the number of entr

[RESEND PATCH v5 0/3] Add PM support to STM32 LP Timer drivers

This patch series adds power management support for STM32 LP Timer: - PWM driver - Document the pinctrl states for sleep mode It also adds device link between the PWM consumer and the PWM provider. This allows proper sequencing for suspend/resume (e.g. user will likely do a pwm_disable() before th

[RESEND PATCH v5 3/3] pwm: core: add consumer device link

Add a device link between the PWM consumer and the PWM provider. This enforces the PWM user to get suspended before the PWM provider. It allows proper synchronization of suspend/resume sequences: the PWM user is responsible for properly stopping PWM, before the provider gets suspended: see [1]. Add

Re: [PATCH v3 1/3] dt-bindings: input: add Elan 400 combo keyboard/touchpad over i2c

On Mon, Apr 15, 2019 at 6:11 PM Jeffrey Hugo wrote: > > The Elan 400 combo keyboard/touchpad over i2c device is a distinct device > from the Elan 400 standalone touchpad device. The combo device has been > found in the Lenovo Miix 630 and HP Envy x2 laptops. > > Signed-off-by: Jeffrey Hugo > ---

[PATCH] docs: hwmon: convert three docs to ReST format

Those three new drivers were missed on the initial conversion to ReST format. So: - Rename them to .rst; - Add them to the hwmon index.rst index; - add some blank lines at the "Supported systems:" part, in order to allow Sphinx to properly identify new lines, suppressing warnings and avoid it

RE: IOMMU Page faults when running DMA transfers from PCIe device

From: Jerome Glisse > Sent: 16 April 2019 16:33 ... > I am no expert but i am guessing your FPGA set the request field in the > PCIE TLP write packet to 00:00.0 and this might work when IOMMU is off but > might not work when IOMMU is on ie when IOMMU is on your device should set > the request field

Re: [PATCH] nds32: add vmlinux.lds and vdso.so to .gitignore

Hi Greentime, On Wed, Apr 3, 2019 at 5:39 PM Masahiro Yamada wrote: > > These are build artifacts, which should be ignored by git. > > Signed-off-by: Masahiro Yamada > --- Ping ? > > arch/nds32/kernel/.gitignore | 1 + > arch/nds32/kernel/vdso/.gitignore | 1 + > 2 files changed, 2 inser

Re: [PATCH] nds32: vdso: fix and clean-up Makefile

Hi Greentime, On Wed, Apr 3, 2019 at 5:38 PM Masahiro Yamada wrote: > > - $(call if_changed,...) must have FORCE as a prerequisite > > - vdso.lds is a generated file, so it should be prefixed with > $(obj)/ instead of $(src)/. > > - cmd_vdsosym is a one-liner rule, so the assignment with '=' >

[RESEND PATCH v5 1/3] dt-bindings: pwm-stm32-lp: document pinctrl sleep state

Add documentation for pinctrl sleep state on STM32 LPTimer PWM. Reviewed-by: Rob Herring Signed-off-by: Fabrice Gasnier --- Documentation/devicetree/bindings/pwm/pwm-stm32-lp.txt | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/Documentation/devicetree/bindings/pwm/p

Re: [PATCH V3 1/2] ASoC: fsl_asrc: replace the process_option table with function

Hi > > On Thu, Apr 18, 2019 at 08:50:48AM +, S.j. Wang wrote: > > > And this is according to IMX6DQRM: > > > Limited support for the case when output sampling rates is > > > between 8kHz and 30kHz. The limitation is the supported ratio > > > (Fsin/Fsout) range as between 1/24 to 8

Re: [PATCH v2 1/2] power: reset: nvmem-reboot-mode: use NVMEM as reboot mode write interface

Hi, On Thu, Apr 18, 2019 at 09:29:08AM +0300, Nandor Han wrote: > On 4/18/19 12:56 AM, Sebastian Reichel wrote: > > On Thu, Apr 11, 2019 at 05:54:09AM +, Han Nandor wrote: > > > Add a new reboot mode write interface that is using an NVMEM cell > > > to store the reboot mode magic. > > > > > >

Re: [PATCH V3 3/3] thermal/cpu-cooling: Update thermal pressure in case of a maximum frequency capping

On Tuesday 16 Apr 2019 at 15:38:41 (-0400), Thara Gopinath wrote: > diff --git a/drivers/thermal/cpu_cooling.c b/drivers/thermal/cpu_cooling.c > @@ -177,6 +178,9 @@ static int cpufreq_thermal_notifier(struct notifier_block > *nb, > > if (policy->max > clipped_freq) >

Re: [PATCH] x86/mm/mem_encrypt: fix a crash with kmemleak_scan

On Thu, Apr 18, 2019 at 09:45:10AM +0200, Borislav Petkov wrote: > On Tue, Apr 16, 2019 at 08:38:30PM -0400, Qian Cai wrote: > > kmemleak_init() will register the data/bss sections (only register > > .data..ro_after_init if not within .data) and then kmemleak_scan() will scan > > those address and

Re: [PATCH 3/3] Documentation: devicetree: add PPMU events description

Hi Chanwoo, On 4/17/19 10:26 AM, Chanwoo Choi wrote: > Hi Lukasz, > > On 19. 4. 17. 오후 4:48, Lukasz Luba wrote: >> Extend the documenation by events description with new 'event-data-type' >> field. Add example how the event might be defined in DT. >> >> Signed-off-by: Lukasz Luba >> --- >> ...

[PATCH] docs: core-api: fix broken references for div64.c and gcd.c

Those files were moved to lib/math. Fixes: 9635bad21596 ("lib: Move mathematic helpers to separate folder") Signed-off-by: Mauro Carvalho Chehab --- Documentation/core-api/kernel-api.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/core-api/kernel-api.rst

Re: [PATCH v3 2/3] HID: quirks: Fix keyboard + touchpad on Lenovo Miix 630 for DT

Hi, On 18-04-19 11:34, Benjamin Tissoires wrote: On Mon, Apr 15, 2019 at 6:11 PM Jeffrey Hugo wrote: Following up on commit 2bafa1e96254 ("HID: quirks: Fix keyboard + touchpad on Lenovo Miix 630"), the devicetree (DT) identifier for the combo keyboard + touchpad device is "elan,combo400-i2c",

[PATCH] ARM: vdso: use $(LD) instead of $(CC) to link VDSO

We use $(LD) to link vmlinux, modules, decompressors, etc. VDSO is the only exceptional case where $(CC) is used as the linker driver, but I do not know why we need to do so. VDSO uses a special linker script, and does not link standard libraries at all. I changed the Makefile to use $(LD) rather

  1   2   3   4   5   6   7   8   9   10   >