linux-next: manual merge of the scsi tree with the block tree

2019-04-14 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the scsi tree got a conflict in: drivers/scsi/sd.c between commit: c92e2f04b359 ("block: disk_events: introduce event flags") from the block tree and commit: 21e6ba3f0e02 ("scsi: sd: Rely on the driver core for asynchronous probing") d16ece577bf2

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

2019-04-14 Thread Chris Chiu
The touchpad of the ASUS laptops E403NA, X540NA, X541NA are not responsive after suspend/resume. The following error message shows after resume. i2c_hid i2c-ELAN1200:00: failed to reset device. On these laptops, the touchpad interrupt is connected via a GPIO pin which is controlled by Intel

Re: [PATCH 1/1] arm: mm: Export __sync_icache_dcache() for xen-privcmd

2019-04-14 Thread Christoph Hellwig
On Sat, Apr 13, 2019 at 06:30:52PM +0200, Heinrich Schuchardt wrote: > This patch avoids > ERROR: "__sync_icache_dcache" [drivers/xen/xen-privcmd.ko] undefined! > observed when compiling v4.19.34. > > The xen-privcmd driver, which can be modular, calls set_pte_at() > which in turn may call

Re: [PATCH v2 1/3] RISC-V: Add separate asm/encoding.h for spec related defines

2019-04-14 Thread Christoph Hellwig
On Sat, Apr 13, 2019 at 03:38:35PM +, Anup Patel wrote: > It's better to have all RISC-V spec related defines in one place > so this patch adds separate asm/encoding.h for such defines which > can be included in assembly as well as C code. As per the discussion of version 1 on Saturday I

Re: [PATCH v2] sched/clock: Prevent generic sched_clock wrap caused by tick_freeze()

2019-04-14 Thread Chang-An Chen
Hi, This is just a gentle ping for this patch. On Fri, 2019-03-29 at 10:59 +0800, Chang-An Chen wrote: > tick_freeze() introduced by suspend-to-idle in commit 124cf9117c5f > ("PM / sleep: Make it possible to quiesce timers during suspend-to-idle") > will use timekeeping_suspend() instead of

Re: [PATCH v2 06/26] PCI: keystone: Move initializations to appropriate places

2019-04-14 Thread Kishon Vijay Abraham I
Hi Bjorn, On 13/04/19 8:00 PM, Bjorn Helgaas wrote: > On Mon, Mar 25, 2019 at 02:04:41PM +0530, Kishon Vijay Abraham I wrote: >> No functional change. Move host specific platform_get_resource to >> ks_add_pcie_port and the common platform_get_resource (applicable >> to both host and endpoint) to

Re: [PATCH v3 02/26] PCI: keystone: Cleanup error_irq configuration

2019-04-14 Thread Kishon Vijay Abraham I
Hi Bjorn, On 13/04/19 7:33 PM, Bjorn Helgaas wrote: > Hi Kishon, > > On Mon, Mar 25, 2019 at 03:09:23PM +0530, Kishon Vijay Abraham I wrote: >> pci-keystone driver uses irq_of_parse_and_map to get irq number of >> error_irq. Use platform_get_irq instead and move platform_get_irq() >> and

RE: [PATCH] MAINTAINERS: normalize Michael Hennerich's email address

2019-04-14 Thread Hennerich, Michael
> -Original Message- > From: Lukas Bulwahn [mailto:lukas.bulw...@gmail.com] > Sent: Samstag, 13. April 2019 11:26 > To: Hennerich, Michael > Cc: linux-kernel@vger.kernel.org; Lukas Bulwahn > Subject: [PATCH] MAINTAINERS: normalize Michael Hennerich's email address > > MAINTAINERS

Re: [PATCH v4 1/9] clkdev: Hold clocks_mutex while iterating clocks list

2019-04-14 Thread Matti Vaittinen
On Fri, Apr 12, 2019 at 11:31:42AM -0700, Stephen Boyd wrote: > We recently introduced a change to support devm clk lookups. That change > introduced a code-path that used clk_find() without holding the > 'clocks_mutex'. Unfortunately, clk_find() iterates over the 'clocks' > list and so we need to

Re: Linux 5.1-rc5

2019-04-14 Thread Christoph Hellwig
Can we please have the page refcount overflow fixes out on the list for review, even if it is after the fact? On Sun, Apr 14, 2019 at 03:40:47PM -0700, Linus Torvalds wrote: > Nothing in here makes me feel uncomfortable about this release cycle > so far. Knock wood. > > Shortlog appended with an

Re: [PATCH v3 3/4] arm64: kdump: support more than one crash kernel regions

2019-04-14 Thread Mike Rapoport
Hi, On Mon, Apr 15, 2019 at 10:05:18AM +0800, Chen Zhou wrote: > Hi Mike, > > On 2019/4/14 20:10, Mike Rapoport wrote: > >> > >> solution A:phys_addr_t start[INIT_MEMBLOCK_RESERVED_REGIONS * 2]; > >>phys_addr_t end[INIT_MEMBLOCK_RESERVED_REGIONS * 2]; > >> start, end is

Re: [PATCH v3 3/4] arm64: kdump: support more than one crash kernel regions

2019-04-14 Thread Mike Rapoport
On Mon, Apr 15, 2019 at 10:27:30AM +0800, Chen Zhou wrote: > Hi Mike, > > On 2019/4/14 20:13, Mike Rapoport wrote: > > Hi, > > > > On Tue, Apr 09, 2019 at 06:28:18PM +0800, Chen Zhou wrote: > >> After commit (arm64: kdump: support reserving crashkernel above 4G), > >> there may be two crash

Re: misuse of fget_raw() in perf_event_get()

