[PATCH v2 3/5] input: misc: bma150: Add support for device tree

2019-02-02 Thread Paweł Chmiel
From: Jonathan Bakker Add of_match table to enable bma150 to be probed via DT Changes from v1: - Add properties for all of bma150_cfg Signed-off-by: Jonathan Bakker Signed-off-by: Paweł Chmiel --- drivers/input/misc/bma150.c | 64 - include/linux/bma150.h

Re: [PATCH] x86/mce: Initialize "bank" when we find a fatal error in mce_no_way_out()

2019-02-02 Thread Borislav Petkov
On Fri, Feb 01, 2019 at 10:36:17AM -0800, Luck, Tony wrote: > > so it'll be more robust if we moved it there. > > It would be redundant to move it there for both > existing uses. Maybe. But if the bank write happens there, it won't be "forgotten" again. I don't care what the functions are called

[PATCH net-next v5 00/12] net: y2038-safe socket timestamps

2019-02-02 Thread Deepa Dinamani
The series introduces new socket timestamps that are y2038 safe. The time data types used for the existing socket timestamp options: SO_TIMESTAMP, SO_TIMESTAMPNS and SO_TIMESTAMPING are not y2038 safe. The series introduces SO_TIMESTAMP_NEW, SO_TIMESTAMPNS_NEW and SO_TIMESTAMPING_NEW to replace th

[PATCH net-next v5 04/12] sockopt: Rename SO_TIMESTAMP* to SO_TIMESTAMP*_OLD

2019-02-02 Thread Deepa Dinamani
SO_TIMESTAMP, SO_TIMESTAMPNS and SO_TIMESTAMPING options, the way they are currently defined, are not y2038 safe. Subsequent patches in the series add new y2038 safe versions of these options which provide 64 bit timestamps on all architectures uniformly. Hence, rename existing options with OLD tag

[PATCH net-next v5 02/12] socket: move compat timeout handling into sock.c

2019-02-02 Thread Deepa Dinamani
From: Arnd Bergmann This is a cleanup to prepare for the addition of 64-bit time_t in O_SNDTIMEO/O_RCVTIMEO. The existing compat handler seems unnecessarily complex and error-prone, moving it all into the main setsockopt()/getsockopt() implementation requires half as much code and is easier to ex

[PATCH net-next v5 01/12] selftests: add missing include unistd

2019-02-02 Thread Deepa Dinamani
Compiling rxtimestamp.c generates error messages due to non-existing declaration for write() library call. Add missing unistd.h include to provide the declaration and silence the error. Signed-off-by: Deepa Dinamani Acked-by: Willem de Bruijn --- tools/testing/selftests/networking/timestamping

[PATCH net-next v5 03/12] arch: Use asm-generic/socket.h when possible

2019-02-02 Thread Deepa Dinamani
Many architectures maintain an arch specific copy of the file even though there are no differences with the asm-generic one. Allow these architectures to use the generic one instead. Signed-off-by: Deepa Dinamani Acked-by: Max Filippov Acked-by: Heiko Carstens Acked-by: Willem de Bruijn Cc: ch

[PATCH net-next v5 05/12] arch: sparc: Override struct __kernel_old_timeval

2019-02-02 Thread Deepa Dinamani
struct __kernel_old_timeval is supposed to have the same layout as struct timeval. But, it was inadvarently missed that __kernel_suseconds has a different definition for sparc64. Provide an asm-specific override that fixes it. Reported-by: Arnd Bergmann Suggested-by: Arnd Bergmann Signed-off-by:

[PATCH net-next v5 11/12] socket: Rename SO_RCVTIMEO/ SO_SNDTIMEO with _OLD suffixes

2019-02-02 Thread Deepa Dinamani
SO_RCVTIMEO and SO_SNDTIMEO socket options use struct timeval as the time format. struct timeval is not y2038 safe. The subsequent patches in the series add support for new socket timeout options with _NEW suffix that will use y2038 safe data structures. Although the existing struct timeval layout

[PATCH net-next v5 07/12] socket: Add struct __kernel_sock_timeval

2019-02-02 Thread Deepa Dinamani
The new type is meant to be used as a y2038 safe structure to be used as part of cmsg data. Presently the SO_TIMESTAMP socket option uses struct timeval for timestamps. This is not y2038 safe. Subsequent patches in the series add new y2038 safe socket option to be used in the place of SO_TIMESTAMP_

[PATCH net-next v5 09/12] socket: Add SO_TIMESTAMPING_NEW

2019-02-02 Thread Deepa Dinamani
Add SO_TIMESTAMPING_NEW variant of socket timestamp options. This is the y2038 safe versions of the SO_TIMESTAMPING_OLD for all architectures. Signed-off-by: Deepa Dinamani Acked-by: Willem de Bruijn Cc: ch...@zankel.net Cc: fenghua...@intel.com Cc: r...@twiddle.net Cc: t...@linutronix.de Cc: ub

[PATCH net-next v5 08/12] socket: Add SO_TIMESTAMP[NS]_NEW

2019-02-02 Thread Deepa Dinamani
Add SO_TIMESTAMP_NEW and SO_TIMESTAMPNS_NEW variants of socket timestamp options. These are the y2038 safe versions of the SO_TIMESTAMP_OLD and SO_TIMESTAMPNS_OLD for all architectures. Note that the format of scm_timestamping.ts[0] is not changed in this patch. Signed-off-by: Deepa Dinamani Ack

[PATCH net-next v5 10/12] socket: Update timestamping Documentation

