Re: [PATCH 0/7] atomics: generate atomic headers

2018-06-04 Thread Mark Rutland
On Mon, Jun 04, 2018 at 06:21:22PM +0200, Dmitry Vyukov wrote: > On Tue, May 29, 2018 at 8:07 PM, Mark Rutland wrote: > > This series scripts the generation of the various atomic headers, to > > ensure that the various atomic APIs remain consistent, reducing the risk > > of human error, and

Re: Spectre mitigation doesn't seem to work at all?!

2018-06-04 Thread Andreas Hartmann
On 06/04/2018 at 04:12 PM Alan Cox wrote: >> A malicious program most probably won't care about that. Therefore, my >> next question is: which memory regions can be exploited by a malicious >> program? The complete physical memory or only the memory provided to the >> malicious program? Should be

Re: [PATCH V4] powercap/drivers/idle_injection: Add an idle injection framework

2018-06-04 Thread Viresh Kumar
On 05-06-18, 07:48, Daniel Lezcano wrote: > As soon as we reach complete(), no timer can be set because of the > condition before. Why not ? We aren't using any locks here and it is possible that run_duration_ms is set to 0 from idle_injection_stop() only after the first thread has restarted the

RE: [CFT][PATCH] kernfs: Correct kernfs directory seeks.

2018-06-04 Thread Hatayama, Daisuke
> -Original Message- > From: Eric W. Biederman [mailto:ebied...@xmission.com] > Sent: Tuesday, June 5, 2018 11:03 AM > To: Hatayama, Daisuke > Cc: 'gre...@linuxfoundation.org' ; > 't...@kernel.org' ; Okajima, Toshiyuki > ; linux-kernel@vger.kernel.org; > 'ebied...@aristanetworks.com'

Re: [PATCH v5 24/31] kconfig: add CC_IS_GCC and GCC_VERSION

2018-06-04 Thread Stefan Agner
On 05.06.2018 02:07, Masahiro Yamada wrote: > Hi Stefan > > 2018-06-05 6:49 GMT+09:00 Stefan Agner : >> Hi Masahiro, >> >> On 28.05.2018 11:22, Masahiro Yamada wrote: >>> This will be useful to specify the required compiler version, >>> like this: >>> >>> config FOO >>> bool "Use Foo" >>>

[no subject]

2018-06-04 Thread Mavis Wanczyk
-- Good Day, I, Mavis Wanczyk donates $ 5 Million Dollars from part of my Powerball Jackpot Lottery of $ 758 Million Dollars, respond with your details for claims. I await your earliest response and God Bless you Good luck. Mavis Wanczyk

Re: 4.14.44: BUG_ON(!list_empty(>wait_list));

2018-06-04 Thread Daniel J Blueman
On 5 June 2018 at 05:47, wrote: >> -Original Message- >> From: Daniel J Blueman [mailto:dan...@quora.org] >> Sent: Thursday, May 31, 2018 9:21 PM >> To: Linux Kernel; linux-a...@vger.kernel.org >> Cc: Limonciello, Mario; Dominguez, Jared >> Subject: 4.14.44:

Re: [PATCH V4] powercap/drivers/idle_injection: Add an idle injection framework