2019-04-14 Thread Alexei Starovoitov
On Sat, Apr 13, 2019 at 10:02:42PM +0100, Al Viro wrote: > What's the point of using fget_raw(), if you do > _not_ accept O_PATH descriptors? That should be fget()... I think you're talking about commit e03e7ee34fdd ("perf/bpf: Convert perf_event_array to use struct file") I don't really

linux-next: manual merge of the tip tree with the arm64 tree

2019-04-14 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the tip tree got a conflict in: mm/kasan/Makefile between commit: e2092740b723 ("kasan: Makefile: Replace -pg with CC_FLAGS_FTRACE") from the arm64 tree and commit: 57b78a62e7f2 ("x86/uaccess, kasan: Fix KASAN vs SMAP") from the tip tree. I fixed

linux-next: manual merge of the tip tree with the arm64 tree

2019-04-14 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the tip tree got a conflict in: arch/s390/include/asm/Kbuild between commit: fdcd06a8ab77 ("arch: Use asm-generic header for asm/mmiowb.h") from the arm64 tree and commit: 46ad0840b158 ("locking/rwsem: Remove arch specific rwsem files") from the tip

Re: [PATCH v2 01/21] docs/memory-barriers.txt: Rewrite "KERNEL I/O BARRIER EFFECTS" section

2019-04-14 Thread Benjamin Herrenschmidt
On Fri, 2019-04-12 at 14:17 +0100, Will Deacon wrote: > > +the same CPU thread to a particular device will arrive in program > +order. > + > + 2. A writeX() by a CPU thread to the peripheral will first wait for the > +completion of all prior writes to memory either

Re: [PATCH v5 0/5] init: Do not select DEBUG_KERNEL by default

2019-04-14 Thread Kees Cook
On Sat, Apr 13, 2019 at 3:44 PM Sinan Kaya wrote: > > CONFIG_DEBUG_KERNEL has been designed to just enable Kconfig options. > Kernel code generatoin should not depend on CONFIG_DEBUG_KERNEL. > > Proposed alternative plan: let's add a new symbol, something like > DEBUG_MISC ("Miscellaneous debug

Re: [PATCH v4 2/3] csky: Add support for perf registers sampling

2019-04-14 Thread Guo Ren
Hi Mao, On Thu, Apr 11, 2019 at 03:45:00PM +0800, Mao Han wrote: > This patch implements the perf registers sampling and validation API > for csky arch. The valid registers and their register ID are defined in > perf_regs.h. Perf tool can backtrace in userspace with unwind library > and the

[PATCH 1/2] doc: Fixup definition of rcupdate.rcu_task_stall_timeout

2019-04-14 Thread Zhenzhong Duan
A positive value of rcupdate.rcu_task_stall_timeout is an interval in seconds rather than jiffies. Signed-off-by: Zhenzhong Duan --- Documentation/RCU/stallwarn.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/RCU/stallwarn.txt

[PATCH 2/2] doc: kernel-parameters.txt: fix documentation of nmi_watchdog parameter

2019-04-14 Thread Zhenzhong Duan
As stated in "Documentation/lockup-watchdogs.txt:line 22", the default behaivor after 'hardlockup' is to stay locked up rather than panic. Signed-off-by: Zhenzhong Duan --- Documentation/admin-guide/kernel-parameters.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH v3 net-next 18/24] net: dsa: sja1105: Add support for traffic through standalone ports