2019-02-02 Thread Deepa Dinamani
With the new y2038 safe timestamping options added, update the documentation to reflect the changes. Signed-off-by: Deepa Dinamani Acked-by: Willem de Bruijn --- Documentation/networking/timestamping.txt | 43 --- 1 file changed, 38 insertions(+), 5 deletions(-) diff --git

[PATCH net-next v5 06/12] socket: Use old_timeval types for socket timestamps

2019-02-02 Thread Deepa Dinamani
As part of y2038 solution, all internal uses of struct timeval are replaced by struct __kernel_old_timeval and struct compat_timeval by struct old_timeval32. Make socket timestamps use these new types. This is mainly to be able to verify that the kernel build is y2038 safe when such non y2038 safe

[PATCH net-next v5 12/12] sock: Add SO_RCVTIMEO_NEW and SO_SNDTIMEO_NEW

2019-02-02 Thread Deepa Dinamani
Add new socket timeout options that are y2038 safe. Signed-off-by: Deepa Dinamani Acked-by: Willem de Bruijn Cc: ccaul...@redhat.com Cc: da...@davemloft.net Cc: del...@gmx.de Cc: pau...@samba.org Cc: r...@linux-mips.org Cc: r...@twiddle.net Cc: cluster-de...@redhat.com Cc: linuxppc-...@lists.ozl

Re: [PATCH v4 1/2] iio: light: add driver for MAX44009

2019-02-02 Thread Jonathan Cameron
On Thu, 31 Jan 2019 07:29:01 -0800 Robert Eshleman wrote: > The MAX44009 is a low-power ambient light sensor from Maxim > Integrated. It differs from the MAX44000 in that it doesn't have > proximity sensing and that it requires far less current (1 micro-amp > vs 5 micro-amps). The register mappin

[RFC PATCH] clk: sunxi-ng: sun4i: Use CLK_SET_RATE_PARENT for mmc2 clock

2019-02-02 Thread Priit Laes
Recent patch of improving MP clock rate calculations by taking into account whether adjusting parent rate is allowed, have unfortunately broken eMMC support on A20 Olinuxino-Lime2-eMMC boards which fail with following error: [snip] EXT4-fs (mmcblk1p4): INFO: recovery required on readonly filesyste

Re: [PATCH v4 2/2] dt-bindings: iio: light: Add max44009

2019-02-02 Thread Jonathan Cameron
On Thu, 31 Jan 2019 07:49:16 -0800 Robert Eshleman wrote: > Adds device tree bindings for the max44009 light sensor. > > Signed-off-by: Robert Eshleman Still time for Rob to comment if he want's to, but I think with few tweaks as below this matches what he asked for. Applied to the togreg bra

Re: [RFC net-next 01/13] switchdev: Add SWITCHDEV_PORT_ATTR_SET, SWITCHDEV_PORT_ATTR_GET

2019-02-02 Thread Jiri Pirko
Fri, Feb 01, 2019 at 11:06:45PM CET, f.faine...@gmail.com wrote: >In preparation for allowing switchdev enabled drivers to veto specific >attribute settings from within the context of the caller, introduce a >new switchdev notifier type for port attributes. > >Suggested-by: Ido Schimmel >Signed-of

Re: [PATCH] drivers: iio: Fix wrong license for ADI drivers

2019-02-02 Thread Jonathan Cameron
On Fri, 1 Feb 2019 18:04:32 +0200 Stefan Popa wrote: > Analog Devices drivers are typically GPL v2 only. This patch fixes the > inconsistencies between the module license and SPDX. > > Signed-off-by: Stefan Popa Hi Stefan, This is mostly fine where it is making sure things are consistent. Howe

Re: [RFC net-next 00/13] Get rid of switchdev_ops

2019-02-02 Thread Jiri Pirko
Fri, Feb 01, 2019 at 11:06:44PM CET, f.faine...@gmail.com wrote: >Hi all, > >This patch series converts SWITCHDEV_PORT_ATTR_{GET,SET} to use a >blocking notifier, similar to how SWITCHDEV_PORT_OBJ_{ADD,DEL} has been >changed recently by Petr. > >This was suggested by Ido to help with a particular u

Re: [PATCH V5 2/7] clocksource: tegra: add Tegra210 timer support

2019-02-02 Thread Joseph Lo
On 2/2/19 9:30 PM, Dmitry Osipenko wrote: 01.02.2019 18:37, Joseph Lo пишет: On 2/1/19 11:13 PM, Dmitry Osipenko wrote: 01.02.2019 17:13, Joseph Lo пишет: On 2/1/19 9:54 PM, Jon Hunter wrote: On 01/02/2019 13:11, Dmitry Osipenko wrote: 01.02.2019 16:06, Dmitry Osipenko пишет: 01.02.2019 6:

[PATCH 2/2] linux/kernel.h: split *_MAX and *_MIN macros into

2019-02-02 Thread Masahiro Yamada
tends to be cluttered because we often put various sort of unrelated stuff in it. So, we have split out a sensible chunk of code into a separate header from time to time. This commit splits out the *_MAX and *_MIN defines. The standard header contains various MAX, MIN constants including numeri

[PATCH 1/2] linux/kernel.h: use 'short' to define USHRT_MAX, SHRT_MAX, SHRT_MIN

2019-02-02 Thread Masahiro Yamada
The log of commit 44f564a4bf6a ("ipc: add definitions of USHORT_MAX and others") did not explain why it used (s16) and (u16) instead of (short) and (unsigned short). Let's use (short) and (unsigned short), which is more sensible, and more consistent with the other MAX/MIN defines. As you see in i