2018-06-04 Thread Daniel Lezcano
On 05/06/2018 07:14, Viresh Kumar wrote: > On 31-05-18, 20:25, Daniel Lezcano wrote: >> On 29/05/2018 11:31, Viresh Kumar wrote: >>> On 25-05-18, 11:49, Daniel Lezcano wrote: + /* + * The last CPU waking up is in charge of setting the timer. If + * the CPU is hotplugged, the

Re: [PATCH v2 4/9] x86: alternatives: macrofy locks for better inlining

2018-06-04 Thread kbuild test robot
Hi Nadav, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.17 next-20180604] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https

RE: [CFT][PATCH] kernfs: Correct kernfs directory seeks.

2018-06-04 Thread Hatayama, Daisuke
> -Original Message- > From: Eric W. Biederman [mailto:ebied...@xmission.com] > Sent: Monday, June 4, 2018 11:45 PM > To: Hatayama, Daisuke > Cc: 'gre...@linuxfoundation.org' ; > 't...@kernel.org' ; Okajima, Toshiyuki > ; linux-kernel@vger.kernel.org; > 'ebied...@aristanetworks.com'

Re: [PATCH v2 4/9] x86: alternatives: macrofy locks for better inlining

2018-06-04 Thread kbuild test robot
Hi Nadav, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.17 next-20180604] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https

[PATCH] remoteproc: qcom: Introduce Hexagon V5 based WCSS driver

2018-06-04 Thread Sricharan R
IPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan (Lithium) IP. An mdt type single image format is used for the firmware. So the mdt_load function can be directly used to load the firmware. Also add the relevant resets required for this core. Acked-by: Rob Herring (for bindings)

Re: [PATCH v2 2/9] x86: objtool: use asm macro for better compiler decisions

2018-06-04 Thread kbuild test robot
Hi Nadav, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.17 next-20180604] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https

Re: [PATCH 6/6] x86/vdso: Move out the CPU number store

2018-06-04 Thread H. Peter Anvin
On 06/04/18 20:57, Mika Penttilä wrote: > > This won't work on X86-32 because it actually uses the segment limit with fs: > access. So there > is a reason why the lsl based method is X86-64 only. > Why does that matter in any shape, way, or form? The LSL instruction doesn't touch any of

Re: [PATCHv2 03/16] atomics/treewide: make atomic64_inc_not_zero() optional

2018-06-04 Thread Mark Rutland
On Mon, Jun 04, 2018 at 04:17:25PM -0700, Palmer Dabbelt wrote: > On Tue, 29 May 2018 08:43:33 PDT (-0700), mark.rutl...@arm.com wrote: > > We define a trivial fallback for atomic_inc_not_zero(), but don't do > > the same for atmic64_inc_not_zero(), leading most architectures to > > define the

Re: [greybus-dev] [PATCH] Staging:greybus Fix comparison to NULL

2018-06-04 Thread Viresh Kumar
On 03-06-18, 08:52, Janani Sankara Babu wrote: > This patch replaces comparison of var to NULL with !var > > Signed-off-by: Janani Sankara Babu > --- > drivers/staging/greybus/core.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/staging/greybus/core.c

Re: [PATCH 6/6] x86/vdso: Move out the CPU number store

2018-06-04 Thread Mika Penttilä
On 06/05/2018 07:44 AM, Bae, Chang Seok wrote: >>> diff --git a/arch/x86/kernel/setup_percpu.c b/arch/x86/kernel/setup_percpu.c >>> index ea554f8..e716e94 100644 >>> --- a/arch/x86/kernel/setup_percpu.c >>> +++ b/arch/x86/kernel/setup_percpu.c >>> @@ -155,12 +155,21 @@ static void __init

Re: [PATCH V4] powercap/drivers/idle_injection: Add an idle injection framework

2018-06-04 Thread Viresh Kumar
On 31-05-18, 20:25, Daniel Lezcano wrote: > On 29/05/2018 11:31, Viresh Kumar wrote: > > On 25-05-18, 11:49, Daniel Lezcano wrote: > >> + /* > >> + * The last CPU waking up is in charge of setting the timer. If > >> + * the CPU is hotplugged, the timer will move to another CPU > >> + *

[PATCH V2 2/2] arm: dts: sunxi: Add missing cooling device properties for CPUs

2018-06-04 Thread Viresh Kumar
The cooling device properties, like "#cooling-cells" and "dynamic-power-coefficient", should either be present for all the CPUs of a cluster or none. If these are present only for a subset of CPUs of a cluster then things will start falling apart as soon as the CPUs are brought online in a

[PATCH V2 1/2] arm: dts: sun8i-h3: Add missing cooling device properties for CPUs

2018-06-04 Thread Viresh Kumar
The cooling device properties, like "#cooling-cells" and "dynamic-power-coefficient", should either be present for all the CPUs of a cluster or none. If these are present only for a subset of CPUs of a cluster then things will start falling apart as soon as the CPUs are brought online in a

Re: Regression in Linux next again

2018-06-04 Thread Tony Lindgren
Hi, * Maciej Purski [180604 14:02]: > Tony, please apply this patchset and test it on your Beaglebone. It'd be > great if you could try to find out, which patch causes failure. They should > be appliable on the current next. It seems beagle-x15 boots for me except with the last patch in the

Re: [PATCH 6/6] x86/vdso: Move out the CPU number store

2018-06-04 Thread Bae, Chang Seok
>> diff --git a/arch/x86/kernel/setup_percpu.c b/arch/x86/kernel/setup_percpu.c >> index ea554f8..e716e94 100644 >> --- a/arch/x86/kernel/setup_percpu.c >> +++ b/arch/x86/kernel/setup_percpu.c >> @@ -155,12 +155,21 @@ static void __init pcpup_populate_pte(unsigned long >> addr) >> >> static

Re: [PATCH 1/6] arm64: dts: amlogic: Add missing cooling device properties for CPUs

2018-06-04 Thread Viresh Kumar
On 02-06-18, 01:14, Olof Johansson wrote: > And what I am saying is that it sounds like a broken binding if you don't > allow > that, especially since it'll be a super common case that all CPUs will specify > the same cooling-device specifier. I am fine with allowing the #cooling-cells property

Re: [PATCH 0/3] Provide more fine grained control over multipathing

2018-06-04 Thread Christoph Hellwig
On Mon, Jun 04, 2018 at 02:58:49PM -0700, Roland Dreier wrote: > We plan to implement all the fancy NVMe standards like ANA, but it > seems that there is still a requirement to let the host side choose > policies about how to use paths (round-robin vs least queue depth for > example). Even in the

Re: [PATCH -mm -V3 00/21] mm, THP, swap: Swapout/swapin THP in one piece

2018-06-04 Thread Huang, Ying
Daniel Jordan writes: > On Wed, May 23, 2018 at 04:26:04PM +0800, Huang, Ying wrote: >> And for all, Any comment is welcome! >> >> This patchset is based on the 2018-05-18 head of mmotm/master. > > Trying to review this and it doesn't apply to mmotm-2018-05-18-16-44. git > fails on patch 10: >

Re: Common config for N900 and D4

2018-06-04 Thread Tony Lindgren
* Pavel Machek [180603 21:03]: > Hi! > > > > Aaro, I know I have asked before, but if you have common config for > > > N900 and Droid4, please send me a copy. Yes, it should be somewhere in > > > my inbox already, but I can't find it and version for v4.17 would be > > > more useful. > > > > > >

Re: [rfc patch] mm, oom: fix unnecessary killing of additional processes

2018-06-04 Thread David Rientjes
On Fri, 1 Jun 2018, Michal Hocko wrote: > > We've discussed the mm > > having a single blockable mmu notifier. Regardless of how we arrive at > > the point where the oom reaper can't free memory, which could be any of > > those three cases, if (1) the original victim is sufficiently large

Re: [PATCH] uart: fix race between uart_put_char() and uart_shutdown()

2018-06-04 Thread Serge E. Hallyn
Quoting Tycho Andersen (ty...@tycho.ws): > We have reports of the following crash: > > PID: 7 TASK: 88085c6d61c0 CPU: 1 COMMAND: "kworker/u25:0" > #0 [88085c6db710] machine_kexec at 81046239 > #1 [88085c6db760] crash_kexec at 810fc248 > #2

Re: [PATCH 6/6] x86/vdso: Move out the CPU number store

2018-06-04 Thread Mika Penttilä
On 06/04/2018 10:24 PM, Chang S. Bae wrote: > The CPU (and node) number will be written, as early enough, > to the segment limit of per CPU data and TSC_AUX MSR entry. > The information has been retrieved by vgetcpu in user space > and will be also loaded from the paranoid entry, when > FSGSBASE

Re: [PATCH 16/19] sched/numa: Detect if node actively handling migration

2018-06-04 Thread Srikar Dronamraju
* Rik van Riel [2018-06-04 16:05:55]: > On Mon, 2018-06-04 at 15:30 +0530, Srikar Dronamraju wrote: > > > @@ -1554,6 +1562,9 @@ static void task_numa_compare(struct > > task_numa_env *env, > > if (READ_ONCE(dst_rq->numa_migrate_on)) > > return; > > > > + if (*move &&

Re: [PATCH 1/2] platform/x86: asus-wmi: Call new led hw_changed API on kbd brightness change

2018-06-04 Thread Chris Chiu
On Tue, Jun 5, 2018 at 10:31 AM, Darren Hart wrote: > On Mon, Jun 04, 2018 at 04:23:04PM +0200, Hans de Goede wrote: >> Hi, >> >> On 04-06-18 15:51, Daniel Drake wrote: >> > On Mon, Jun 4, 2018 at 7:22 AM, Hans de Goede wrote: >> > > Is this really a case of the hardware itself processing the >>

linux-next: build warning after merge of the mfd tree

2018-06-04 Thread Stephen Rothwell
Hi Lee, After merging the mfd tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/mfd/cros_ec_dev.c:265:13: warning: '__remove' defined but not used [-Wunused-function] static void __remove(struct device *dev) { } ^~~~ Introduced by commit

rf69_set_deviation in rf69.c (pi433 driver)

2018-06-04 Thread Hugo Lefeuvre
Hi Marcus, I have been taking a look at the pi433 driver these last days, and started working on the remaining TODOs. I just stumbled across the following one (drivers/staging/pi433/rf69.c): 245 // TODO: Dependency to bitrate 246 if (deviation < 600 || deviation > 50) { 247

Re: [PATCH] ARM: dts: armada388-helios4

2018-06-04 Thread Baruch Siach
Hi Dennis, On Mon, Jun 04, 2018 at 08:13:43PM -0500, Dennis Gilmore wrote: > The helios4 is a Armada388 based nas board designed by SolidRun and > based on their SOM. It is sold by kobol.io the dts file came from >

Re: [PATCH] Use an IDR to allocate apparmor secids

2018-06-04 Thread John Johansen
On 06/04/2018 07:27 PM, Matthew Wilcox wrote: > On Mon, Jun 04, 2018 at 06:27:09PM -0700, John Johansen wrote: >> hey Mathew, >> >> I've pulled this into apparmor-next and done the retuning of >> AA_SECID_INVALID a follow on patch. The reworking of the api to >> return the specific error type can

Re: [PATCH 1/2] platform/x86: asus-wmi: Call new led hw_changed API on kbd brightness change

2018-06-04 Thread Darren Hart
On Mon, Jun 04, 2018 at 04:23:04PM +0200, Hans de Goede wrote: > Hi, > > On 04-06-18 15:51, Daniel Drake wrote: > > On Mon, Jun 4, 2018 at 7:22 AM, Hans de Goede wrote: > > > Is this really a case of the hardware itself processing the > > > keypress and then changing the brightness *itself* ? >

Re: [PATCH 2/2] sched/fair: util_est: add running_sum tracking

2018-06-04 Thread kbuild test robot
Hi Patrick, Thank you for the patch! Yet something to improve: [auto build test ERROR on tip/sched/core] [also build test ERROR on next-20180604] [cannot apply to v4.17] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https

Re: [PATCH] Use an IDR to allocate apparmor secids

2018-06-04 Thread Matthew Wilcox
On Mon, Jun 04, 2018 at 06:27:09PM -0700, John Johansen wrote: > hey Mathew, > > I've pulled this into apparmor-next and done the retuning of > AA_SECID_INVALID a follow on patch. The reworking of the api to > return the specific error type can wait for another cycle. Oh ... here's what I

RE: [PATCH] panic: move bust_spinlocks(0) after console_flush_on_panic() to avoid deadlocks

2018-06-04 Thread Hoeun Ryu
I misunderstood the cause of a deadlock. I sent v2 fixing the commit message about the reason of the deadlock. Please ignore this and review v2. Thank you. > -Original Message- > From: Steven Rostedt [mailto:rost...@goodmis.org] > Sent: Tuesday, June 05, 2018 10:44 AM > To: Hoeun Ryu >

[PATCH v2] panic: move bust_spinlocks(0) after console_flush_on_panic() to avoid deadlocks

2018-06-04 Thread Hoeun Ryu
From: Hoeun Ryu Many console device drivers hold the uart_port->lock spinlock with irq disabled (using spin_lock_irqsave()) while the device drivers are writing characters to their devices, but the device drivers just try to hold the spin lock (using spin_trylock_irqsave()) instead if

Re: [PATCH 1/2] platform/x86: asus-wmi: Call new led hw_changed API on kbd brightness change

2018-06-04 Thread Darren Hart
On Mon, Jun 04, 2018 at 08:32:37PM +0800, Chris Chiu wrote: > Make asus-wmi notify on hotkey kbd brightness changes, listen for > brightness events and update the brightness directly in the driver. > For this purpose, bound check on brightness in kbd_led_set must be > based on the same data type

Re: [CFT][PATCH] kernfs: Correct kernfs directory seeks.

2018-06-04 Thread Eric W. Biederman
ebied...@xmission.com (Eric W. Biederman) writes: > "Hatayama, Daisuke" writes: > >>> Can you test this and please verify it fixes your issue? >> >> I tried this patch on top of v4.17 but the system fails to boot >> without detecting root disks by dracut like this: [snip] >> OTOH, there's no

[PATCH] ksys_mount: check for permissions before resource allocation

2018-06-04 Thread Ilya Matveychikov
Early check for mount permissions prevents possible allocation of 3 pages from kmalloc() pool by unpriveledged user which can be used for spraying the kernel heap. Signed-off-by: Ilya V. Matveychikov --- fs/namespace.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/fs/namespace.c

Re: [GIT PULL] x86/asm changes for v4.18

2018-06-04 Thread Linus Torvalds
On Mon, Jun 4, 2018 at 5:21 AM Ingo Molnar wrote: > > - __clear_user() micro-optimization (Alexey Dobriyan) Was this actually tested? I think one reason people avoided the constant was that on some microarchitecture it ended up being a separate uop just for the constant generation, because it

Re: [PATCH v2] platform/x86: asus-wmi: Add keyboard backlight toggle support

2018-06-04 Thread Darren Hart
On Mon, Jun 04, 2018 at 11:27:43AM +0200, Benjamin Berg wrote: > Hi, > > On Thu, 2018-05-24 at 16:33 +0800, Chris Chiu wrote: > > I've made my change to set the brightness level directly in the > > driver, but the > > OSD doesn't show correctly correspond to the level value. The brightness > >

Re: [PATCH v4 8/8] Documentation/ABI: Add documentation mlxreg-io sysfs interfaces

2018-06-04 Thread Darren Hart
On Tue, May 29, 2018 at 08:59:07AM +, Vadim Pasternak wrote: > Add documentation for mlxreg-io driver sysfs interfaces for user space > access to system's power resets control, reset causes monitoring, > programmable devices version reading and devices selection control. > > Signed-off-by:

Re: [PATCH] panic: move bust_spinlocks(0) after console_flush_on_panic() to avoid deadlocks

2018-06-04 Thread Steven Rostedt
On Mon, 4 Jun 2018 14:45:57 +0900 Hoeun Ryu wrote: > From: Hoeun Ryu > > Many console device drivers hold the uart_port->lock spinlock with irq > enabled > (using spin_lock()) while the device drivers are writing characters to their > devices, > but the device drivers just try to hold the

Re: [PATCH 1/2] sched/fair: pelt: use u32 for util_avg

2018-06-04 Thread kbuild test robot
Hi Patrick, Thank you for the patch! Yet something to improve: [auto build test ERROR on tip/sched/core] [also build test ERROR on v4.17 next-20180604] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux

Re: [PATCH V2] cros_ec_keyb: Mark cros_ec_keyb driver as wake enabled device.

2018-06-04 Thread Brian Norris
Hi, On Fri, May 25, 2018 at 06:14:40PM -0700, Ravi Chandra Sadineni wrote: > Mark cros_ec_keyb has wake enabled by default. If we see a MKBP event > related to keyboard, call pm_wakeup_event() to make sure wakeup > triggers are accounted to keyb during suspend resume path. > > Signed-off-by:

Re: [PATCH 1/2] sched/fair: pelt: use u32 for util_avg

2018-06-04 Thread kbuild test robot
Hi Patrick, Thank you for the patch! Yet something to improve: [auto build test ERROR on tip/sched/core] [also build test ERROR on v4.17 next-20180604] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux

Re: [PATCH 2/2] sched/fair: util_est: add running_sum tracking

2018-06-04 Thread kbuild test robot
Hi Patrick, Thank you for the patch! Yet something to improve: [auto build test ERROR on tip/sched/core] [also build test ERROR on next-20180604] [cannot apply to v4.17] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https

Re: [PATCH] Use an IDR to allocate apparmor secids

2018-06-04 Thread John Johansen
On 05/28/2018 10:01 AM, Matthew Wilcox wrote: > > ping? > > I have this queued up in my XArray tree. If I don't hear from you before > -rc1, I'll be submitting it as part of the XArray conversion. > hey Mathew, I've pulled this into apparmor-next and done the retuning of AA_SECID_INVALID a

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

2018-06-04 Thread Stephen Rothwell
Hi Dave, On Tue, 5 Jun 2018 10:59:04 +1000 Dave Chinner wrote: > > On Tue, Jun 05, 2018 at 10:34:03AM +1000, Stephen Rothwell wrote: > > > > Today's linux-next merge of the xfs tree got a conflict in: > > > > fs/gfs2/bmap.c > > > > between commit: > > > > 628e366df11c ("gfs2: Iomap

Re: linux-next: manual merge of the nvdimm tree with the jc_docs tree

2018-06-04 Thread Stephen Rothwell
Hi all, On Wed, 9 May 2018 18:05:39 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the nvdimm tree got a conflict in: > > mm/hmm.c > > between commit: > > ad56b738c5dd ("docs/vm: rename documentation files to .rst") > > from the jc_docs tree and commit: > >

[PATCH] ARM: dts: armada388-helios4

2018-06-04 Thread Dennis Gilmore
The helios4 is a Armada388 based nas board designed by SolidRun and based on their SOM. It is sold by kobol.io the dts file came from https://raw.githubusercontent.com/armbian/build/master/patch/kernel/mvebu-default/95-helios4-device-tree.patch I added a SPDX license line to match the clearfog it

Re: [PATCH] riscv: add riscv-specific predefines to CHECKFLAGS

2018-06-04 Thread Palmer Dabbelt
On Thu, 31 May 2018 08:42:01 PDT (-0700), luc.vanoostenr...@gmail.com wrote: RISC-V uses the macro __riscv_xlen, predefined by GCC, to make the distinction between 32 or 64 bit code. However, sparse doesn't know anything about this macro which lead to wrong warnings and failures. Fix this by

Re: [PATCH] riscv: pass machine size to sparse

2018-06-04 Thread Palmer Dabbelt
On Thu, 31 May 2018 08:35:54 PDT (-0700), luc.vanoostenr...@gmail.com wrote: On Thu, May 31, 2018 at 05:09:21AM -0700, Palmer Dabbelt wrote: On Mon, 28 May 2018 23:14:20 PDT (-0700), yamada.masah...@socionext.com wrote: > 2018-05-29 15:11 GMT+09:00 Christoph Hellwig : > > On Mon, May 28, 2018

Re: kernel panic in reading /proc/kpageflags when enabling RAM-simulated PMEM

2018-06-04 Thread Matthew Wilcox
On Tue, Jun 05, 2018 at 12:54:03AM +, Naoya Horiguchi wrote: > Reproduction precedure is like this: > - enable RAM based PMEM (with a kernel boot parameter like memmap=1G!4G) > - read /proc/kpageflags (or call tools/vm/page-types with no arguments) > (- my kernel config is attached) > > I

Re: [PATCH 1/6] PCI: iproc: Update iProc PCI binding for INTx support

2018-06-04 Thread Ray Jui
Hi Rob/Arnd, On 6/4/2018 7:17 AM, Rob Herring wrote: +Arnd On Tue, May 29, 2018 at 4:58 PM, Ray Jui wrote: Update the iProc PCIe binding document for better modeling of the legacy interrupt (INTx) support Signed-off-by: Ray Jui --- .../devicetree/bindings/pci/brcm,iproc-pcie.txt| 31

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

2018-06-04 Thread Andreas Grünbacher
2018-06-05 2:59 GMT+02:00 Dave Chinner : > On Tue, Jun 05, 2018 at 10:34:03AM +1000, Stephen Rothwell wrote: >> Hi all, >> >> Today's linux-next merge of the xfs tree got a conflict in: >> >> fs/gfs2/bmap.c >> >> between commit: >> >> 628e366df11c ("gfs2: Iomap cleanups and improvements") >>

Re: [PATCH] riscv/ftrace: Export _mcount when FUNCTION_GRAPH_TRACER isn't set

2018-06-04 Thread Alan Kao
Hi Palmer, Thanks for the refining work! But a small correction here: On Mon, Jun 04, 2018 at 01:30:28PM -0700, Palmer Dabbelt wrote: > From: Alan Kao > > The EXPORT_SYMBOL(_mcount) for RISC-V ended up inside a > CONFIG_FUNCTION_GRAPH_TRACER ifdef. If you enable modules without > enabling

Re: [PATCH v4 6/8] platform/mellanox: Introduce support for Mellanox register access driver

2018-06-04 Thread Darren Hart
On Tue, May 29, 2018 at 08:59:05AM +, Vadim Pasternak wrote: > Introduce new Mellanox platform driver to allow access to Mellanox > programmable device register space trough sysfs interface. > The driver purpose is to provide sysfs interface for user space for the > registers essential for

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

2018-06-04 Thread Dave Chinner
On Tue, Jun 05, 2018 at 10:34:03AM +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the xfs tree got a conflict in: > > fs/gfs2/bmap.c > > between commit: > > 628e366df11c ("gfs2: Iomap cleanups and improvements") > > from Linus' tree and commit: > >

kernel panic in reading /proc/kpageflags when enabling RAM-simulated PMEM

2018-06-04 Thread Naoya Horiguchi
Hi everyone, I detected a kernel panic in mmotm on 5/25. [ 33.316734] BUG: unable to handle kernel paging request at fffe [ 33.318157] PGD 9b20e067 P4D 9b20e067 PUD 9b210067 PMD 0 [ 33.319201] Oops: [#1] SMP PTI [ 33.319876] CPU: 2 PID: 1728 Comm: page-types Not tainted

[PATCH v3] cros_ec: cleanup dependency chain for cros_ec modules

2018-06-04 Thread Enrico Granata
From: Enrico Granata If one builds the Chrome EC support as modules, there is no explicit dependency chain amongst the several modules (LPC, CHARDEV, CORE, ...) This makes it possible - for instance - to rmmod cros_ec_core, even though cros_ec_dev actively uses it for data transport to the EC

[PATCH v2] cros_ec: cleanup dependency chain for cros_ec modules

2018-06-04 Thread Enrico Granata
From: Enrico Granata If one builds the Chrome EC support as modules, there is no explicit dependency chain amongst the several modules (LPC, CHARDEV, CORE, ...) This makes it possible - for instance - to rmmod cros_ec_core, even though cros_ec_dev actively uses it for data transport to the EC

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

2018-06-04 Thread Stephen Rothwell
Hi all, On Tue, 5 Jun 2018 10:34:03 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the xfs tree got a conflict in: > > fs/gfs2/bmap.c > > between commit: > > 628e366df11c ("gfs2: Iomap cleanups and improvements") > > from Linus' tree and commit: > > 7ee66c03e40a

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

2018-06-04 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the xfs tree got a conflict in: fs/gfs2/bmap.c between commit: 628e366df11c ("gfs2: Iomap cleanups and improvements") from Linus' tree and commit: 7ee66c03e40a ("iomap: move IOMAP_F_BOUNDARY to gfs2") from the xfs tree. I fixed it up (see below)

Re: linux-next: manual merge of the vfs tree with the overlayfs tree

2018-06-04 Thread Stephen Rothwell
Hi all, On Tue, 29 May 2018 11:30:35 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the vfs tree got a conflict in: > > fs/read_write.c > > between commit: > > 63ea46a359b2 ("vfs: dedupe: extract helper for a single dedup") > > from the overlayfs tree and commit: > >

linux-next: build warning after merge of the nfs tree

2018-06-04 Thread Stephen Rothwell
Hi Trond, After merging the nfs tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: fs/nfs/nfs4proc.c:910:13: warning: 'nfs4_layoutget_release' defined but not used [-Wunused-function] static void nfs4_layoutget_release(void *calldata)

Re: [PATCH v5 24/31] kconfig: add CC_IS_GCC and GCC_VERSION

2018-06-04 Thread Masahiro Yamada
Hi Stefan 2018-06-05 6:49 GMT+09:00 Stefan Agner : > Hi Masahiro, > > On 28.05.2018 11:22, Masahiro Yamada wrote: >> This will be useful to specify the required compiler version, >> like this: >> >> config FOO >> bool "Use Foo" >> depends on GCC_VERSION >= 40800 >> help >>

Re: [PATCH] Cleanup dependency chain for cros_ec modules

2018-06-04 Thread Gwendal Grignou
On Mon, Jun 4, 2018 at 1:22 PM Enrico Granata wrote: > > From: Enrico Granata > > If one builds the Chrome EC support as modules, there is no explicit > dependency chain amongst the several modules (LPC, CHARDEV, CORE, ...) > > This makes it possible - for instance - to rmmod cros_ec_core, even

[PATCH] uart: fix race between uart_put_char() and uart_shutdown()

2018-06-04 Thread Tycho Andersen
We have reports of the following crash: PID: 7 TASK: 88085c6d61c0 CPU: 1 COMMAND: "kworker/u25:0" #0 [88085c6db710] machine_kexec at 81046239 #1 [88085c6db760] crash_kexec at 810fc248 #2 [88085c6db830] oops_end at 81008ae7 #3

Re: [PATCH 1/2] HID: multitouch: report MT_TOOL_PALM for non-confident touches

2018-06-04 Thread Dmitry Torokhov
On Tue, Jun 05, 2018 at 09:51:14AM +1000, Peter Hutterer wrote: > On Mon, Jun 04, 2018 at 04:28:01PM -0700, Dmitry Torokhov wrote: > > On Tue, Jun 05, 2018 at 09:06:24AM +1000, Peter Hutterer wrote: > > > On Mon, Jun 04, 2018 at 02:32:55PM -0700, Dmitry Torokhov wrote: > > > > On Mon, Jun 04, 2018

Re: [PATCH 7/7] regulator: core: Enable voltage balancing

2018-06-04 Thread kbuild test robot
Hi Maciej, Thank you for the patch! Yet something to improve: [auto build test ERROR on regulator/for-next] [also build test ERROR on next-20180604] [cannot apply to v4.17] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https

Re: [PATCH 1/2] HID: multitouch: report MT_TOOL_PALM for non-confident touches

2018-06-04 Thread Peter Hutterer
On Mon, Jun 04, 2018 at 04:28:01PM -0700, Dmitry Torokhov wrote: > On Tue, Jun 05, 2018 at 09:06:24AM +1000, Peter Hutterer wrote: > > On Mon, Jun 04, 2018 at 02:32:55PM -0700, Dmitry Torokhov wrote: > > > On Mon, Jun 04, 2018 at 10:59:16PM +0200, Benjamin Tissoires wrote: > > > > On Mon, Jun 4,

Re: [PATCH v9 2/7] i2c: Add FSI-attached I2C master algorithm

2018-06-04 Thread Benjamin Herrenschmidt
On Mon, 2018-06-04 at 22:21 +0300, Andy Shevchenko wrote: > > +#define I2C_INT_ENABLE 0xff80 > > +#define I2C_INT_ERR0xfcc0 > > Now it looks like a flags combinations. > For me as for reader would be better to see quickly a decoded line. > > My proposal is to

Re: [PATCH v9 3/7] i2c: fsi: Add port structures

2018-06-04 Thread Benjamin Herrenschmidt
On Mon, 2018-06-04 at 22:17 +0300, Andy Shevchenko wrote: > > > +static int fsi_i2c_remove(struct device *dev) > > +{ > > + struct fsi_i2c_master *i2c = dev_get_drvdata(dev); > > + struct fsi_i2c_port *port; > > + > > + list_for_each_entry(port, >ports, list) { > > +

Re: [PATCH 5/6 v2] mtd: rawnand: ams-delta: use GPIO lookup table

2018-06-04 Thread Boris Brezillon
On Tue, 5 Jun 2018 01:09:32 +0200 Boris Brezillon wrote: > On Mon, 04 Jun 2018 18:48:08 +0200 > Janusz Krzysztofik wrote: > > > On Monday, June 4, 2018 11:55:43 AM CEST Boris Brezillon wrote: > > > On Wed, 30 May 2018 22:39:03 +0200 > > > > > > Janusz Krzysztofik wrote: > > > > On

Re: [PATCH 1/2] HID: multitouch: report MT_TOOL_PALM for non-confident touches

2018-06-04 Thread Dmitry Torokhov
On Tue, Jun 05, 2018 at 09:06:24AM +1000, Peter Hutterer wrote: > On Mon, Jun 04, 2018 at 02:32:55PM -0700, Dmitry Torokhov wrote: > > On Mon, Jun 04, 2018 at 10:59:16PM +0200, Benjamin Tissoires wrote: > > > On Mon, Jun 4, 2018 at 8:26 PM, Dmitry Torokhov > > > wrote: > > > > On Mon, Jun 04,

Re: [PATCHv2 01/16] atomics/treewide: s/__atomic_add_unless/atomic_fetch_add_unless/

2018-06-04 Thread Palmer Dabbelt
On Tue, 29 May 2018 08:43:31 PDT (-0700), mark.rutl...@arm.com wrote: While __atomic_add_unless was originally intended as a building-block for atomic_add_unless, it's now used in a number of places around the kernel. It's the only common atomic operation named __atomic*(), rather than

Re: [PATCHv2 04/16] atomics/treewide: make atomic_fetch_add_unless() optional

2018-06-04 Thread Palmer Dabbelt
On Tue, 29 May 2018 08:43:34 PDT (-0700), mark.rutl...@arm.com wrote: Several architectures these have a near-identical implementation based on atomic_read() and atomic_cmpxchg() that we can instead define in , so let's do so, using something close to the existing x86 implementation with

Re: [PATCHv2 02/16] atomics/treewide: remove redundant atomic_inc_not_zero() definitions

2018-06-04 Thread Palmer Dabbelt
On Tue, 29 May 2018 08:43:32 PDT (-0700), mark.rutl...@arm.com wrote: When atomic_inc_not_zero(v) isn't defined, will define it as falling back to atomic_add_unless((v), 1, 0), so there's no need for arch code to do so. There should be no functional change as a result of this patch.

Re: [PATCHv2 15/16] atomics/treewide: make unconditional inc/dec ops optional

2018-06-04 Thread Palmer Dabbelt
On Tue, 29 May 2018 08:43:45 PDT (-0700), mark.rutl...@arm.com wrote: Many of the inc/dec ops are mandatory, but for most architectures inc/dec are simply trivial wrappers around their corresponding add/sub ops. Let's make all the inc/dec ops optional, so that we can get rid of these

Re: [PATCHv2 13/16] atomics/treewide: make test ops optional

2018-06-04 Thread Palmer Dabbelt
On Tue, 29 May 2018 08:43:43 PDT (-0700), mark.rutl...@arm.com wrote: Some of the atomics return the result of a test applied after the atomic operation, and almost all architectures implement these as trivial wrappers around the underlying atomic. Specifically: * _inc_and_test(v) is

Re: [PATCHv2 03/16] atomics/treewide: make atomic64_inc_not_zero() optional

2018-06-04 Thread Palmer Dabbelt
On Tue, 29 May 2018 08:43:33 PDT (-0700), mark.rutl...@arm.com wrote: We define a trivial fallback for atomic_inc_not_zero(), but don't do the same for atmic64_inc_not_zero(), leading most architectures to define the same boilerplate. atmic64 Let's add a fallback in , and remove the

Re: [PATCHv2 11/16] atomics/riscv: define atomic64_fetch_add_unless()

2018-06-04 Thread Palmer Dabbelt
On Tue, 29 May 2018 08:43:41 PDT (-0700), mark.rutl...@arm.com wrote: As a step towards unifying the atomic/atomic64/atomic_long APIs, this patch converts the arch/riscv implementation of atomic64_add_unless() into an implementation of atomic64_fetch_add_unless(). A wrapper in will build

[git pull] Input updates for v4.18-rc0

2018-06-04 Thread Dmitry Torokhov
Hi Linus, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus to receive updates for the input subsystem. You will get: - a new driver to ChipOne icn8505 based touchscreens - on certain systems with Elan touch controllers they will be switched

Re: [PATCH 7/7] regulator: core: Enable voltage balancing

2018-06-04 Thread kbuild test robot
Hi Maciej, Thank you for the patch! Yet something to improve: [auto build test ERROR on regulator/for-next] [also build test ERROR on next-20180604] [cannot apply to v4.17] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https

Re: [PATCH] arm64: dts: stingray: Add otp device node

2018-06-04 Thread Scott Branden
On 18-06-04 03:41 PM, Florian Fainelli wrote: On 06/04/2018 03:33 PM, Scott Branden wrote: On 18-06-04 02:33 PM, Florian Fainelli wrote: On 06/04/2018 02:30 PM, Scott Branden wrote: Hi Florian, On 18-06-04 02:24 PM, Florian Fainelli wrote: On 05/23/2018 01:17 PM, Scott Branden wrote:

Re: [PATCH 5/6 v2] mtd: rawnand: ams-delta: use GPIO lookup table

2018-06-04 Thread Boris Brezillon
On Mon, 04 Jun 2018 18:48:08 +0200 Janusz Krzysztofik wrote: > On Monday, June 4, 2018 11:55:43 AM CEST Boris Brezillon wrote: > > On Wed, 30 May 2018 22:39:03 +0200 > > > > Janusz Krzysztofik wrote: > > > On Wednesday, May 30, 2018 7:52:20 PM CEST Boris Brezillon wrote: > > > > On Wed, 30

Re: [PATCH] iw_cxgb4: add INFINIBAND_ADDR_TRANS dependency

2018-06-04 Thread Jason Gunthorpe
On Thu, May 31, 2018 at 02:40:59PM -0400, Doug Ledford wrote: > On Wed, 2018-05-30 at 21:03 -0700, Greg Thelen wrote: > > On Wed, May 30, 2018 at 4:01 PM Jason Gunthorpe wrote: > > > > > On Thu, May 31, 2018 at 12:40:54AM +0200, Arnd Bergmann wrote: > > > > > On 5/30/2018 5:25 PM, Jason

Re: [PATCH 1/2] HID: multitouch: report MT_TOOL_PALM for non-confident touches

2018-06-04 Thread Peter Hutterer
On Mon, Jun 04, 2018 at 02:32:55PM -0700, Dmitry Torokhov wrote: > On Mon, Jun 04, 2018 at 10:59:16PM +0200, Benjamin Tissoires wrote: > > On Mon, Jun 4, 2018 at 8:26 PM, Dmitry Torokhov > > wrote: > > > On Mon, Jun 04, 2018 at 07:55:57PM +0200, Henrik Rydberg wrote: > > >> Hi Dmitry, > > >> > >

Re: [PATCH] module: exclude SHN_UNDEF symbols from kallsyms api

2018-06-04 Thread Josh Poimboeuf
On Mon, Jun 04, 2018 at 05:56:05PM -0500, Josh Poimboeuf wrote: > On Mon, Jun 04, 2018 at 09:54:12AM -0500, Josh Poimboeuf wrote: > > On Mon, Jun 04, 2018 at 04:05:11PM +0200, Jessica Yu wrote: > > > +++ Josh Poimboeuf [04/06/18 08:16 -0500]: > > > > On Mon, Jun 04, 2018 at 03:01:31PM +0200,

Re: [PATCH 1/2] HID: multitouch: report MT_TOOL_PALM for non-confident touches

2018-06-04 Thread Peter Hutterer
On Mon, Jun 04, 2018 at 02:19:44PM -0700, Dmitry Torokhov wrote: > On Mon, Jun 04, 2018 at 10:42:31PM +0200, Benjamin Tissoires wrote: > > On Mon, Jun 4, 2018 at 7:33 PM, Dmitry Torokhov > > wrote: > > > On Mon, Jun 04, 2018 at 03:18:12PM +0200, Benjamin Tissoires wrote: > > >> On Fri, Jun 1,

Re: [PATCH] module: exclude SHN_UNDEF symbols from kallsyms api

2018-06-04 Thread Josh Poimboeuf
On Mon, Jun 04, 2018 at 09:54:12AM -0500, Josh Poimboeuf wrote: > On Mon, Jun 04, 2018 at 04:05:11PM +0200, Jessica Yu wrote: > > +++ Josh Poimboeuf [04/06/18 08:16 -0500]: > > > On Mon, Jun 04, 2018 at 03:01:31PM +0200, Jessica Yu wrote: > > > > +++ Jessica Yu [04/06/18 11:54 +0200]: > > > > >

Re: [PATCH] arm64: dts: stingray: Add otp device node

2018-06-04 Thread Florian Fainelli
On 06/04/2018 03:33 PM, Scott Branden wrote: > > > On 18-06-04 02:33 PM, Florian Fainelli wrote: >> On 06/04/2018 02:30 PM, Scott Branden wrote: >>> Hi Florian, >>> >>> >>> On 18-06-04 02:24 PM, Florian Fainelli wrote: On 05/23/2018 01:17 PM, Scott Branden wrote: > Add otp device node

Re: ptrval hiding -- first kernel messages look rather "interesting"

2018-06-04 Thread Steven Rostedt
On Fri, 1 Jun 2018 12:31:44 +0200 Pavel Machek wrote: > Hi! > > v4.17 on n900: > > [0.00] Virtual kernel memory layout: > [0.00] vector : 0x - 0x1000 ( 4 kB) > [0.00] fixmap : 0xffc0 - 0xfff0 (3072 kB) > [0.00] vmalloc :

Re: [PATCH] arm64: dts: stingray: Add otp device node

2018-06-04 Thread Scott Branden
On 18-06-04 02:33 PM, Florian Fainelli wrote: On 06/04/2018 02:30 PM, Scott Branden wrote: Hi Florian, On 18-06-04 02:24 PM, Florian Fainelli wrote: On 05/23/2018 01:17 PM, Scott Branden wrote: Add otp device node for Stingray SOC. Fixes: 2fa9e9e29ea2 ("arm64: dts: Add GPIO DT nodes for

Re: [PATCH] arm64: dts: stingray: move common board components to stingray-board-base

2018-06-04 Thread Scott Branden
Hi Florian, On 18-06-04 02:09 PM, Florian Fainelli wrote: On 05/22/2018 11:55 AM, Scott Branden wrote: Move common board components from base bcm958742 dtsi file to new stingray-board-base dtsi file so they can be shared between many stingray boards following common design. Signed-off-by:

  1   2   3   4   5   6   7   8   9   >