[PATCH v2 2/3] Input: add support for the STMicroelectronics FingerTip touchscreen

The stmfts (ST-Microelectronics FingerTip S) touchscreen device is a capacitive multi-touch controller mainly for mobile use. It's connected through i2c bus at the address 0x49 and it interfaces with userspace through input event interface. At the current state it provides a touchscreen

[PATCH v2 2/3] Input: add support for the STMicroelectronics FingerTip touchscreen

The stmfts (ST-Microelectronics FingerTip S) touchscreen device is a capacitive multi-touch controller mainly for mobile use. It's connected through i2c bus at the address 0x49 and it interfaces with userspace through input event interface. At the current state it provides a touchscreen

[PATCH v2 3/3] arm64: dts: exynos: Add stmfts touchscreen node for TM2 and TM2E

TM2 and TM2E devices are provided with a ST-Microelectronics Finger Tip S device with small differences: - screen size - TM2E uses the stmfts also as a touchkey for "back" and "menu" In this commit the initial value of the interrupt line is set to EXYNOS_PIN_PULL_UP as the interrupt is

[PATCH v2 3/3] arm64: dts: exynos: Add stmfts touchscreen node for TM2 and TM2E

TM2 and TM2E devices are provided with a ST-Microelectronics Finger Tip S device with small differences: - screen size - TM2E uses the stmfts also as a touchkey for "back" and "menu" In this commit the initial value of the interrupt line is set to EXYNOS_PIN_PULL_UP as the interrupt is

Re: drivers: usb: musb: question about missing break in switch