Re: [PATCH V5 2/7] clocksource: tegra: add Tegra210 timer support

2019-02-02 Thread Joseph Lo
On 2/2/19 9:38 PM, Dmitry Osipenko wrote: 02.02.2019 2:53, Joseph Lo пишет: On 2/2/19 2:08 AM, Dmitry Osipenko wrote: 01.02.2019 18:37, Joseph Lo пишет: On 2/1/19 11:13 PM, Dmitry Osipenko wrote: 01.02.2019 17:13, Joseph Lo пишет: On 2/1/19 9:54 PM, Jon Hunter wrote: On 01/02/2019 13:11, D

Want to retouch?

2019-02-02 Thread Grace
Want to retouch your photos? we can help you. Deep etching or masking for your photos, or even adding clipping path. Retouching also if needed. Hopefully to start something for you soon. Thanks, Grace Bremerhdaven Wunsdtorf

Want to retouch?

2019-02-02 Thread Grace
Want to retouch your photos? we can help you. Deep etching or masking for your photos, or even adding clipping path. Retouching also if needed. Hopefully to start something for you soon. Thanks, Grace Aaledn Hdaltern

Applied "ASoC: dapm: Add warnings for widget overwrite when adding route" to the asoc tree

2019-02-02 Thread Mark Brown
The patch ASoC: dapm: Add warnings for widget overwrite when adding route has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "regulator: rk808: Fix BUCK1/2 voltages on rk805" to the regulator tree

2019-02-02 Thread Mark Brown
The patch regulator: rk808: Fix BUCK1/2 voltages on rk805 has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Applied "regulator: uniphier: Constify uniphier_regulator_ops" to the regulator tree

2019-02-02 Thread Mark Brown
The patch regulator: uniphier: Constify uniphier_regulator_ops has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 ho

Applied "regulator: uniphier: Fix probe error handling" to the regulator tree

2019-02-02 Thread Mark Brown
The patch regulator: uniphier: Fix probe error handling has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) an

[PATCH] PCI: Consider alignment of hot-added bridges when distributing available resources

2019-02-02 Thread Nicholas Johnson
New systems with Thunderbolt are starting to use native PCI enumeration. Mika Westerberg's patch "PCI: Distribute available resources to hotplug capable PCIe downstream ports" (https://patchwork.kernel.org/patch/9972155/) adds code to expand downstream PCI hotplug bridges to consume all remaining r

Re: [PATCH 1/2] linux/kernel.h: use 'short' to define USHRT_MAX, SHRT_MAX, SHRT_MIN

2019-02-02 Thread Alexey Dobriyan
On Sun, Feb 03, 2019 at 01:06:24AM +0900, Masahiro Yamada wrote: > The log of commit 44f564a4bf6a ("ipc: add definitions of USHORT_MAX > and others") did not explain why it used (s16) and (u16) instead of > (short) and (unsigned short). > > Let's use (short) and (unsigned short), which is more sen

Re: [PATCH 1/2] linux/kernel.h: use 'short' to define USHRT_MAX, SHRT_MAX, SHRT_MIN