2019-04-14 Thread Andrew Lunn
> It fails to decode the frames, obviously. But so does any other EtherType. > Florian was hinting > (https://lwn.net/ml/netdev/b52f4cdf-edcf-0757-1d6e-d4a831ec7...@gmail.com/) > at the recent pull requests submitted to tcpdump and libpcap that make > it possible to decode based on the string in

linux-next: manual merge of the block tree with Linus' tree

2019-04-14 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the block tree got a conflict in: include/linux/bvec.h between commit: 1200e07f3ad4 ("block: don't use for-inside-for in bio_for_each_segment_all") from Linus' tree and commit: 52d52d1c98a9 ("block: only allow contiguous page structs in a bio_vec")

linux-next: manual merge of the block tree with Linus' tree

2019-04-14 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the block tree got a conflict in: block/bfq-iosched.c between commit: eed47d19d936 ("block, bfq: fix use after free in bfq_bfqq_expire") from Linus' tree and commit: 636b8fe86bed ("block, bfq: fix some typos in comments") from the block tree. I

Re: [PATCH] crypto: testmgr - allocate buffers with __GFP_COMP

2019-04-14 Thread Herbert Xu
On Sun, Apr 14, 2019 at 07:24:12PM -0700, Matthew Wilcox wrote: > On Thu, Apr 11, 2019 at 01:32:32PM -0700, Kees Cook wrote: > > > @@ -156,7 +156,8 @@ static int __testmgr_alloc_buf(char *buf[XBUFSIZE], > > > int order) > > > int i; > > > > > > for (i = 0; i < XBUFSIZE; i++) { > >

Re: [PATCH] printk: tie printk_once / printk_deferred_once into .data.once for reset

2019-04-14 Thread Sergey Senozhatsky
On (04/12/19 22:11), Paul Gortmaker wrote: > In commit b1fca27d384e ("kernel debug: support resetting WARN*_ONCE") > we got the opportunity to reset state on the one shot messages, > without having to reboot. Didn't know that. > However printk_once (printk_deferred_once) live in a different file

Re: [PATCH v3 3/4] arm64: kdump: support more than one crash kernel regions

2019-04-14 Thread Chen Zhou
Hi Mike, On 2019/4/14 20:13, Mike Rapoport wrote: > Hi, > > On Tue, Apr 09, 2019 at 06:28:18PM +0800, Chen Zhou wrote: >> After commit (arm64: kdump: support reserving crashkernel above 4G), >> there may be two crash kernel regions, one is below 4G, the other is >> above 4G. >> >> Crash dump

Re: [PATCH] crypto: testmgr - allocate buffers with __GFP_COMP

2019-04-14 Thread Matthew Wilcox
On Thu, Apr 11, 2019 at 01:32:32PM -0700, Kees Cook wrote: > > @@ -156,7 +156,8 @@ static int __testmgr_alloc_buf(char *buf[XBUFSIZE], int > > order) > > int i; > > > > for (i = 0; i < XBUFSIZE; i++) { > > - buf[i] = (char *)__get_free_pages(GFP_KERNEL, order); > > +

linux-next: manual merge of the wireless-drivers-next tree with the wireless-drivers tree

2019-04-14 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the wireless-drivers-next tree got a conflict in: drivers/net/wireless/intel/iwlwifi/pcie/drv.c between commits: 0d5bad14226a ("iwlwifi: rename structs to fit the new names") 972d8e137779 ("iwlwifi: add new 0x2723/0x2080 card for 22000") from the

Re: [PATCH v3 3/4] arm64: kdump: support more than one crash kernel regions

2019-04-14 Thread Chen Zhou
Hi Mike, On 2019/4/14 20:10, Mike Rapoport wrote: > Hi, > > On Thu, Apr 11, 2019 at 08:17:43PM +0800, Chen Zhou wrote: >> Hi Mike, >> >> This overall looks well. >> Replacing memblock_cap_memory_range() with memblock_cap_memory_ranges() was >> what i wanted >> to do in v1, sorry for don't

[RFC PATCH v4 4/4] x86/acrn: Add hypercall for ACRN guest

2019-04-14 Thread Zhao Yakui
When ACRN hypervisor is detected, the hypercall is needed so that the ACRN guest can query/config some settings. For example: it can be used to query the resources in hypervisor and manage the CPU/memory/device/ interrupt for guest operating system. Add the hypercall so that the kernel can

[RFC PATCH v4 3/4] x86/acrn: Use HYPERVISOR_CALLBACK_VECTOR for ACRN guest upcall vector

2019-04-14 Thread Zhao Yakui
Linux kernel uses the HYPERVISOR_CALLBACK_VECTOR for hypervisor upcall vector. And it is already used for Xen and HyperV. After ACRN hypervisor is detected, it will also use this defined vector to notify kernel. Co-developed-by: Jason Chen CJ Signed-off-by: Jason Chen CJ Signed-off-by: Zhao

[PATCH v4 2/4] x86: Add the support of Linux guest on ACRN hypervisor

2019-04-14 Thread Zhao Yakui
ACRN is an open-source hypervisor maintained by Linux Foundation. It is built for embedded IOT with small footprint and real-time features. Add the ACRN guest support so that it allows linux to be booted under ACRN hypervisor. Following this patch it will setup the upcall notification vector,

[RFC PATCH v4 0/4] x86: Add the support of ACRN guest under arch/x86

2019-04-14 Thread Zhao Yakui
ACRN is a flexible, lightweight reference hypervisor, built with real-time and safety-criticality in mind, optimized to streamline embedded development through an open source platform. It is built for embedded IOT with small footprint and real-time features. More details can be found in

[RFC PATCH v4 1/4] x86/Kconfig: Add new config symbol to unify conditional definition of hv_irq_callback_count

2019-04-14 Thread Zhao Yakui
Add a special Kconfig symbol X86_HV_CALLBACK_VECTOR so that the guests using the hypervisor interrupt callback counter can select and thus enable that counter. Select it when xen or hyperv support is enabled. No functional changes. Signed-off-by: Zhao Yakui Reviewed-by: Borislav Petkov ---

linux-next: manual merge of the wireless-drivers-next tree with the wireless-drivers tree

2019-04-14 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the wireless-drivers-next tree got a conflict in: drivers/net/wireless/intel/iwlwifi/iwl-trans.h between commit: 07d35b4270ef ("iwlwifi: use sync nmi in case of init flow failure") from the wireless-drivers tree and commit: 4b1831e48974 ("iwlwifi:

RE: [PATCH] MAINTAINERS: normalize Woojung Huh's email address

2019-04-14 Thread Woojung.Huh
> MAINTAINERS contains a lower-case and upper-case variant of > Woojung Huh' s email address. > > Only keep the lower-case variant in MAINTAINERS. > > Signed-off-by: Lukas Bulwahn Acked-by: Woojung Huh

[PATCH v2 1/4] power: supply: max17040: Add IRQ handler for low SOC alert

2019-04-14 Thread Matheus Castello
According datasheet max17040 has a pin for alert host for low SOC. This pin can be used as external interrupt, so we need to check for interrupts assigned for device and handle it. In hadler we are checking and storing fuel gauge registers values and send an uevent to notificate user space, so

[PATCH v2 2/4] dt-bindings: power: supply: Max17040: Add low level SOC alert threshold

2019-04-14 Thread Matheus Castello
For configure low level state of charge threshold alert signaled from max17040 we add "maxim,alert-soc-level" property. Signed-off-by: Matheus Castello --- .../power/supply/max17040_battery.txt | 24 +++ 1 file changed, 24 insertions(+) create mode 100644

[PATCH v2 3/4] power: supply: max17040: Config alert SOC low level threshold from FDT

2019-04-14 Thread Matheus Castello
For configuration of fuel gauge alert for a low level state of charge interrupt we add a function to config level threshold and a device tree binding property to set it in flatned device tree node. Now we can use "maxim,alert-soc-level" property with the values from 1 up to 32 to configure alert

[PATCH v2 4/4] power: supply: max17040: Send uevent in SOC changes

2019-04-14 Thread Matheus Castello
Notify core through power_supply_changed() in case of changes in state of charge. This is useful for user-space to efficiently update current battery level. Signed-off-by: Matheus Castello --- drivers/power/supply/max17040_battery.c | 7 +++ 1 file changed, 7 insertions(+) diff --git

Re: [PATCH] PCI: rockchip: fix bitwise operations on status and ROCKCHIP_PCIE_EP_CMD_STATUS_IS

2019-04-14 Thread Shawn Lin
On 2019/4/12 17:51, Lorenzo Pieralisi wrote: On Sat, Mar 30, 2019 at 03:09:10PM +, Colin King wrote: From: Colin Ian King Currently the bitwise operations on the u16 variable 'status' with the setting ROCKCHIP_PCIE_EP_CMD_STATUS_IS are incorrect because ROCKCHIP_PCIE_EP_CMD_STATUS_IS is

[PATCH v2 0/4] power: supply: MAX17040: Add IRQ for low level and alert SOC changes

2019-04-14 Thread Matheus Castello
This series add IRQ handler for low level SOC alert, define a devicetree binding attribute to configure the alert level threshold and check for changes in SOC for send uevents. Max17040 have a pin for alert host about low level state of charge and this alert can be configured in a threshold from

63c35ea6b8 ("x86/stacktrace: Use common infrastructure"): BUG: kernel hang in early-boot stage, last printk: early console in setup code

2019-04-14 Thread kernel test robot
Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/stacktrace commit 63c35ea6b829a0f98d307a8dec038095681ecd13 Author: Thomas Gleixner AuthorDate: Thu Apr 11 12:52:04 2019 +0200 Commit:

[tip:WIP.core/stacktrace 34/47] drivers/gpu/drm/drm_mm.c:136:3: error: implicit declaration of function 'stack_trace_snprintf'

2019-04-14 Thread kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/stacktrace head: 63c35ea6b829a0f98d307a8dec038095681ecd13 commit: 6476291d5b823a05b9c903a65a5f6e6026a02606 [34/47] drm: Simplify stacktrace handling config: i386-randconfig-a1-201915 (attached as .config) compiler:

[tip:WIP.core/stacktrace 24/47] mm/slab.c:1490:11: error: 'trace' undeclared

2019-04-14 Thread kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/stacktrace head: 63c35ea6b829a0f98d307a8dec038095681ecd13 commit: c79cc35c00e9f15a9a32a08569036cb8365c8816 [24/47] mm/slab: Simplify stack trace handling config: i386-randconfig-a1-201915 (attached as .config)

[PATCH v4 02/11] PCI: imx6: Drop imx6_pcie_wait_for_link()

2019-04-14 Thread Andrey Smirnov
All calls to imx6_pcie_wait_for_link() share the same error path and the state of PHY debug registers will already be printed there, so there's no real reason we can't just use dw_pcie_wait_for_link(). Drop imx6_pcie_wait_for_link() and replace it with dw_pcie_wait_for_link(). Signed-off-by:

[PATCH v4 05/11] PCI: dwc: imx6: Share PHY debug register definitions

2019-04-14 Thread Andrey Smirnov
Both pcie-designware.c and pci-imx6.c contain custom definitions for PHY debug registers R0/R1 and on top of that there's already a definition for R0 in pcie-designware.h. Move all of the definitions to pcie-designware.h. No functional change intended. Signed-off-by: Andrey Smirnov Reviewed-by:

[PATCH v4 03/11] PCI: imx6: Return -ETIMEOUT from imx6_pcie_wait_for_speed_change()

2019-04-14 Thread Andrey Smirnov
Change error code from EINVAL to ETIMEDOUT in imx6_pcie_wait_for_speed_change() since that error code seems more appropriate. Signed-off-by: Andrey Smirnov Reviewed-by: Lucas Stach Cc: Lorenzo Pieralisi Cc: Bjorn Helgaas Cc: Chris Healy Cc: Lucas Stach Cc: linux-kernel@vger.kernel.org Cc:

[PATCH v4 08/11] PCI: imx6: Simplify pcie_phy_poll_ack()

2019-04-14 Thread Andrey Smirnov
Simplify pcie_phy_poll_ack() by incorporating shifting into constant definition and convert the code to use 'bool'. No functional change intended. Signed-off-by: Andrey Smirnov Cc: Lorenzo Pieralisi Cc: Bjorn Helgaas Cc: Chris Healy Cc: Lucas Stach Cc: linux-kernel@vger.kernel.org Cc:

[PATCH v4 06/11] PCI: imx6: Make use of BIT() in constant definitions

2019-04-14 Thread Andrey Smirnov
Avoid using explicit left shifts and convert various definitions to use BIT() instead. No functional change intended. Signed-off-by: Andrey Smirnov Reviewed-by: Lucas Stach Cc: Lorenzo Pieralisi Cc: Bjorn Helgaas Cc: Chris Healy Cc: Lucas Stach Cc: linux-kernel@vger.kernel.org Cc:

[PATCH v4 09/11] PCI: imx6: Restrict PHY register data to 16-bit

2019-04-14 Thread Andrey Smirnov
PHY registers on i.MX6 are 16-bit wide, so we can get rid of explicit masking if we restrict pcie_phy_read/pcie_phy_write to use 'u16' instead of 'int'. No functional change intended. Signed-off-by: Andrey Smirnov Reviewed-by: Lucas Stach Cc: Lorenzo Pieralisi Cc: Bjorn Helgaas Cc: Chris

[PATCH v4 04/11] PCI: imx6: Remove PCIE_PL_PFLR_* constants

2019-04-14 Thread Andrey Smirnov
Code using these constants was removed in commit a71280722eeb ("PCI: imx6: Remove LTSSM disable workaround"). No functional change intended. Signed-off-by: Andrey Smirnov Reviewed-by: Lucas Stach Cc: Lorenzo Pieralisi Cc: Bjorn Helgaas Cc: Chris Healy Cc: Lucas Stach Cc:

[PATCH v4 01/11] PCI: imx6: Simplify imx7d_pcie_wait_for_phy_pll_lock()

2019-04-14 Thread Andrey Smirnov
Make use of regmap_read_poll_timeout() to simplify imx7d_pcie_wait_for_phy_pll_lock(). No functional change intended. Signed-off-by: Andrey Smirnov Reviewed-by: Lucas Stach Cc: Lorenzo Pieralisi Cc: Bjorn Helgaas Cc: Chris Healy Cc: Lucas Stach Cc: linux-kernel@vger.kernel.org Cc:

[PATCH v4 07/11] PCI: imx6: Simplify bit operations in PHY functions

2019-04-14 Thread Andrey Smirnov
Simplify the code by incorporating left shifts into constant defnitions as well as using FIELD_PREP/GENMASK. No functional change intended. Signed-off-by: Andrey Smirnov Reviewed-by: Lucas Stach Cc: Lorenzo Pieralisi Cc: Bjorn Helgaas Cc: Chris Healy Cc: Lucas Stach Cc:

[PATCH v4 11/11] PCI: imx6: Use usleep_range() in imx6_pcie_enable_ref_clk()

2019-04-14 Thread Andrey Smirnov
imx6_pcie_enable_ref_clk() is never called in atomic context, so there's no need to use udelay(). Replace it with usleep_range(). Signed-off-by: Andrey Smirnov Cc: Lorenzo Pieralisi Cc: Bjorn Helgaas Cc: Chris Healy Cc: Lucas Stach Cc: linux-kernel@vger.kernel.org Cc:

[PATCH v4 10/11] PCI: imx6: Use flags to indicate support for suspend

2019-04-14 Thread Andrey Smirnov
Now that driver data has flags variable that can be used to indicate quirks/features supported we can switch the code to use it instead of having a special function that does so based on variant alone. No functional change intended. Signed-off-by: Andrey Smirnov Reviewed-by: Lucas Stach Cc:

[PATCH v4 00/11] i.MX6, DesignWare PCI improvements

2019-04-14 Thread Andrey Smirnov
Everyone: This is the series containing various small improvements that I made while reading the code and researching commit history of pci-imx6.c and pcie-designware*.c files. All changes are optional, so commits that don't seem like an improvement can be easily dropped. Hopefully each patch is

Re: Kconfig dependency issue on function-graph tracer and frame pointer on arm

2019-04-14 Thread Masami Hiramatsu
On Sun, 14 Apr 2019 16:37:04 +0100 Russell King - ARM Linux admin wrote: > On Sun, Apr 14, 2019 at 11:52:38PM +0900, Masami Hiramatsu wrote: > > On Sun, 14 Apr 2019 14:34:58 +0100 > > Russell King - ARM Linux admin wrote: > > > > > On Sun, Apr 14, 2019 at 07:47:05PM +0900, Masami Hiramatsu

Re: [PATCH 1/3 RFC] ARM: mvebu: at least warn on kzalloc failure

2019-04-14 Thread Nicholas Mc Guire
On Sun, Apr 14, 2019 at 06:26:02PM +0100, Russell King - ARM Linux admin wrote: > On Sun, Apr 14, 2019 at 06:49:49AM +0200, Nicholas Mc Guire wrote: > > Although it is very unlikely that the allocation during init would > > fail any such failure should point to the original cause rather > > than

Re: [PATCH 3/3] ARM: mvebu: add SPDX license identifier

2019-04-14 Thread Nicholas Mc Guire
On Sun, Apr 14, 2019 at 06:22:10PM +0200, Andrew Lunn wrote: > On Sun, Apr 14, 2019 at 06:49:51AM +0200, Nicholas Mc Guire wrote: > > The license is clearly identified as GPL V2 - so just add in the > > appropriate SPDX license identifier. > > > > Signed-off-by: Nicholas Mc Guire > > Hi

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

2019-04-14 Thread Sean Wang
Hi, Light On Thu, Apr 11, 2019 at 8:15 PM Light Hsieh wrote: > > The orginal PINCTRL_MTK_PARIS/PINCTRL_MTK_MOORE need more effort for > specifying register bases when porting platform driver: > 1. Write mt_pinctrl_register_base_name[] array in pinctrl-mt.c >to specify names of

Linux 5.1-rc5

2019-04-14 Thread Linus Torvalds
Here we go again.. It's Sunday afternoon, must mean another rc kernel. We have changes all over, but not unseasonably many of them, and most of the ones here are very small. Looking at the stats, the sound driver updates kind of stand out, being almost a third of the patch (and about a third of

[tip:WIP.x86/stackguards 1/32] mm/slab.c:1486:27: error: expected '}' before ';' token

2019-04-14 Thread kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/stackguards head: 310a7f5b0b42c6a8edeb74ae3289a98896e0e5c9 commit: 7552063baa017438f2bfd6060e0b949808acc812 [1/32] mm/slab: Fix broken stack trace storage config: x86_64-randconfig-x003-201915 (attached as .config)

[tip:WIP.core/stacktrace 37/47] kernel/locking/lockdep.c:2806:2: error: implicit declaration of function 'print_lock_trace'

2019-04-14 Thread kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/stacktrace head: 63c35ea6b829a0f98d307a8dec038095681ecd13 commit: 88e5708cae1e9cb0cca97bb0af5866ac54532ceb [37/47] lockdep: Simplify stack trace handling config: x86_64-randconfig-l2-201915 (attached as .config)

BUG: Internal error: Oops: 17 [#1] SMP / _raw_spin_lock()

2019-04-14 Thread U.Mutlu
Hi, while issuing the command "dd if=/dev/zero of=test2 bs=8k count=64k conv=sync" in /tmp3 on the rootfs (/dev/sda1; a SSD drive), the system sometime crashes (maybe in 5% of the cases) The device is a Banana Pi using Allwinner A20 SoC (sunxi/sun7i/ARM), the kernel in use is the stock 5.0.5

[tip:WIP.core/stacktrace 24/47] mm/slab.c:1490:11: error: 'trace' undeclared; did you mean 'true'?

2019-04-14 Thread kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/stacktrace head: 63c35ea6b829a0f98d307a8dec038095681ecd13 commit: c79cc35c00e9f15a9a32a08569036cb8365c8816 [24/47] mm/slab: Simplify stack trace handling config: x86_64-randconfig-x003-201915 (attached as .config)

[tip:WIP.core/stacktrace 37/47] kernel/locking/lockdep.c:2806:2: error: implicit declaration of function 'print_lock_trace'; did you mean 'print_lock_name'?

2019-04-14 Thread kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/stacktrace head: 63c35ea6b829a0f98d307a8dec038095681ecd13 commit: 88e5708cae1e9cb0cca97bb0af5866ac54532ceb [37/47] lockdep: Simplify stack trace handling config: i386-randconfig-x018-201915 (attached as .config)

[tip:WIP.core/stacktrace 47/47] kernel//trace/trace_stack.c:263:26: error: invalid use of undefined type 'struct stack_trace'

2019-04-14 Thread kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/stacktrace head: 63c35ea6b829a0f98d307a8dec038095681ecd13 commit: 63c35ea6b829a0f98d307a8dec038095681ecd13 [47/47] x86/stacktrace: Use common infrastructure config: i386-randconfig-x010-201915 (attached as .config)

[tip:WIP.core/stacktrace 34/47] drivers/gpu/drm/drm_mm.c:136:3: error: implicit declaration of function 'stack_trace_snprintf'; did you mean 'stack_trace_snprint'?

2019-04-14 Thread kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/stacktrace head: 63c35ea6b829a0f98d307a8dec038095681ecd13 commit: 6476291d5b823a05b9c903a65a5f6e6026a02606 [34/47] drm: Simplify stacktrace handling config: i386-randconfig-x019-201915 (attached as .config) compiler:

[tip:WIP.core/stacktrace 18/47] kernel//trace/trace_stack.c:24:17: error: static declaration of 'stack_trace_index' follows non-static declaration

2019-04-14 Thread kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/stacktrace head: 63c35ea6b829a0f98d307a8dec038095681ecd13 commit: 4a934c54305ab50cf2d4b0afb915feee0dbb487e [18/47] tracing: Cleanup stack trace code config: i386-randconfig-x010-201915 (attached as .config) compiler:

Re: bug disabling NX (noexec=off)

2019-04-14 Thread Xose Vazquez Perez
On 4/14/19 11:59 AM, Thomas Gleixner wrote: > On Sat, 13 Apr 2019, Xose Vazquez Perez wrote: >> [0.00] NX (Execute Disable) protection: disabled by kernel command >> line option >> [0.00] [ cut here ] >> [0.00] attempted to set unsupported pgprot:

[tip:x86/urgent] x86/speculation: Prevent deadlock on ssb_state::lock

2019-04-14 Thread tip-bot for Thomas Gleixner
Commit-ID: 2f5fb19341883bb6e37da351bc3700489d8506a7 Gitweb: https://git.kernel.org/tip/2f5fb19341883bb6e37da351bc3700489d8506a7 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 19:51:06 +0200 Committer: Thomas Gleixner CommitDate: Sun, 14 Apr 2019 23:05:52 +0200 x86/speculation:

[tip:core/stacktrace] tracing: Remove the ULONG_MAX stack trace hackery

2019-04-14 Thread tip-bot for Thomas Gleixner
Commit-ID: 4285f2fcef8001ead0f1c9315ba50302cab68cda Gitweb: https://git.kernel.org/tip/4285f2fcef8001ead0f1c9315ba50302cab68cda Author: Thomas Gleixner AuthorDate: Wed, 10 Apr 2019 12:28:10 +0200 Committer: Thomas Gleixner CommitDate: Sun, 14 Apr 2019 19:58:32 +0200 tracing: Remove

[tip:core/stacktrace] drm: Remove the ULONG_MAX stack trace hackery

2019-04-14 Thread tip-bot for Thomas Gleixner
Commit-ID: fa49e2eac9aa8259e1ea540d1bd301448d5b735d Gitweb: https://git.kernel.org/tip/fa49e2eac9aa8259e1ea540d1bd301448d5b735d Author: Thomas Gleixner AuthorDate: Wed, 10 Apr 2019 12:28:09 +0200 Committer: Thomas Gleixner CommitDate: Sun, 14 Apr 2019 19:58:32 +0200 drm: Remove the

[tip:core/stacktrace] latency_top: Remove the ULONG_MAX stack trace hackery

2019-04-14 Thread tip-bot for Thomas Gleixner
Commit-ID: accddc41b96915ab4e5d37796c6d17d70805999c Gitweb: https://git.kernel.org/tip/accddc41b96915ab4e5d37796c6d17d70805999c Author: Thomas Gleixner AuthorDate: Wed, 10 Apr 2019 12:28:08 +0200 Committer: Thomas Gleixner CommitDate: Sun, 14 Apr 2019 19:58:31 +0200 latency_top:

[tip:core/stacktrace] mm/kasan: Remove the ULONG_MAX stack trace hackery

2019-04-14 Thread tip-bot for Thomas Gleixner
Commit-ID: ead97a49ec3a3cb9b5133acbfed9a49b91ebf37c Gitweb: https://git.kernel.org/tip/ead97a49ec3a3cb9b5133acbfed9a49b91ebf37c Author: Thomas Gleixner AuthorDate: Wed, 10 Apr 2019 12:28:07 +0200 Committer: Thomas Gleixner CommitDate: Sun, 14 Apr 2019 19:58:31 +0200 mm/kasan: Remove

[tip:core/stacktrace] mm/page_owner: Remove the ULONG_MAX stack trace hackery

2019-04-14 Thread tip-bot for Thomas Gleixner
Commit-ID: 4621c9858f05ab08434221e3a15cc8098645ef2a Gitweb: https://git.kernel.org/tip/4621c9858f05ab08434221e3a15cc8098645ef2a Author: Thomas Gleixner AuthorDate: Wed, 10 Apr 2019 12:28:06 +0200 Committer: Thomas Gleixner CommitDate: Sun, 14 Apr 2019 19:58:30 +0200 mm/page_owner:

[tip:core/stacktrace] mm/slub: Remove the ULONG_MAX stack trace hackery

2019-04-14 Thread tip-bot for Thomas Gleixner
Commit-ID: b8ca7ff7731f57b256fcc13a9b7d4913f5282e5c Gitweb: https://git.kernel.org/tip/b8ca7ff7731f57b256fcc13a9b7d4913f5282e5c Author: Thomas Gleixner AuthorDate: Wed, 10 Apr 2019 12:28:05 +0200 Committer: Thomas Gleixner CommitDate: Sun, 14 Apr 2019 19:58:30 +0200 mm/slub: Remove

[tip:core/stacktrace] s390/stacktrace: Remove the pointless ULONG_MAX marker

2019-04-14 Thread tip-bot for Thomas Gleixner
Commit-ID: 6a28b4c2d93b812512d8d2e5179e61a14f578560 Gitweb: https://git.kernel.org/tip/6a28b4c2d93b812512d8d2e5179e61a14f578560 Author: Thomas Gleixner AuthorDate: Wed, 10 Apr 2019 12:28:03 +0200 Committer: Thomas Gleixner CommitDate: Sun, 14 Apr 2019 19:58:29 +0200 s390/stacktrace:

[tip:core/stacktrace] parisc/stacktrace: Remove the pointless ULONG_MAX marker

2019-04-14 Thread tip-bot for Thomas Gleixner
Commit-ID: 4f3bd6ca310b594df09c8f1e319cda9baf502ec8 Gitweb: https://git.kernel.org/tip/4f3bd6ca310b594df09c8f1e319cda9baf502ec8 Author: Thomas Gleixner AuthorDate: Wed, 10 Apr 2019 12:28:02 +0200 Committer: Thomas Gleixner CommitDate: Sun, 14 Apr 2019 19:58:29 +0200 parisc/stacktrace:

[tip:core/stacktrace] lockdep: Remove the ULONG_MAX stack trace hackery

2019-04-14 Thread tip-bot for Thomas Gleixner
Commit-ID: 2dfed4565afe263751d2451ad22336ad806c25a6 Gitweb: https://git.kernel.org/tip/2dfed4565afe263751d2451ad22336ad806c25a6 Author: Thomas Gleixner AuthorDate: Wed, 10 Apr 2019 12:28:04 +0200 Committer: Thomas Gleixner CommitDate: Sun, 14 Apr 2019 19:58:30 +0200 lockdep: Remove

[tip:core/stacktrace] arm64/stacktrace: Remove the pointless ULONG_MAX marker

2019-04-14 Thread tip-bot for Thomas Gleixner
Commit-ID: 7b2c7b6233497bfab8826ece574bc1c26e97478d Gitweb: https://git.kernel.org/tip/7b2c7b6233497bfab8826ece574bc1c26e97478d Author: Thomas Gleixner AuthorDate: Wed, 10 Apr 2019 12:28:01 +0200 Committer: Thomas Gleixner CommitDate: Sun, 14 Apr 2019 19:58:29 +0200 arm64/stacktrace:

[tip:core/stacktrace] riscv/stacktrace: Remove the pointless ULONG_MAX marker

2019-04-14 Thread tip-bot for Thomas Gleixner
Commit-ID: fa9833992d5ff3c0d6e81d708bec363bce2fb54c Gitweb: https://git.kernel.org/tip/fa9833992d5ff3c0d6e81d708bec363bce2fb54c Author: Thomas Gleixner AuthorDate: Wed, 10 Apr 2019 12:28:00 +0200 Committer: Thomas Gleixner CommitDate: Sun, 14 Apr 2019 19:58:28 +0200 riscv/stacktrace:

[tip:core/stacktrace] sh/stacktrace: Remove the pointless ULONG_MAX marker

2019-04-14 Thread tip-bot for Thomas Gleixner
Commit-ID: b01f6d368d296cac099383a3eb200e135420f885 Gitweb: https://git.kernel.org/tip/b01f6d368d296cac099383a3eb200e135420f885 Author: Thomas Gleixner AuthorDate: Wed, 10 Apr 2019 12:27:58 +0200 Committer: Thomas Gleixner CommitDate: Sun, 14 Apr 2019 19:58:28 +0200 sh/stacktrace:

[tip:core/stacktrace] unicore32/stacktrace: Remove the pointless ULONG_MAX marker

2019-04-14 Thread tip-bot for Thomas Gleixner
Commit-ID: f8a9a269c28ddd5d741e747ceca753af01c828f2 Gitweb: https://git.kernel.org/tip/f8a9a269c28ddd5d741e747ceca753af01c828f2 Author: Thomas Gleixner AuthorDate: Wed, 10 Apr 2019 12:27:59 +0200 Committer: Thomas Gleixner CommitDate: Sun, 14 Apr 2019 19:58:28 +0200

[tip:core/stacktrace] arm/stacktrace: Remove the pointless ULONG_MAX marker

2019-04-14 Thread tip-bot for Thomas Gleixner
Commit-ID: 2a2bcfa0c94d8bc4770676a6799928036296c037 Gitweb: https://git.kernel.org/tip/2a2bcfa0c94d8bc4770676a6799928036296c037 Author: Thomas Gleixner AuthorDate: Wed, 10 Apr 2019 12:27:57 +0200 Committer: Thomas Gleixner CommitDate: Sun, 14 Apr 2019 19:58:27 +0200 arm/stacktrace:

[tip:core/stacktrace] um/stacktrace: Remove the pointless ULONG_MAX marker

2019-04-14 Thread tip-bot for Thomas Gleixner
Commit-ID: fdc7833964d83b7f7f39a03e2ee48a229ba0291f Gitweb: https://git.kernel.org/tip/fdc7833964d83b7f7f39a03e2ee48a229ba0291f Author: Thomas Gleixner AuthorDate: Wed, 10 Apr 2019 12:27:55 +0200 Committer: Thomas Gleixner CommitDate: Sun, 14 Apr 2019 19:58:27 +0200 um/stacktrace:

[tip:core/stacktrace] x86/stacktrace: Remove the pointless ULONG_MAX marker

2019-04-14 Thread tip-bot for Thomas Gleixner
Commit-ID: c5c27a0a583844c69a433039e4fd6396ba23551b Gitweb: https://git.kernel.org/tip/c5c27a0a583844c69a433039e4fd6396ba23551b Author: Thomas Gleixner AuthorDate: Wed, 10 Apr 2019 12:27:56 +0200 Committer: Thomas Gleixner CommitDate: Sun, 14 Apr 2019 19:58:27 +0200 x86/stacktrace:

Re: [PATCH] MIPS: scall64-o32: Fix indirect syscall number load

2019-04-14 Thread Philippe Mathieu-Daudé
On 4/9/19 4:53 PM, Aurelien Jarno wrote: > Commit 4c21b8fd8f14 (MIPS: seccomp: Handle indirect system calls (o32)) > added indirect syscall detection for O32 processes running on MIPS64, > but it did not work correctly for big endian kernel/processes. The > reason is that the syscall number is

[PATCH v2 4/4] ARM: dts: tegra30: Add External Memory Controller node

2019-04-14 Thread Dmitry Osipenko
Add External Memory Controller node to the device-tree. Signed-off-by: Dmitry Osipenko --- arch/arm/boot/dts/tegra30.dtsi | 11 +++ 1 file changed, 11 insertions(+) diff --git a/arch/arm/boot/dts/tegra30.dtsi b/arch/arm/boot/dts/tegra30.dtsi index e074258d4518..92c4aeafab29 100644 ---

[PATCH v2 3/4] memory: tegra: Introduce Tegra30 EMC driver

2019-04-14 Thread Dmitry Osipenko
Introduce driver for the External Memory Controller (EMC) found on Tegra30 chips, it controls the external DRAM on the board. The purpose of this driver is to program memory timing for external memory on the EMC clock rate change. Signed-off-by: Dmitry Osipenko --- drivers/memory/tegra/Kconfig

[PATCH v2 2/4] dt-bindings: memory: Add binding for NVIDIA Tegra30 External Memory Controller

2019-04-14 Thread Dmitry Osipenko
Add device-tree binding for NVIDIA Tegra30 External Memory Controller. The binding is based on the Tegra124 EMC binding since hardware is similar, although there are couple significant differences. Signed-off-by: Dmitry Osipenko --- .../memory-controllers/nvidia,tegra30-emc.txt | 257

[PATCH v2 0/4] memory: tegra: Introduce Tegra30 EMC driver

2019-04-14 Thread Dmitry Osipenko
Hello, This series introduces driver for the External Memory Controller (EMC) found on Tegra30 chips, it controls the external DRAM on the board. The purpose of this driver is to program memory timing for external memory on the EMC clock rate change. The driver was tested using the ACTMON devfreq

[PATCH v2 1/4] clk: tegra20/30: Add custom EMC clock implementation

2019-04-14 Thread Dmitry Osipenko
A proper External Memory Controller clock rounding and parent selection functionality is required by the EMC drivers. It is not available using the generic clock implementation, hence add a custom one. The clock rate rounding shall be done by the EMC drivers because they have information about

Re: [PATCH] [PATCHv1] drivers: edac: This patch fix the following checkpatch warning.

2019-04-14 Thread Borislav Petkov
On Sun, Apr 14, 2019 at 10:09:49PM +0300, mohan kumar wrote: > Ok Thanks, I will do that. Good. One more thing: please do not top-post when replying on public mailing lists. Thx. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.

[PATCH 0/4] clone: add CLONE_PIDFD

2019-04-14 Thread Christian Brauner
Hey Linus, This patchset makes it possible to retrieve pid file descriptors at process creation time by introducing the new flag CLONE_PIDFD to the clone() system call as previously discussed. As decided last week [1] Jann and I have refined the implementation of pidfds as anonymous inodes.

[PATCH 2/4] clone: add CLONE_PIDFD

2019-04-14 Thread Christian Brauner
As discussed this patchset makes it possible to retrieve pid file descriptors at process creation time by introducing the new flag CLONE_PIDFD to the clone() system call. Linus originally suggested to implement this as a new flag to clone() instead of making it a separate system call. As spotted

[PATCH 3/4] signal: support CLONE_PIDFD with pidfd_send_signal

2019-04-14 Thread Christian Brauner
Let pidfd_send_signal() use pidfds retrieved via CLONE_PIDFD. With this patch pidfd_send_signal() becomes independent of procfs. This fullfils the request made when we merged the pidfd_send_signal() patchset. The pidfd_send_signal() syscall is now always available allowing for it to be used by

[PATCH 4/4] samples: show race-free pidfd metadata access

2019-04-14 Thread Christian Brauner
This is a sample program showing userspace how to get race-free access to process metadata from a pidfd. It is rather easy to do and userspace can actually simply reuse code that currently parses a process's status file in procfs. The program can easily be extended into a generic helper suitable

[PATCH 1/4] Make anon_inodes unconditional

2019-04-14 Thread Christian Brauner
From: David Howells Make the anon_inodes facility unconditional so that it can be used by core VFS code and pidfd code. Signed-off-by: David Howells Signed-off-by: Al Viro [christ...@brauner.io: adapt commit message to mention pidfds] Signed-off-by: Christian Brauner ---

  1   2   3   >