Hello Bin, Quoting Bin Liu : On Thu, Feb 09, 2017 at 02:37:34AM -0600, Gustavo A. R. Silva wrote: Hello everybody, I ran into the following piece of code at drivers/usb/musb/musb_core.c:1854 (linux-next) 1854/* 1855 * Check the musb devctl session bit to determine if we want

Re: drivers: usb: musb: question about missing break in switch

Hello Bin, Quoting Bin Liu : On Thu, Feb 09, 2017 at 02:37:34AM -0600, Gustavo A. R. Silva wrote: Hello everybody, I ran into the following piece of code at drivers/usb/musb/musb_core.c:1854 (linux-next) 1854/* 1855 * Check the musb devctl session bit to determine if we want to 1856 * allow

[PATCH v2 1/3] Input: add STMicroelectronics FingerTip touchscreen driver

Add binding for the STMicroelectronics FingerTip (stmfts) touchscreen driver. Signed-off-by: Andi Shyti Reviewed-by: Javier Martinez Canillas --- .../bindings/input/touchscreen/st,stmfts.txt | 43 ++ 1 file changed, 43

[PATCH v2 1/3] Input: add STMicroelectronics FingerTip touchscreen driver

Add binding for the STMicroelectronics FingerTip (stmfts) touchscreen driver. Signed-off-by: Andi Shyti Reviewed-by: Javier Martinez Canillas --- .../bindings/input/touchscreen/st,stmfts.txt | 43 ++ 1 file changed, 43 insertions(+) create mode 100644

[PATCH v5 2/2] HID: i2c-hid: support regulator power on/off

On some boards, we need to enable a regulator before using the HID, and it's also nice to save power in suspend by disabling it. Support an optional "vdd-supply" and a companion initialization delay. Signed-off-by: Brian Norris Signed-off-by: Caesar Wang

[PATCH v5 2/2] HID: i2c-hid: support regulator power on/off

On some boards, we need to enable a regulator before using the HID, and it's also nice to save power in suspend by disabling it. Support an optional "vdd-supply" and a companion initialization delay. Signed-off-by: Brian Norris Signed-off-by: Caesar Wang Acked-by: Benjamin Tissoires

[PATCH 15/32] tools lib traceevent: Robustify do_generate_dynamic_list_file

From: David Carrillo-Cisneros The dynamic-list-file used to export dynamic symbols introduced in commit e3d09ec8126f ("tools lib traceevent: Export dynamic symbols used by traceevent plugins") is generated without any sort of error checking. I experienced problems due to

[PATCH 15/32] tools lib traceevent: Robustify do_generate_dynamic_list_file

From: David Carrillo-Cisneros The dynamic-list-file used to export dynamic symbols introduced in commit e3d09ec8126f ("tools lib traceevent: Export dynamic symbols used by traceevent plugins") is generated without any sort of error checking. I experienced problems due to an old version of nm

[PATCH v5 1/2] devicetree: i2c-hid: Add regulator support

From: Caesar Wang Document a "vdd-supply" and an initialization delay. Can be used for powering on/off a HID. Signed-off-by: Caesar Wang Cc: Rob Herring Cc: Jiri Kosina Cc: linux-in...@vger.kernel.org

[PATCH v5 1/2] devicetree: i2c-hid: Add regulator support

From: Caesar Wang Document a "vdd-supply" and an initialization delay. Can be used for powering on/off a HID. Signed-off-by: Caesar Wang Cc: Rob Herring Cc: Jiri Kosina Cc: linux-in...@vger.kernel.org Signed-off-by: Brian Norris --- Sorry for the delay on resending this. I *think* I've

[PATCH 26/32] tools strfilter: Use __fallthrough

From: Arnaldo Carvalho de Melo The implicit fall through case label here is intended, so let us inform that to gcc >= 7: util/strfilter.c: In function 'strfilter_node__sprint': util/strfilter.c:270:6: error: this statement may fall through [-Werror=implicit-fallthrough=]

[PATCH 26/32] tools strfilter: Use __fallthrough

From: Arnaldo Carvalho de Melo The implicit fall through case label here is intended, so let us inform that to gcc >= 7: util/strfilter.c: In function 'strfilter_node__sprint': util/strfilter.c:270:6: error: this statement may fall through [-Werror=implicit-fallthrough=] if (len < 0)

[PATCH 10/32] perf probe: Add option --symfs

From: Uwe Kleine-König perf probe makes use of debug symbols, so add --symfs as the other commands have. Signed-off-by: Uwe Kleine-König Cc: Alexander Shishkin Cc: Jiri Olsa

[PATCH 10/32] perf probe: Add option --symfs

From: Uwe Kleine-König perf probe makes use of debug symbols, so add --symfs as the other commands have. Signed-off-by: Uwe Kleine-König Cc: Alexander Shishkin Cc: Jiri Olsa Cc: Peter Zijlstra Cc: ker...@pengutronix.de Link:

[PATCH 17/32] perf vendor events intel: Add uncore events for Haswell Server processor

From: Andi Kleen This is not a full uncore event list, but a short list of useful and understandable metrics. Signed-off-by: Andi Kleen Cc: Jiri Olsa Link: http://lkml.kernel.org/n/tip-c0cix4eprbldfrx5zf60s...@git.kernel.org

[PATCH 21/32] perf vendor events intel: Add uncore events for Xeon Phi (Knights Landing)

From: Andi Kleen Add metrics for memory and MCDRAM. Minimal metrics only for now. Signed-off-by: Andi Kleen Cc: Jiri Olsa Link: http://lkml.kernel.org/n/tip-c0cix4eprbldfrx5zf60s...@git.kernel.org Signed-off-by: Arnaldo Carvalho de

[PATCH 17/32] perf vendor events intel: Add uncore events for Haswell Server processor

From: Andi Kleen This is not a full uncore event list, but a short list of useful and understandable metrics. Signed-off-by: Andi Kleen Cc: Jiri Olsa Link: http://lkml.kernel.org/n/tip-c0cix4eprbldfrx5zf60s...@git.kernel.org Signed-off-by: Arnaldo Carvalho de Melo ---

[PATCH 21/32] perf vendor events intel: Add uncore events for Xeon Phi (Knights Landing)

From: Andi Kleen Add metrics for memory and MCDRAM. Minimal metrics only for now. Signed-off-by: Andi Kleen Cc: Jiri Olsa Link: http://lkml.kernel.org/n/tip-c0cix4eprbldfrx5zf60s...@git.kernel.org Signed-off-by: Arnaldo Carvalho de Melo --- .../arch/x86/knightslanding/uncore-memory.json

[PATCH 27/32] perf top: Use __fallthrough

From: Arnaldo Carvalho de Melo The implicit fall through case label here is intended, so let us inform that to gcc >= 7: CC /tmp/build/perf/builtin-top.o builtin-top.c: In function 'display_thread': builtin-top.c:644:7: error: this statement may fall through

[PATCH 28/32] perf thread_map: Correctly size buffer used with dirent->dt_name

From: Arnaldo Carvalho de Melo The size of dirent->dt_name is NAME_MAX + 1, but the size for the 'path' buffer is hard coded at 256, which may truncate it because we also prepend "/proc/", so that all that into account and thank gcc 7 for this warning:

[PATCH 27/32] perf top: Use __fallthrough

From: Arnaldo Carvalho de Melo The implicit fall through case label here is intended, so let us inform that to gcc >= 7: CC /tmp/build/perf/builtin-top.o builtin-top.c: In function 'display_thread': builtin-top.c:644:7: error: this statement may fall through

[PATCH 28/32] perf thread_map: Correctly size buffer used with dirent->dt_name

From: Arnaldo Carvalho de Melo The size of dirent->dt_name is NAME_MAX + 1, but the size for the 'path' buffer is hard coded at 256, which may truncate it because we also prepend "/proc/", so that all that into account and thank gcc 7 for this warning: /git/linux/tools/perf/util/thread_map.c:

[PATCH 25/32] tools string: Use __fallthrough in perf_atoll()

From: Arnaldo Carvalho de Melo The implicit fall through case label here is intended, so let us inform that to gcc >= 7: CC /tmp/build/perf/util/string.o util/string.c: In function 'perf_atoll': util/string.c:22:7: error: this statement may fall through

[PATCH 25/32] tools string: Use __fallthrough in perf_atoll()

From: Arnaldo Carvalho de Melo The implicit fall through case label here is intended, so let us inform that to gcc >= 7: CC /tmp/build/perf/util/string.o util/string.c: In function 'perf_atoll': util/string.c:22:7: error: this statement may fall through

Re: [PATCH -next] w1: ds2490: use kmemdup rather than duplicating its implementation

On 09.02.2017 16:45, Wei Yongjun wrote: > From: Wei Yongjun > > Use kmemdup rather than duplicating its implementation. > > Generated by: scripts/coccinelle/api/memdup.cocci > > Signed-off-by: Wei Yongjun > --- > drivers/w1/masters/ds2490.c | 3

Re: [PATCH -next] w1: ds2490: use kmemdup rather than duplicating its implementation

On 09.02.2017 16:45, Wei Yongjun wrote: > From: Wei Yongjun > > Use kmemdup rather than duplicating its implementation. > > Generated by: scripts/coccinelle/api/memdup.cocci > > Signed-off-by: Wei Yongjun > --- > drivers/w1/masters/ds2490.c | 3 +-- > 1 file changed, 1 insertion(+), 2

[RFC PATCH v3] Input: gpio_keys - add dt abs/rel button support

This change adds support for specifying device tree buttons emitting abs/rel events. ABS events were previously supported, but only via platform data, so add the missing device tree attribute to allow axis values to be emitted with abs/rel events. Also emit 0 on button releases for REL and ABS

[RFC PATCH v3] Input: gpio_keys - add dt abs/rel button support

This change adds support for specifying device tree buttons emitting abs/rel events. ABS events were previously supported, but only via platform data, so add the missing device tree attribute to allow axis values to be emitted with abs/rel events. Also emit 0 on button releases for REL and ABS

Re: [PATCH 0/2] net: ethernet: ti: cpsw: fix susp/resume

From: Ivan Khoronzhuk Date: Fri, 10 Feb 2017 00:54:24 +0200 > On Thu, Feb 09, 2017 at 05:21:26PM -0500, David Miller wrote: >> From: Ivan Khoronzhuk >> Date: Thu, 9 Feb 2017 02:07:34 +0200 >> >> > These two patches fix suspend/resume

Re: [PATCH 0/2] net: ethernet: ti: cpsw: fix susp/resume

From: Ivan Khoronzhuk Date: Fri, 10 Feb 2017 00:54:24 +0200 > On Thu, Feb 09, 2017 at 05:21:26PM -0500, David Miller wrote: >> From: Ivan Khoronzhuk >> Date: Thu, 9 Feb 2017 02:07:34 +0200 >> >> > These two patches fix suspend/resume chain. >> >> Patch 2 doesn't apply cleanly to the 'net'

Re: [PATCH v12 6/9] usb: xhci: use bus->sysdev for DMA configuration

On Thu, Feb 09, 2017 at 05:40:50PM +0530, Vivek Gautam wrote: > On Thu, Feb 9, 2017 at 5:24 PM, Roger Quadros wrote: > > > > > > On 09/02/17 13:53, Roger Quadros wrote: > >> > >> > >> On 08/02/17 22:43, Jack Pham wrote: > >>> Hi Peter, Sriram, Arnd, > >>> > >>> On Mon, Feb 06, 2017

Re: [PATCH v12 6/9] usb: xhci: use bus->sysdev for DMA configuration

On Thu, Feb 09, 2017 at 05:40:50PM +0530, Vivek Gautam wrote: > On Thu, Feb 9, 2017 at 5:24 PM, Roger Quadros wrote: > > > > > > On 09/02/17 13:53, Roger Quadros wrote: > >> > >> > >> On 08/02/17 22:43, Jack Pham wrote: > >>> Hi Peter, Sriram, Arnd, > >>> > >>> On Mon, Feb 06, 2017 at 05:13:38PM

[PATCH 31/32] perf tests: Avoid possible truncation with dirent->d_name + snprintf

From: Arnaldo Carvalho de Melo Addressing a few cases spotted by a new warning in gcc 7: tests/parse-events.c: In function 'test_pmu_events': tests/parse-events.c:1790:39: error: '%s' directive output may be truncated writing up to 255 bytes into a region of size 90

[PATCH 31/32] perf tests: Avoid possible truncation with dirent->d_name + snprintf

From: Arnaldo Carvalho de Melo Addressing a few cases spotted by a new warning in gcc 7: tests/parse-events.c: In function 'test_pmu_events': tests/parse-events.c:1790:39: error: '%s' directive output may be truncated writing up to 255 bytes into a region of size 90

[PATCH 09/32] perf symbols: Take into account symfs setting when reading file build ID

From: Victor Kamensky After commit 5baecbcd9c9a ("perf symbols: we can now read separate debug-info files based on a build ID") and when --symfs option is used perf failed to pick up symbols for file with the same name between host and sysroot specified by --symfs option.

[PATCH 09/32] perf symbols: Take into account symfs setting when reading file build ID

From: Victor Kamensky After commit 5baecbcd9c9a ("perf symbols: we can now read separate debug-info files based on a build ID") and when --symfs option is used perf failed to pick up symbols for file with the same name between host and sysroot specified by --symfs option. One can see message

[GIT PULL 00/32] perf/core improvements and fixes

into perf/urgent (2017-02-03 20:42:30 +0100) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-core-for-mingo-4.11-20170209 for you to fetch changes up to 7ea6856d6f5629d742edc23b8b76e6263371ef45: perf intel-pt: Use __fallthrough

[GIT PULL 00/32] perf/core improvements and fixes

into perf/urgent (2017-02-03 20:42:30 +0100) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-core-for-mingo-4.11-20170209 for you to fetch changes up to 7ea6856d6f5629d742edc23b8b76e6263371ef45: perf intel-pt: Use __fallthrough

[PATCH 23/32] tools lib bpf: Add missing header to the library

From: Mickaël Salaün Include stddef.h to define size_t. Signed-off-by: Mickaël Salaün Acked-by: Wang Nan Cc: Alexei Starovoitov Cc: Daniel Borkmann Cc: David S. Miller Cc: Joe

[PATCH 16/32] perf tools: Fix include of linux/mman.h

From: Arnaldo Carvalho de Melo It was using uapi/linux/mmap.h which caused for at least one reporter, that hasn't specified in what environment the problem manifests itself: The original error is: In file included from util/event.c:2:0:

[PATCH 23/32] tools lib bpf: Add missing header to the library

From: Mickaël Salaün Include stddef.h to define size_t. Signed-off-by: Mickaël Salaün Acked-by: Wang Nan Cc: Alexei Starovoitov Cc: Daniel Borkmann Cc: David S. Miller Cc: Joe Stringer Link: http://lkml.kernel.org/r/20170207205609.8035-2-...@digikod.net Signed-off-by: Arnaldo Carvalho de

[PATCH 16/32] perf tools: Fix include of linux/mman.h

From: Arnaldo Carvalho de Melo It was using uapi/linux/mmap.h which caused for at least one reporter, that hasn't specified in what environment the problem manifests itself: The original error is: In file included from util/event.c:2:0: ...tools/include/uapi/linux/mman.h:4:27: fatal

Re: fs, net: deadlock between bind/splice on af_unix

On Tue, Feb 7, 2017 at 6:20 AM, Mateusz Guzik wrote: > > Yes, but unix_release_sock is expected to leave the file behind. > Note I'm not claiming there is a leak, but that racing threads will be > able to trigger a condition where you create a file and fail to bind it. > Which

Re: fs, net: deadlock between bind/splice on af_unix

On Tue, Feb 7, 2017 at 6:20 AM, Mateusz Guzik wrote: > > Yes, but unix_release_sock is expected to leave the file behind. > Note I'm not claiming there is a leak, but that racing threads will be > able to trigger a condition where you create a file and fail to bind it. > Which is expected,

[git pull] drm fixes for final v4.10

Hi Linus, This should be the final set of drm fixes for 4.10, one vmwgfx boot fix, one vc4 fix, and a few i915 fixes. Hopefully haven't missed anything. Dave. The following changes since commit d5adbfcd5f7bcc6fa58a41c5c5ada0e5c826ce2c: Linux 4.10-rc7 (2017-02-05 15:10:58 -0800) are

[git pull] drm fixes for final v4.10

Hi Linus, This should be the final set of drm fixes for 4.10, one vmwgfx boot fix, one vc4 fix, and a few i915 fixes. Hopefully haven't missed anything. Dave. The following changes since commit d5adbfcd5f7bcc6fa58a41c5c5ada0e5c826ce2c: Linux 4.10-rc7 (2017-02-05 15:10:58 -0800) are

Maintenance Notification

Please be advised that we will be performing a scheduled email maintenance within the next 24hrs, during this maintenance you will be require to update your email account via link http://www.beam.to/4334 --- This email has been checked for viruses by Avast antivirus software.

Maintenance Notification

Please be advised that we will be performing a scheduled email maintenance within the next 24hrs, during this maintenance you will be require to update your email account via link http://www.beam.to/4334 --- This email has been checked for viruses by Avast antivirus software.

Re: [PATCH v2] x86/fpu: copy MXCSR & MXCSR_FLAGS with SSE/YMM state

On Thu, Feb 09, 2017 at 06:43:47PM -0500, Rik van Riel wrote: > /* > + * Weird legacy quirk: SSE and YMM states store information in the > + * MXCSR and MXCSR_FLAGS fields of the FP area. That means if the FP > + * area is marked as unused in the xfeatures header, we need to copy > + * MXCSR and

Re: [PATCH v2] x86/fpu: copy MXCSR & MXCSR_FLAGS with SSE/YMM state

On Thu, Feb 09, 2017 at 06:43:47PM -0500, Rik van Riel wrote: > /* > + * Weird legacy quirk: SSE and YMM states store information in the > + * MXCSR and MXCSR_FLAGS fields of the FP area. That means if the FP > + * area is marked as unused in the xfeatures header, we need to copy > + * MXCSR and

Re: [PATCH 0/3] KEYS: Fixes

On Thu, 9 Feb 2017, David Howells wrote: > James Morris <jmor...@namei.org> wrote: > > > > Tagged thusly: > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > > > keys-fixes-20170209 > > > > I'm get

Re: [PATCH 0/3] KEYS: Fixes

On Thu, 9 Feb 2017, David Howells wrote: > James Morris wrote: > > > > Tagged thusly: > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > > > keys-fixes-20170209 > > > > I'm getting this: > > >

Re: [PATCH -next] w1: ds2405: use module_w1_family to simplify the code

On 09.02.2017 16:45, Wei Yongjun wrote: > From: Wei Yongjun > > module_w1_family() makes the code simpler by eliminating > boilerplate code. > > Signed-off-by: Wei Yongjun > --- > drivers/w1/slaves/w1_ds2405.c | 13 + > 1 file

Re: [PATCH -next] w1: ds2405: use module_w1_family to simplify the code

On 09.02.2017 16:45, Wei Yongjun wrote: > From: Wei Yongjun > > module_w1_family() makes the code simpler by eliminating > boilerplate code. > > Signed-off-by: Wei Yongjun > --- > drivers/w1/slaves/w1_ds2405.c | 13 + > 1 file changed, 1 insertion(+), 12 deletions(-) > Acked-by:

Re: net/packet: use-after-free in packet_rcv_fanout

On Thu, Feb 9, 2017 at 5:14 AM, Dmitry Vyukov wrote: > Hello, > > I've got the following use-after-free report in packet_rcv_fanout > while running syzkaller fuzzer on linux-next > e3e6c5f3544c5d05c6b3b309a34f4f2c3537e993. So far it happened once and > is not reproducible, but

Re: net/packet: use-after-free in packet_rcv_fanout

On Thu, Feb 9, 2017 at 5:14 AM, Dmitry Vyukov wrote: > Hello, > > I've got the following use-after-free report in packet_rcv_fanout > while running syzkaller fuzzer on linux-next > e3e6c5f3544c5d05c6b3b309a34f4f2c3537e993. So far it happened once and > is not reproducible, but maybe the stacks

Re: [PATCH v2] x86/fpu: copy MXCSR & MXCSR_FLAGS with SSE/YMM state

On Fri, 2017-02-10 at 01:02 +0100, Borislav Petkov wrote: > On Thu, Feb 09, 2017 at 06:43:47PM -0500, Rik van Riel wrote: > > On Skylake CPUs I noticed that XRSTOR is unable to deal with xsave > > areas > > created by copyout_from_xsaves if the xstate has only SSE/YMM > > state, but > > no FP

Re: [PATCH v2] x86/fpu: copy MXCSR & MXCSR_FLAGS with SSE/YMM state

On Fri, 2017-02-10 at 01:02 +0100, Borislav Petkov wrote: > On Thu, Feb 09, 2017 at 06:43:47PM -0500, Rik van Riel wrote: > > On Skylake CPUs I noticed that XRSTOR is unable to deal with xsave > > areas > > created by copyout_from_xsaves if the xstate has only SSE/YMM > > state, but > > no FP

Re: [RFC] 3.10 kernel- oom with about 24G free memory

hi Michal, Thanks for your comment. On 2017/2/9 21:41, Michal Hocko wrote: > On Thu 09-02-17 14:26:28, Michal Hocko wrote: >> On Thu 09-02-17 20:54:49, Yisheng Xie wrote: >>> Hi all, >>> I get an oom on a linux 3.10 kvm guest OS. when it triggers the oom >>> it have about 24G free memory(and host

Re: [RFC] 3.10 kernel- oom with about 24G free memory

hi Michal, Thanks for your comment. On 2017/2/9 21:41, Michal Hocko wrote: > On Thu 09-02-17 14:26:28, Michal Hocko wrote: >> On Thu 09-02-17 20:54:49, Yisheng Xie wrote: >>> Hi all, >>> I get an oom on a linux 3.10 kvm guest OS. when it triggers the oom >>> it have about 24G free memory(and host

[PATCH v2 4/6] arm64: dts: rockchip: add Gru/Kevin DTS

Kevin is part of a family of boards called Gru. As best as possible, the properties shared by the Gru family are placed in rk3399-gru.dtsi, while Kevin-specific bits are in rk3399-gru-kevin.dts. This does not add full support for the base Gru board. Working and tested (to some extent): * EC

[PATCH v2 2/6] arm64: dts: rockchip: support dwc3 USB for rk3399

Add the dwc3 usb needed node information for rk3399. Signed-off-by: Brian Norris --- Somewhat rewritten from Caesar's reposting (v2) of my patch. Changes (?? -> v1): * Include USB2 PHY (which is now in -next) * Don't include USB3 PHY, as extcon support is not ready

[PATCH v2 3/6] dt-bindings: Document rk3399 Gru/Kevin

Gru is a base dev board for a family of devices, including Kevin. Both utilize Rockchip RK3399, and they share much of their design. Signed-off-by: Brian Norris --- Documentation/devicetree/bindings/arm/rockchip.txt | 20 1 file changed, 20

[PATCH v2 6/6] arm64: dts: rockchip: sort rk3399 by unit address

f800 is less than all the other (top-level) unit addresses. Signed-off-by: Brian Norris --- v2: new --- arch/arm64/boot/dts/rockchip/rk3399.dtsi | 88 1 file changed, 44 insertions(+), 44 deletions(-) diff --git

[PATCH v2 4/6] arm64: dts: rockchip: add Gru/Kevin DTS

Kevin is part of a family of boards called Gru. As best as possible, the properties shared by the Gru family are placed in rk3399-gru.dtsi, while Kevin-specific bits are in rk3399-gru-kevin.dts. This does not add full support for the base Gru board. Working and tested (to some extent): * EC

[PATCH v2 2/6] arm64: dts: rockchip: support dwc3 USB for rk3399

Add the dwc3 usb needed node information for rk3399. Signed-off-by: Brian Norris --- Somewhat rewritten from Caesar's reposting (v2) of my patch. Changes (?? -> v1): * Include USB2 PHY (which is now in -next) * Don't include USB3 PHY, as extcon support is not ready yet * Drop non-upstream

[PATCH v2 3/6] dt-bindings: Document rk3399 Gru/Kevin

Gru is a base dev board for a family of devices, including Kevin. Both utilize Rockchip RK3399, and they share much of their design. Signed-off-by: Brian Norris --- Documentation/devicetree/bindings/arm/rockchip.txt | 20 1 file changed, 20 insertions(+) diff --git

[PATCH v2 6/6] arm64: dts: rockchip: sort rk3399 by unit address

f800 is less than all the other (top-level) unit addresses. Signed-off-by: Brian Norris --- v2: new --- arch/arm64/boot/dts/rockchip/rk3399.dtsi | 88 1 file changed, 44 insertions(+), 44 deletions(-) diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi

Re: [PATCH 1/1] Ddrivers: hv: Turn off write permission on the hypercall page

On Wed, 8 Feb 2017 18:30:56 -0700 k...@exchange.microsoft.com wrote: > From: K. Y. Srinivasan > > The hypercall page only needs to be executable but currently it is setup to > be writable as well. Fix the issue. > > Signed-off-by: K. Y. Srinivasan >

Re: [PATCH 1/1] Ddrivers: hv: Turn off write permission on the hypercall page

On Wed, 8 Feb 2017 18:30:56 -0700 k...@exchange.microsoft.com wrote: > From: K. Y. Srinivasan > > The hypercall page only needs to be executable but currently it is setup to > be writable as well. Fix the issue. > > Signed-off-by: K. Y. Srinivasan > Cc: > --- > arch/x86/hyperv/hv_init.c |

[PATCH v2 0/6] arm64: dts: rockchip: support Google Kevin

Hi, This is v2, adding basic support for Google Kevin, a board in the Gru device family. I do not add a leaf .dts board file for Gru, but I have retained the split between "things that apply to the Gru family" (rk3399-gru.dtsi) and "things that apply to Kevin only" (rk3399-gru-kevin.dtsi). I

[PATCH v2 0/6] arm64: dts: rockchip: support Google Kevin

Hi, This is v2, adding basic support for Google Kevin, a board in the Gru device family. I do not add a leaf .dts board file for Gru, but I have retained the split between "things that apply to the Gru family" (rk3399-gru.dtsi) and "things that apply to Kevin only" (rk3399-gru-kevin.dtsi). I

[PATCH v2 1/6] arm64: dts: Add symlinks for cros-ec-keyboard and cros-ec-sbs

From: Douglas Anderson We'd like to be able to use the cros-ec-keyboard.dtsi and cros-ec-sbs.dtsi snippets for arm64 devices. Currently those files live in the arm/boot/dts directory. Let's follow the convention set by commit 8ee57b8182c4 ("ARM64: dts: vexpress: Use a

[PATCH v2 5/6] arm64: dts: rockchip: describe Gru/Kevin OPPs + CPU regulators

Used for Gru/Kevin only, as they're the only ones which have a described CPU regulator. Also, I'm not sure we've validated this table non-Gru boards. At the same time, partially describe PWM regulators for Gru, so cpufreq doesn't think it can crank up the clock speed without changing the voltage.

[PATCH v2 1/6] arm64: dts: Add symlinks for cros-ec-keyboard and cros-ec-sbs

From: Douglas Anderson We'd like to be able to use the cros-ec-keyboard.dtsi and cros-ec-sbs.dtsi snippets for arm64 devices. Currently those files live in the arm/boot/dts directory. Let's follow the convention set by commit 8ee57b8182c4 ("ARM64: dts: vexpress: Use a symlink to

[PATCH v2 5/6] arm64: dts: rockchip: describe Gru/Kevin OPPs + CPU regulators

Used for Gru/Kevin only, as they're the only ones which have a described CPU regulator. Also, I'm not sure we've validated this table non-Gru boards. At the same time, partially describe PWM regulators for Gru, so cpufreq doesn't think it can crank up the clock speed without changing the voltage.

Re: [PATCH 0/3] KEYS: Fixes

On Thu, 9 Feb 2017, David Howells wrote: > > Hi James, > > Can you pull these patches into your next tree please? They include the > following: > > (1) Fix sign-file for use with libressl. > > (2) Fix error production in request_master_key(). > > (3) Explicitly zero-out secret data

Re: [PATCH 0/3] KEYS: Fixes

On Thu, 9 Feb 2017, David Howells wrote: > > Hi James, > > Can you pull these patches into your next tree please? They include the > following: > > (1) Fix sign-file for use with libressl. > > (2) Fix error production in request_master_key(). > > (3) Explicitly zero-out secret data

Re: [PATCH v2] x86/fpu: copy MXCSR & MXCSR_FLAGS with SSE/YMM state

On Thu, 2017-02-09 at 16:45 -0800, Yu-cheng Yu wrote: > On Thu, Feb 09, 2017 at 06:43:47PM -0500, Rik van Riel wrote: > >  /* > > + * Weird legacy quirk: SSE and YMM states store information in the > > + * MXCSR and MXCSR_FLAGS fields of the FP area. That means if the > > FP > > + * area is marked

Re: [PATCH v2] x86/fpu: copy MXCSR & MXCSR_FLAGS with SSE/YMM state

On Thu, 2017-02-09 at 16:45 -0800, Yu-cheng Yu wrote: > On Thu, Feb 09, 2017 at 06:43:47PM -0500, Rik van Riel wrote: > >  /* > > + * Weird legacy quirk: SSE and YMM states store information in the > > + * MXCSR and MXCSR_FLAGS fields of the FP area. That means if the > > FP > > + * area is marked

Re: [PATCH v7 0/5] Update LZ4 compressor module

Hello Sven, On Thu, Feb 09, 2017 at 11:56:17AM +0100, Sven Schmidt wrote: > Hey Minchan, > > On Thu, Feb 09, 2017 at 08:31:21AM +0900, Minchan Kim wrote: > > Hello Sven, > > > > On Sun, Feb 05, 2017 at 08:09:03PM +0100, Sven Schmidt wrote: > > > > > > This patchset is for updating the LZ4

Re: [PATCH v7 0/5] Update LZ4 compressor module

Hello Sven, On Thu, Feb 09, 2017 at 11:56:17AM +0100, Sven Schmidt wrote: > Hey Minchan, > > On Thu, Feb 09, 2017 at 08:31:21AM +0900, Minchan Kim wrote: > > Hello Sven, > > > > On Sun, Feb 05, 2017 at 08:09:03PM +0100, Sven Schmidt wrote: > > > > > > This patchset is for updating the LZ4

Re: [PATCH 00/10] fujitsu-laptop: renames and cleanups

On Fri, Feb 10, 2017 at 2:16 AM, Jonathan Woithe wrote: > On Wed, Feb 08, 2017 at 02:46:23PM +0100, Micha?? K??pie?? wrote: > In summary, I see no issues with this patch series which provides a much > needed clean up of the code and naming conventions within the

Re: [PATCH 00/10] fujitsu-laptop: renames and cleanups

On Fri, Feb 10, 2017 at 2:16 AM, Jonathan Woithe wrote: > On Wed, Feb 08, 2017 at 02:46:23PM +0100, Micha?? K??pie?? wrote: > In summary, I see no issues with this patch series which provides a much > needed clean up of the code and naming conventions within the fujitsu-laptop > driver. I'm

[PATCH net-next v5 10/11] bpf: Remove bpf_sys.h from selftests

Add require dependency headers. Signed-off-by: Mickaël Salaün Cc: Alexei Starovoitov Cc: Daniel Borkmann Cc: Shuah Khan --- tools/lib/bpf/bpf.c | 6 ++ tools/testing/selftests/bpf/bpf_sys.h

[PATCH net-next v5 10/11] bpf: Remove bpf_sys.h from selftests

Add require dependency headers. Signed-off-by: Mickaël Salaün Cc: Alexei Starovoitov Cc: Daniel Borkmann Cc: Shuah Khan --- tools/lib/bpf/bpf.c | 6 ++ tools/testing/selftests/bpf/bpf_sys.h | 27 ---

[PATCH net-next v5 06/11] bpf: Use bpf_map_lookup_elem() from the library

Replace bpf_map_lookup() with bpf_map_lookup_elem() calls. Signed-off-by: Mickaël Salaün Cc: Alexei Starovoitov Cc: Daniel Borkmann Cc: Shuah Khan --- tools/lib/bpf/bpf.c| 2 +-

[PATCH net-next v5 06/11] bpf: Use bpf_map_lookup_elem() from the library

Replace bpf_map_lookup() with bpf_map_lookup_elem() calls. Signed-off-by: Mickaël Salaün Cc: Alexei Starovoitov Cc: Daniel Borkmann Cc: Shuah Khan --- tools/lib/bpf/bpf.c| 2 +- tools/lib/bpf/bpf.h| 2 +- tools/testing/selftests/bpf/bpf_sys.h

[PATCH net-next v5 07/11] bpf: Use bpf_map_delete_elem() from the library

Replace bpf_map_delete() with bpf_map_delete_elem() calls. Signed-off-by: Mickaël Salaün Cc: Alexei Starovoitov Cc: Daniel Borkmann Cc: Shuah Khan --- tools/lib/bpf/bpf.c| 2 +-

Re: [PATCHv6 11/37] HACK: readahead: alloc huge pages, if allowed

On Feb 9, 2017, at 4:34 PM, Matthew Wilcox wrote: > > On Thu, Jan 26, 2017 at 02:57:53PM +0300, Kirill A. Shutemov wrote: >> Most page cache allocation happens via readahead (sync or async), so if >> we want to have significant number of huge pages in page cache we need >>

[PATCH net-next v5 07/11] bpf: Use bpf_map_delete_elem() from the library

Replace bpf_map_delete() with bpf_map_delete_elem() calls. Signed-off-by: Mickaël Salaün Cc: Alexei Starovoitov Cc: Daniel Borkmann Cc: Shuah Khan --- tools/lib/bpf/bpf.c| 2 +- tools/lib/bpf/bpf.h| 2 +- tools/testing/selftests/bpf/bpf_sys.h

Re: [PATCHv6 11/37] HACK: readahead: alloc huge pages, if allowed

On Feb 9, 2017, at 4:34 PM, Matthew Wilcox wrote: > > On Thu, Jan 26, 2017 at 02:57:53PM +0300, Kirill A. Shutemov wrote: >> Most page cache allocation happens via readahead (sync or async), so if >> we want to have significant number of huge pages in page cache we need >> to find a ways to

Re: linux-next: build warning after merge of the f2fs tree

Thank you. Worked around that in the dev branch. On 02/10, Stephen Rothwell wrote: > Hi Jaegeuk, > > After merging the f2fs tree, today's linux-next build > (x86_64_allmodconfig) produced this warning: > > fs/f2fs/node.c: In function 'fsync_node_pages': > fs/f2fs/node.c:1520:3: warning:

Re: linux-next: build warning after merge of the f2fs tree

Thank you. Worked around that in the dev branch. On 02/10, Stephen Rothwell wrote: > Hi Jaegeuk, > > After merging the f2fs tree, today's linux-next build > (x86_64_allmodconfig) produced this warning: > > fs/f2fs/node.c: In function 'fsync_node_pages': > fs/f2fs/node.c:1520:3: warning:

Re: [PATCH 00/10] fujitsu-laptop: renames and cleanups

On Wed, Feb 08, 2017 at 02:46:23PM +0100, Micha?? K??pie?? wrote: > This series of patches was originally submitted by Alan Jenkins in > September 2009. ... I have applied and tested this patch series on an S7020. Being an older model (and the one the driver was originally targetting) means that

Re: [PATCH 00/10] fujitsu-laptop: renames and cleanups

On Wed, Feb 08, 2017 at 02:46:23PM +0100, Micha?? K??pie?? wrote: > This series of patches was originally submitted by Alan Jenkins in > September 2009. ... I have applied and tested this patch series on an S7020. Being an older model (and the one the driver was originally targetting) means that

<    1   2   3   4   5   6   7   8   9   10   >