2019-02-02 Thread Alexey Dobriyan
On Sat, Feb 02, 2019 at 07:31:05PM +0300, Alexey Dobriyan wrote: > On Sun, Feb 03, 2019 at 01:06:24AM +0900, Masahiro Yamada wrote: > > The log of commit 44f564a4bf6a ("ipc: add definitions of USHORT_MAX > > and others") did not explain why it used (s16) and (u16) instead of > > (short) and (unsign

Re: [PATCH v2 0/4] clk: meson: rework drivers dependencies

2019-02-02 Thread Neil Armstrong
Hi, Le 01/02/2019 13:58, Jerome Brunet a écrit : > The goal of this patchset to clean-up the dependencies between > the controllers and the different clock drivers provided in the meson > directory. The expected result is that each controllers can pick the > the clock drivers they need, without ne

Re: [PATCH net-next 00/12] code optimizations & bugfixes for HNS3 driver

2019-02-02 Thread David Miller
From: Huazhong Tan Date: Sat, 2 Feb 2019 22:39:25 +0800 > This patchset includes bugfixes and code optimizations for the HNS3 > ethernet controller driver Series applied.

Re: Frequent dwc3 crashes on suspend or reboot since 5.0-rc1

2019-02-02 Thread Alan Stern
On Fri, 1 Feb 2019, John Stultz wrote: > Hey all, > Since the 5.0 merge window opened, I've been tripping on frequent > dwc3 crashes on reboot and suspend, which I've added an example to the > bottom of this mail. > > I've dug in a little bit and sort of have a sense of whats going on. > > In

Re: [PATCH v6 0/4] clk: meson-g12a: Add EE clock controller driver

2019-02-02 Thread Neil Armstrong
Hi, Le 01/02/2019 15:53, Jerome Brunet a écrit : > This purpose of this patchset is to the main clock controller of the > g12a SoC family > > This patchset depends on the recent rework the meson clock directory [7]. > > Changes since v5 [6]: > * use clock input driver until something better com

Re: [PATCH] swiotlb: Return error from swiotlb_init_with_tbl()

2019-02-02 Thread Christoph Hellwig
On Fri, Feb 01, 2019 at 05:59:01PM +0100, Joerg Roedel wrote: > > > This sounds like a change to break quite a couple of places in the > > > kernel. But okay, it just makes this hunk obsolete. > > > > He also added either explicit panic calls or error handling (panic > > in case of swiotlb): > >

Re: [PATCH v2 1/2] staging: iio: frequency: ad9833: Get frequency value statically

2019-02-02 Thread Jonathan Cameron
On Fri, 1 Feb 2019 17:01:37 +0200 Beniamin Bia wrote: > From: Beniamin Bia > > The values from platform data were replaced by statically values. > This was just a intermediate step of taking this driver out of staging and > load data from device tree. > > Signed-off-by: Beniamin Bia Applied t

Re: [GIT PULL] bcm2835-dt-64-next-2019-02-01

2019-02-02 Thread Florian Fainelli
Le 2/1/19 à 3:02 PM, Stefan Wahren a écrit : > Hi Florian, > > this is the fixup version (cherry picked the patch with the reference target) > of the dt-64-next pull request. Please consider this as a replacement for > the broken dt-64-next pull request. > > The following changes since commit bfe

Re: [PATCH v2 2/2] staging: iio: frequency: ad9833: Load clock using clock framework

2019-02-02 Thread Jonathan Cameron
On Fri, 1 Feb 2019 17:01:38 +0200 Beniamin Bia wrote: > From: Beniamin Bia > > The clock frequency is loaded from device-tree using clock framework > instead of statically value. The change allow configuration of > the device via device-trees and better initialization sequence. > This is part o

Re: [PATCH] iio: chemical: sps30: remove printk format specifier

2019-02-02 Thread Jonathan Cameron
On Sat, 2 Feb 2019 10:00:03 +0100 Tomasz Duszynski wrote: > pr_fmt is used by printk wrappers. There are not any in the driver > code so remove the format specifier. > > Signed-off-by: Tomasz Duszynski Applied to the togreg branch of iio.git and pushed out as testing for the autobuilders to mo

[GIT PULL] Devicetree fix for 5.0-rc5

2019-02-02 Thread Rob Herring
Linus, Please pull. Rob The following changes since commit 75a080cde08d2dcba19ee864f9732094d93fab41: powerpc: chrp: Use of_node_is_type to access device_type (2019-01-19 10:35:42 -0600) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git ta

Re: [PATCH v3 3/3] dt-bindings: iio: chemical: pms7003: add device tree support

2019-02-02 Thread Jonathan Cameron
On Fri, 1 Feb 2019 22:57:59 +0100 Tomasz Duszynski wrote: > Add device tree support for Plantower PMS7003 particulate matter sensor. > > Signed-off-by: Tomasz Duszynski Hi Tomasz, Sorry, I clearly didn't look at this in enough detail on earlier versions. I think the set gpio is rather device

Re: [PATCH] dell_rbu: stop abusing the DMA API

2019-02-02 Thread Christoph Hellwig
On Fri, Feb 01, 2019 at 03:15:59PM -0800, Darren Hart wrote: > On Tue, Jan 29, 2019 at 08:34:09AM +0100, Christoph Hellwig wrote: > > For some odd reason dell_rbu actually seems to want the physical and > > not a bus address for the allocated buffer. Lets assume that actually > > is correct given

Re: [PATCH v5 08/13] x86/fsgsbase/64: Introduce the FIND_PERCPU_BASE macro

2019-02-02 Thread Andy Lutomirski
On Fri, Feb 1, 2019 at 12:55 PM Chang S. Bae wrote: > > GSBASE is used to find per-CPU data in the kernel. But when it is unknown, > the per-CPU base can be found from the per_cpu_offset table with a CPU NR. > The CPU NR is extracted from the limit field of the CPUNODE entry in GDT, > or by the RD

Re: [PATCH v3 1/3] iio: chemical: add support for Plantower PMS7003 sensor

2019-02-02 Thread Jonathan Cameron
On Fri, 1 Feb 2019 22:57:57 +0100 Tomasz Duszynski wrote: > Add support for Plantower PMS7003 particulate matter sensor. > > Signed-off-by: Tomasz Duszynski Other than waiting for review of the binding and potentially that minor change to the gpio naming I suggested, this looks good to me. Th

Re: [PATCH net-next v5 12/12] sock: Add SO_RCVTIMEO_NEW and SO_SNDTIMEO_NEW

2019-02-02 Thread Oliver Hartkopp
Hi all, On 02.02.19 16:34, Deepa Dinamani wrote: Add new socket timeout options that are y2038 safe. (..) diff --git a/arch/alpha/include/uapi/asm/socket.h b/arch/alpha/include/uapi/asm/socket.h index 9826d1db71d0..0d0fddb7e738 100644 --- a/arch/alpha/include/uapi/asm/socket.h +++ b/arch/alp

Re: [PATCH 02/18] dmaengine: imx-sdma: pass struct device to DMA API functions

2019-02-02 Thread Christoph Hellwig
On Sat, Feb 02, 2019 at 03:41:21PM +0530, Vinod Koul wrote: > On 01-02-19, 09:47, Christoph Hellwig wrote: > > The DMA API generally relies on a struct device to work properly, and > > only barely works without one for legacy reasons. Pass the easily > > available struct device from the platform_d

Re: [PATCH v5 07/13] x86/fsgsbase/64: When copying a thread, use the FSGSBASE instructions if available

2019-02-02 Thread Andy Lutomirski
On Fri, Feb 1, 2019 at 12:54 PM Chang S. Bae wrote: > > Copy real FS/GSBASE values instead of approximation when FSGSBASE is > enabled. > > Factoring out to save_fsgs() does not result in the same behavior because > save_base_legacy() does not copy FS/GSBASE when the index is zero. > > Signed-off-

Re: [PATCH AUTOSEL 4.19 181/258] tools uapi asm: Update asm-generic/unistd.h copy

2019-02-02 Thread Sasha Levin
On Mon, Jan 28, 2019 at 05:56:55PM +0100, Arnd Bergmann wrote: On Mon, Jan 28, 2019 at 5:07 PM Sasha Levin wrote: From: Arnaldo Carvalho de Melo [ Upstream commit 89a0948984896352cac1ebe079cb3d64d6c3adc6 ] To get the change in: b7d624ab4312 ("asm-generic: unistd.h: fixup broken macro inc

Re: [PATCH AUTOSEL 4.19 083/258] drm: Move drm_mode_setcrtc() local re-init to failure path

2019-02-02 Thread Sasha Levin
On Mon, Jan 28, 2019 at 04:03:41PM -0500, Sean Paul wrote: On Mon, Jan 28, 2019 at 10:56:29AM -0500, Sasha Levin wrote: From: Sean Paul [ Upstream commit c232e9f41b136c141df9938024e521191a7b910d ] Instead of always re-initializing the variables we need to clean up on out, move the re-initiali

[PATCH] e1000e: Disable runtime PM on CNP+

2019-02-02 Thread Kai-Heng Feng
There are some new e1000e devices can only be woken up from D3 one time, by plugging ethernet cable. Subsequent cable plugging does set PME bit correctly, but it still doesn't get woken up. Since e1000e connects to the root complex directly, we rely on ACPI to wake it up. In this case, the GPE fro

Re: [PATCH] PCI / ACPI: Don't clear pme_poll on device that has unreliable ACPI wake

2019-02-02 Thread Kai Heng Feng
Hi Bjorn, > On Jan 28, 2019, at 3:51 PM, Kai Heng Feng > wrote: [snipped] >> If I understand correctly, the bugzilla lspci >> (https://bugzilla.kernel.org/attachment.cgi?id=280691) was collected >> at point 8, and it shows PME_Status=1 when it should be 0. >> >> If we write a 1 to PME_Status t

[PATCH] net: dsa: Fix lockdep false positive splat

2019-02-02 Thread Marc Zyngier
Creating a macvtap on a DSA-backed interface results in the following splat when lockdep is enabled: [ 19.638080] IPv6: ADDRCONF(NETDEV_CHANGE): lan0: link becomes ready [ 23.041198] device lan0 entered promiscuous mode [ 23.043445] device eth0 entered promiscuous mode [ 23.049255] [ 23.

Re: [PATCH] Move static keyword at beginning of declaration

2019-02-02 Thread Geoff Levand
On 2/2/19 5:05 AM, Mathieu Malaterre wrote: > Move the static keyword around to remove the following warnings (W=1): > > arch/powerpc/platforms/ps3/os-area.c:212:1: error: 'static' is not at > beginning of declaration [-Werror=old-style-declaration] > arch/powerpc/platforms/ps3/system-bus.c:4

Re: System crash with perf_fuzzer (kernel: 5.0.0-rc3)

2019-02-02 Thread Vince Weaver
On Fri, 1 Feb 2019, Jiri Olsa wrote: > > > > I've just started fuzzing with the patch applied. Often it takes a few > > hours to trigger the bug. > > cool, thanks I let it run overnight and no crash. > > Added question about this bug. It appeared that the crash was triggered > > by the BTS

Re: [PATCH] swiotlb: Return error from swiotlb_init_with_tbl()

2019-02-02 Thread kbuild test robot
Hi Joerg, I love your patch! Perhaps something to improve: [auto build test WARNING on swiotlb/linux-next] [also build test WARNING on v5.0-rc4] [cannot apply to next-20190201] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://gi

RE: [PATCH V9 3/5] i2c: tegra: Add DMA support

2019-02-02 Thread Sowjanya Komatineni
> > This patch adds DMA support for Tegra I2C. > > > > Tegra I2C TX and RX FIFO depth is 8 words. PIO mode is used for > > transfer size of the max FIFO depth and DMA mode is used for transfer > > size higher than max FIFO depth to save CPU overhead. > > > > PIO mode needs full intervention of

Re: perf_event_open+clone = unkillable process

2019-02-02 Thread Jiri Olsa
On Fri, Feb 01, 2019 at 06:06:03PM +0100, Dmitry Vyukov wrote: > On Fri, Feb 1, 2019 at 5:48 PM Dmitry Vyukov wrote: > > > > Hello, > > > > The following program creates an unkillable process that eats CPU. > > /proc/pid/stack is empty, I am not sure what other info I can provide. > > > > Tested i

Re: [PATCH 1/3] sched/wait: use freezable_schedule when possible

2019-02-02 Thread Joel Fernandes
On Fri, Feb 01, 2019 at 06:38:05AM +0100, Hugo Lefeuvre wrote: > Replace schedule(); try_to_freeze() by freezable_schedule(). > > Tasks calling freezable_schedule() set the PF_FREEZER_SKIP flag > before calling schedule(). Unlike tasks calling schedule(); > try_to_freeze() tasks calling freezable_

RE: [PATCH V9 3/5] i2c: tegra: Add DMA support

2019-02-02 Thread Sowjanya Komatineni
> +static int tegra_i2c_init_dma(struct tegra_i2c_dev *i2c_dev) { > +struct dma_chan *dma_chan; > +u32 *dma_buf; > +dma_addr_t dma_phys; > +int err = 0; > + > +if (!IS_ENABLED(CONFIG_TEGRA20_APB_DMA)) > +

Re: [GIT PULL] SCSI fixes for 5.0-rc4

2019-02-02 Thread pr-tracker-bot
The pull request you sent on Fri, 01 Feb 2019 16:06:45 -0800: > git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-fixes has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/3cde55ee7921609331178c84cca485491c97df2a Thank you! -- Deet-doot-dot, I am a bot. ht

Re: [GIT PULL] Devicetree fix for 5.0-rc5

2019-02-02 Thread pr-tracker-bot
The pull request you sent on Sat, 2 Feb 2019 11:10:06 -0600: > git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git > tags/devicetree-fixes-for-5.0-3 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/12491ed354d23c0ecbe02459bf4be58b8c772bc8 Thank you! -- Deet-

Re: [PATCH] platform/x86: intel_int0002_vgpio: Implement irq_set_wake

2019-02-02 Thread Maxim Mikityanskiy
On Sat, Feb 2, 2019 at 12:52 AM Hans de Goede wrote: > > Hi, > > On 1/31/19 8:47 PM, Maxim Mikityanskiy wrote: > > Hi, > > > > On Mon, Sep 24, 2018 at 5:37 PM Hans de Goede wrote: > >> > >> We were relying on the interrupt being shared with the ACPI SCI and the > >> ACPI core calling irq_set_wake

Re: [GIT PULL] libnvdimm fixes for v5.0-rc4

2019-02-02 Thread Linus Torvalds
On Sat, Jan 26, 2019 at 3:31 PM Williams, Dan J wrote: > > Hi Linus, please pull from: > > git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm > tags/libnvdimm-fixes-5.0-rc4 Hmm. One more pr-tracker-bot note: going through the pull requests from the last week, I notice that this one di

Re: general protection fault in rds_recv_rcvbuf_delta

2019-02-02 Thread syzbot
syzbot has found a reproducer for the following crash on: HEAD commit:cd984a5be215 Merge tag 'xtensa-20190201' of git://github.c.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1725e4ff40 kernel config: https://syzkaller.appspot.com/x/.config?x=2e0064

Re: [PATCH AUTOSEL 4.19 059/258] x86/resctrl: Fixup the user-visible strings

2019-02-02 Thread Sasha Levin
On Mon, Jan 28, 2019 at 11:07:34AM -0800, Reinette Chatre wrote: Hi Sasha, On 1/28/2019 7:56 AM, Sasha Levin wrote: From: Babu Moger [ Upstream commit 723f1a0dd8e26a7523ba068204bee11c95ded38d ] Fix the messages in rdt_last_cmd_printf() and rdt_last_cmd_puts() to make them more meaningful and

Re: [PATCH] net: dsa: Fix lockdep false positive splat

2019-02-02 Thread Florian Fainelli
Le 2/2/19 à 9:53 AM, Marc Zyngier a écrit : > Creating a macvtap on a DSA-backed interface results in the following > splat when lockdep is enabled: > > [ 19.638080] IPv6: ADDRCONF(NETDEV_CHANGE): lan0: link becomes ready > [ 23.041198] device lan0 entered promiscuous mode > [ 23.043445] dev

Re: [PATCH] Drivers: hv: vmbus: Add mutex lock to channel show functions

2019-02-02 Thread Kimberly Brown
On Fri, Feb 01, 2019 at 06:24:24PM +, Dexuan Cui wrote: > > From: Kimberly Brown > > Sent: Thursday, January 31, 2019 9:47 AM > > ... > > 2) Prevent a deadlock that can occur between the proposed mutex_lock() > > call in the vmbus_chan_attr_show() function and the sysfs/kernfs functions. > Hi

Re: [GIT PULL] libnvdimm fixes for v5.0-rc4

2019-02-02 Thread Dan Williams
On Sat, Feb 2, 2019 at 11:12 AM Linus Torvalds wrote: > > On Sat, Jan 26, 2019 at 3:31 PM Williams, Dan J > wrote: > > > > Hi Linus, please pull from: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm > > tags/libnvdimm-fixes-5.0-rc4 > > Hmm. One more pr-tracker-bot note: goi

Re: [PATCH] docs: kernel-doc: typo "documentaion"

2019-02-02 Thread Matthew Wilcox
On Fri, Feb 01, 2019 at 02:04:16PM -0800, frowand.l...@gmail.com wrote: >Include documentation for each *function* in *source*. > - If no *function* if specified, the documentaion for all functions > + If no *function* if specified, the documentation for all functions >and types in the *s

linux-next: Fixes tag needs some work in Linus' tree

2019-02-02 Thread Stephen Rothwell
[Just a reminder for the future.] Hi all, In commit 85bd6e61f34d ("blk-mq: fix a hung issue when fsync") Fixes tag Fixes: bd166ef1 (blk-mq-sched: add framework for MQ capable IO schedulers) has these problem(s): - SHA1 should be at least 12 digits long Can be fixed by setting core.

linux-next: Fixes tag needs some work in the origin tree

2019-02-02 Thread Stephen Rothwell
[Just a reminder for the future.] Hi all, In commit 2bb10639f12c ("RISC-V: fix bad use of of_node_put") Fixes tag Fixes: 94f9bf118f ("RISC-V: Fix of_node_* refcount") has these problem(s): - SHA1 should be at least 12 digits long Can be fixed by setting core.abbrev to 12 (or more)

[PATCH] staging: comedi: dt2811: fix integer overflow in multiply

2019-02-02 Thread Colin King
From: Colin Ian King Multiplying two unsigned ints leads to an unsigned int result. The intention is that the result is a unsigned long long, so to fix the overflow cast the div to an unsigned long long to ensure that the multiplication is on unsigned long longs to avoid overflow. Detected by Co

Re: [PATCH][next] media: staging: intel-ipu3: fix unsigned comparison with < 0

2019-02-02 Thread Colin Ian King
ping? On 22/12/2018 11:49, Colin King wrote: > From: Colin Ian King > > The comparison css->pipes[pipe].bindex < 0 is always false because > bindex is an unsigned int. Fix this by using a signed integer for > the comparison. > > Detected by CoverityScan, CID#1476023 ("Unsigned compared against

[PATCH] MMC: OMAP: fix the maximum timeout setting

2019-02-02 Thread Aaro Koskinen
When running OMAP1 kernel on QEMU, MMC access is annoyingly noisy: MMC: CTO of 0xff and 0xfe cannot be used! MMC: CTO of 0xff and 0xfe cannot be used! MMC: CTO of 0xff and 0xfe cannot be used! [ad inf.] Emulator warnings appear to be valid. The TI document SPRU680

linux-next: tracebacks in workqueue.c/__flush_work()

2019-02-02 Thread Guenter Roeck
Commit "workqueue: Try to catch flush_work() without INIT_WORK()" added a warning if flush_work() is called without worker function. This results in the following tracebacks, typically observed during system shutdown. [ cut here ] WARNING: CPU: 0 PID: 101 at kernel/workqu

Re: Bluetooth: hci0: last event is not cmd complete (0x0f) with LG TV

2019-02-02 Thread Paul Menzel
Dear Linux folks, On 01.02.19 22:34, Paul Menzel wrote: [attaching Linux messages, lspci and lsusb output] On 01.02.19 22:20, Paul Menzel wrote: When trying to pair a Dell Latitude E7250 running Debian Sid/unstable with Linux 4.20 and GNOME 3.30 with an LG TV, after starting the pairing pr

[PATCH] staging: most: cdev: add missing check for cdev_add failure

2019-02-02 Thread Colin King
From: Colin Ian King Currently the call to cdev_add is missing a check for failure. Fix this by checking for failure and exiting via a new error path that ensures the allocated comp_channel struct is kfree'd. Detected by CoverityScan, CID#1462359 ("Unchecked return value") Fixes: 9bc79bbcd0c5 (

[PATCH] staging: rtl8192u: fix a null pointer dereference on a null dev pointer

2019-02-02 Thread Colin King
From: Colin Ian King There is an earlier null check on pointer dev which implies it may be null, however the assignment of pointer pref and the call to free_ieee82011 on a null dev can cause null pointer dereference errors. Fix this by moving the assignment of priv and the the call to free_ieee8

Re: [PATCH] XArray tests: allocation has to be GFP_ATOMIC under rcu_read_lock

2019-02-02 Thread Matthew Wilcox
On Tue, Jan 29, 2019 at 07:08:42PM +0800, Li RongQing wrote: > - XA_BUG_ON(xa, xa_store_index(xa, 1, GFP_KERNEL) != NULL); > + XA_BUG_ON(xa, xa_store_index(xa, 1, GFP_ATOMIC) != NULL); Did you try running this change in userspace too? I don't think it'll work. I think the right change wo

[PATCH v2 4/9] mtd: rawnand: jz4780: Add support for the JZ4740

2019-02-02 Thread Paul Cercueil
Add support for probing the jz4780-nand driver on the JZ4740 SoC from Ingenic. Signed-off-by: Paul Cercueil --- Changes: v2: - Add support for the JZ4740 and not the JZ4725B: they behave the same, and JZ4740 is fully upstream while JZ4725B is not. The JZ4725B devicetree will then si

[PATCH v2 6/9] mtd: rawnand: jz4780: Add ooblayout for the Qi Ben Nanonote

2019-02-02 Thread Paul Cercueil
The Ben Nanonote from Qi Hardware expects a specific OOB layout on its NAND. If the "ingenic,oob-layout" device property is set to "qi,lb60", this specific OOB layout is used. Signed-off-by: Paul Cercueil --- Changes: v2: New patch drivers/mtd/nand/raw/ingenic/jz4780_nand.c | 37 +

[PATCH v2 1/9] mtd: rawnand: Move drivers for Ingenic SoCs to subfolder

2019-02-02 Thread Paul Cercueil
Before adding support for more SoCs and seeing the number of files for these drivers grow, we move them to their own subfolder to keep it tidy. Signed-off-by: Paul Cercueil --- Changes: v2: New patch drivers/mtd/nand/raw/Kconfig | 14 +- drivers/mtd/nand/raw/Ma

[PATCH v2 8/9] mtd: rawnand: jz4780-bch: Add support for the JZ4725B

2019-02-02 Thread Paul Cercueil
Add the backend code for the jz4780-bch driver to support the JZ4725B SoC from Ingenic. Signed-off-by: Paul Cercueil --- Changes: v2: No changes drivers/mtd/nand/raw/ingenic/Makefile | 2 +- drivers/mtd/nand/raw/ingenic/jz4725b_bch.c| 234 ++ .../mtd/nand/raw/ing

[PATCH v2 3/9] mtd: rawnand: jz4780: Use SPDX license notifiers

2019-02-02 Thread Paul Cercueil
Use SPDX license notifiers instead of GPLv2 license text in the headers. Signed-off-by: Paul Cercueil Reviewed-by: Boris Brezillon --- Changes: v2: No changes drivers/mtd/nand/raw/ingenic/jz4780_bch.c | 5 + drivers/mtd/nand/raw/ingenic/jz4780_bch.h | 5 + drivers/mtd/nand/raw/inge

[PATCH v2 5/9] mtd: rawnand: jz4780: Add ooblayout for the JZ4725B

2019-02-02 Thread Paul Cercueil
The boot ROM of the JZ4725B SoC expects a specific OOB layout on the NAND. Add an optional "ingenic,oob-layout" device property. When set to "ingenic,jz4725b", this specific OOB layout is used. Signed-off-by: Paul Cercueil --- Changes: v2: Instead of forcing the OOB layout, leave it to the boa

[PATCH v2 2/9] dt-bindings: mtd: ingenic: Add compatible strings for the JZ4740

2019-02-02 Thread Paul Cercueil
Add compatible strings to probe the jz4780-nand and jz4780-bch drivers from devicetree on the JZ4725B and JZ4740 SoCs from Ingenic. Signed-off-by: Paul Cercueil --- Changes: v2: - Change 'ingenic,jz4725b-nand' compatible string to 'ingenic,jz4740-nand' to reflect driver change - Add '

[PATCH v2 0/9] Ingenic JZ4780 NAND patchset v2

2019-02-02 Thread Paul Cercueil
Hi, As requested by Boris, I added a patch to move all the Ingenic NAND drivers to their own directory. In this V2 I added support for the JZ4740 SoC. The combo of the jz4780-nemc, jz4780-nand and jz4740-bch now obsolete the old and dusty jz4740-nand driver. To support the only upstream JZ4740-b

[PATCH v2 9/9] mtd: rawnand: jz4780-bch: Add support for the JZ4740

2019-02-02 Thread Paul Cercueil
Add the backend code for the jz4780-bch driver to support the JZ4740 SoC from Ingenic. Signed-off-by: Paul Cercueil --- Changes: v2: New patch drivers/mtd/nand/raw/ingenic/Makefile | 2 +- drivers/mtd/nand/raw/ingenic/jz4740_bch.c | 173 ++ .../mtd/nand/raw/ingen

[PATCH v2 7/9] mtd: rawnand: jz4780-bch: Separate top-level and SoC specific code

2019-02-02 Thread Paul Cercueil
The jz4780-nand driver uses an API provided by the jz4780-bch driver. This makes it difficult to support other SoCs in the jz4780-bch driver. To work around this, we separate the API functions from the SoC-specific code, so that these API functions are SoC-agnostic. Signed-off-by: Paul Cercueil -

[PATCH-next] drm/sun4i: Use PTR_ERR_OR_ZERO in sun8i_phy_clk_create()

2019-02-02 Thread Christopher Diaz Riveros
Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR Signed-off-by: Christopher Diaz Riveros --- drivers/gpu/drm/sun4i/sun8i_hdmi_phy_clk.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/gpu/drm/sun4i/sun8i_hdmi_phy_clk.c b/drivers/gpu/drm/sun4i/sun8i_hdmi_p

Re: [PATCH v2 1/2] rtc: add AB-RTCMC-32.768kHz-EOZ9 RTC support

2019-02-02 Thread Artem Panfilov
Hi Alexandre, On 31.01.2019 0:48, Alexandre Belloni wrote: >> +#endif /* CONFIG_RTC_DRV_ABEOZ9_HWMON */ > This comment is not correct Thank you for your remarks. Can I add HMON support as Kconfig build option? Regards, Artem

[PATCH] Bluetooth: Fix decrementing reference count twice in releasing socket

2019-02-02 Thread Myungho Jung
When releasing socket, it is possible to enter hci_sock_release() and hci_sock_dev_event(HCI_DEV_UNREG) at the same time in different thread. The reference count of hdev should be decremented only once from one of them but if storing hdev to local variable in hci_sock_release() before detached from

Re: [PATCH 1/2] linux/kernel.h: use 'short' to define USHRT_MAX, SHRT_MAX, SHRT_MIN

2019-02-02 Thread Masahiro Yamada
On Sun, Feb 3, 2019 at 1:33 AM Alexey Dobriyan wrote: > > On Sun, Feb 03, 2019 at 01:06:24AM +0900, Masahiro Yamada wrote: > > The log of commit 44f564a4bf6a ("ipc: add definitions of USHORT_MAX > > and others") did not explain why it used (s16) and (u16) instead of > > (short) and (unsigned short

[PATCH v2 1/2] linux/kernel.h: use 'short' to define USHRT_MAX, SHRT_MAX, SHRT_MIN

2019-02-02 Thread Masahiro Yamada
The commit log of 44f564a4bf6a ("ipc: add definitions of USHORT_MAX and others") did not explain why it used (s16) and (u16) instead of (short) and (unsigned short). Let's use (short) and (unsigned short), which is more sensible, and more consistent with the other MAX/MIN defines. As you see in i

[PATCH v2 2/2] linux/kernel.h: split *_MAX and *_MIN macros into

2019-02-02 Thread Masahiro Yamada
tends to be cluttered because we often put various sort of unrelated stuff in it. So, we have split out a sensible chunk of code into a separate header from time to time. This commit splits out the *_MAX and *_MIN defines. The standard header contains various MAX, MIN constants including numeri

Re: linux-next: tracebacks in workqueue.c/__flush_work()

2019-02-02 Thread Tetsuo Handa
(Adding Chris Metcalf and Rusty Russell.) If NR_CPUS == 1 due to CONFIG_SMP=n, for_each_cpu(cpu, &has_work) loop does not evaluate "struct cpumask has_work" modified by cpumask_set_cpu(cpu, &has_work) at previous for_each_online_cpu() loop. Guenter Roeck found a problem among three commits listed

<    1   2   3   >