[PATCH v2,5/5] arm64: dts: mediatek: add USB3 DRD driver

USB3 DRD driver is added for MT8173-EVB, and xHCI driver becomes its subnode Signed-off-by: Chunfeng Yun --- arch/arm64/boot/dts/mediatek/mt8173-evb.dts | 46 +-- arch/arm64/boot/dts/mediatek/mt8173.dtsi| 28 2 files

[PATCH v2,5/5] arm64: dts: mediatek: add USB3 DRD driver

USB3 DRD driver is added for MT8173-EVB, and xHCI driver becomes its subnode Signed-off-by: Chunfeng Yun --- arch/arm64/boot/dts/mediatek/mt8173-evb.dts | 46 +-- arch/arm64/boot/dts/mediatek/mt8173.dtsi| 28 2 files changed, 65 insertions(+), 9

Re: [PATCH perf/core v9 01/16] perf-symbol: Introduce filename__readable to check readability

On Mon, 30 May 2016 13:04:47 -0300 Arnaldo Carvalho de Melo wrote: > Em Mon, May 30, 2016 at 01:03:17PM -0300, Arnaldo Carvalho de Melo escreveu: > > Em Sun, May 29, 2016 at 12:15:13AM +0900, Masami Hiramatsu escreveu: > > > Introduce filename__readable to check readability by

[PATCH v2,2/5] usb: xhci-mtk: make IPPC register optional

Make IPPC register optional to support host side of dual-role mode, due to it is moved into common glue layer for simplification. Signed-off-by: Chunfeng Yun --- drivers/usb/host/xhci-mtk.c | 32 +++- 1 file changed, 27 insertions(+), 5

Re: [PATCH perf/core v9 01/16] perf-symbol: Introduce filename__readable to check readability

On Mon, 30 May 2016 13:04:47 -0300 Arnaldo Carvalho de Melo wrote: > Em Mon, May 30, 2016 at 01:03:17PM -0300, Arnaldo Carvalho de Melo escreveu: > > Em Sun, May 29, 2016 at 12:15:13AM +0900, Masami Hiramatsu escreveu: > > > Introduce filename__readable to check readability by opening > > > the

[PATCH v2,2/5] usb: xhci-mtk: make IPPC register optional

Make IPPC register optional to support host side of dual-role mode, due to it is moved into common glue layer for simplification. Signed-off-by: Chunfeng Yun --- drivers/usb/host/xhci-mtk.c | 32 +++- 1 file changed, 27 insertions(+), 5 deletions(-) diff --git

[PATCH v2,4/5] usb: Add MediaTek USB3 DRD Driver

This patch adds support for the MediaTek USB3 controller integrated into MT8173. It can be configured as Dual-Role Device (DRD), Peripheral Only and Host Only (xHCI) modes. Signed-off-by: Chunfeng Yun --- drivers/usb/Kconfig|2 +

[PATCH v2,4/5] usb: Add MediaTek USB3 DRD Driver

This patch adds support for the MediaTek USB3 controller integrated into MT8173. It can be configured as Dual-Role Device (DRD), Peripheral Only and Host Only (xHCI) modes. Signed-off-by: Chunfeng Yun --- drivers/usb/Kconfig|2 + drivers/usb/Makefile |1 +

[PATCH v2,1/5] dt-bindings: mt8173-xhci: support host side of dual-role mode

Some resources, such as IPPC register etc, shared with device driver are moved into common glue layer when xHCI driver is the host side of dual-role mode and they should be changed as optional properties if they are required ones before. For clarity, add a new part of binding to support host side

[PATCH v2,1/5] dt-bindings: mt8173-xhci: support host side of dual-role mode

Some resources, such as IPPC register etc, shared with device driver are moved into common glue layer when xHCI driver is the host side of dual-role mode and they should be changed as optional properties if they are required ones before. For clarity, add a new part of binding to support host side

Add MediaTek USB3 DRD Driver

>From f2b6744b1ed13636db8690dd3e8d65ad7f3fb7ce Mon Sep 17 00:00:00 2001 From: Chunfeng Yun Date: Tue, 31 May 2016 10:52:46 +0800 Subject: [PATCH 0/5] Add MediaTek USB3 DRD Driver These patches introduce the MediaTek USB3 dual-role controller driver. The driver can be

Add MediaTek USB3 DRD Driver

>From f2b6744b1ed13636db8690dd3e8d65ad7f3fb7ce Mon Sep 17 00:00:00 2001 From: Chunfeng Yun Date: Tue, 31 May 2016 10:52:46 +0800 Subject: [PATCH 0/5] Add MediaTek USB3 DRD Driver These patches introduce the MediaTek USB3 dual-role controller driver. The driver can be configured as Dual-Role

[PATCH v2,3/5] dt-bindings: mtu3: add devicetree bindings

add a DT binding doc for MediaTek USB3 DRD driver Signed-off-by: Chunfeng Yun --- Documentation/devicetree/bindings/usb/mtu3.txt | 85 1 file changed, 85 insertions(+) create mode 100644 Documentation/devicetree/bindings/usb/mtu3.txt diff

[PATCH v2,3/5] dt-bindings: mtu3: add devicetree bindings

add a DT binding doc for MediaTek USB3 DRD driver Signed-off-by: Chunfeng Yun --- Documentation/devicetree/bindings/usb/mtu3.txt | 85 1 file changed, 85 insertions(+) create mode 100644 Documentation/devicetree/bindings/usb/mtu3.txt diff --git

Re: [PATCH] mtd: Replace if and BUG with BUG_ON

On Mon, 30 May 2016, Ezequiel Garcia wrote: > Hi Amitoj, > > Thanks for your patch. > > On 28 May 2016 at 13:41, Amitoj Kaur Chawla wrote: > > Replace if condition and BUG() with a BUG_ON having the conditional > > expression of the if statement as argument. > > > > We

Re: [PATCH] mtd: Replace if and BUG with BUG_ON

On Mon, 30 May 2016, Ezequiel Garcia wrote: > Hi Amitoj, > > Thanks for your patch. > > On 28 May 2016 at 13:41, Amitoj Kaur Chawla wrote: > > Replace if condition and BUG() with a BUG_ON having the conditional > > expression of the if statement as argument. > > > > We usually want commit

RE: [PATCH v4] Axi-usb: Add support for 64-bit addressing.

Hi Shubhrajyoti, Thanks for the review... > > /** > > + * xudc_write64 - write 64bit value to device registers > > + * @ep: pointer to the usb device endpoint structure. > > + * @offset: register offset > > + * @val: data to be written > > + **/ > > +static void

RE: [PATCH v4] Axi-usb: Add support for 64-bit addressing.

Hi Shubhrajyoti, Thanks for the review... > > /** > > + * xudc_write64 - write 64bit value to device registers > > + * @ep: pointer to the usb device endpoint structure. > > + * @offset: register offset > > + * @val: data to be written > > + **/ > > +static void

Re: [PATCH v2 1/3] cpufreq: add resolve_freq driver callback

On 30-05-16, 08:31, Steve Muckle wrote: > My goal here was to have the system operate in this case in a manner > that is obviously not optimized (running at fmax), so the platform owner > realizes that the cpufreq driver doesn't fully support the schedutil > governor. > > I was originally going

Re: [PATCH v2 1/3] cpufreq: add resolve_freq driver callback

On 30-05-16, 08:31, Steve Muckle wrote: > My goal here was to have the system operate in this case in a manner > that is obviously not optimized (running at fmax), so the platform owner > realizes that the cpufreq driver doesn't fully support the schedutil > governor. > > I was originally going

Re: [PATCHv3 04/48] thermal: core: use dev.groups to manage always present tz attributes

On Tuesday 31 May 2016 03:45 AM, Eduardo Valentin wrote: Thermal zones attributes are all being created using device_create_file(). This has the disadvantage of making the code complicated and sometimes we may miss the cleanup of them. This patch starts to move the thermal zone sysfs

Re: [PATCHv3 04/48] thermal: core: use dev.groups to manage always present tz attributes

On Tuesday 31 May 2016 03:45 AM, Eduardo Valentin wrote: Thermal zones attributes are all being created using device_create_file(). This has the disadvantage of making the code complicated and sometimes we may miss the cleanup of them. This patch starts to move the thermal zone sysfs

[RFC 1/4] Documentation: hid: Intel ISH HID document

Document explaining ISH HID operation and implementation. Signed-off-by: Srinivas Pandruvada --- Documentation/hid/intel-ish-hid.txt | 375 1 file changed, 375 insertions(+) create mode 100644

[RFC 4/4] hid: intel-ish-hid: ISH HID client driver

From: Daniel Drubin This driver is responsible for implementing ISH HID client, which gets HID description and report. Once it has completely gets report descriptors, it registers as a HID LL drivers. This implements necessary callbacks so that it can be used by HID

[RFC 1/4] Documentation: hid: Intel ISH HID document

Document explaining ISH HID operation and implementation. Signed-off-by: Srinivas Pandruvada --- Documentation/hid/intel-ish-hid.txt | 375 1 file changed, 375 insertions(+) create mode 100644 Documentation/hid/intel-ish-hid.txt diff --git

[RFC 4/4] hid: intel-ish-hid: ISH HID client driver

From: Daniel Drubin This driver is responsible for implementing ISH HID client, which gets HID description and report. Once it has completely gets report descriptors, it registers as a HID LL drivers. This implements necessary callbacks so that it can be used by HID sensor hub driver.

[RFC 2/4] hid: intel_ish-hid: ISH Transport layer

From: Daniel Drubin The ISH transport layer (ishtp) is a bi-directional protocol implemented on the top of PCI based inter processor communication layer. This layer offers: - Connection management - Flow control with the firmware - Multiple client sessions - Client

[RFC 2/4] hid: intel_ish-hid: ISH Transport layer

From: Daniel Drubin The ISH transport layer (ishtp) is a bi-directional protocol implemented on the top of PCI based inter processor communication layer. This layer offers: - Connection management - Flow control with the firmware - Multiple client sessions - Client message transfer - Client

[RFC 3/4] hid: intel-ish-hid: ipc layer

From: Daniel Drubin This layer is responsible for - Enumerating over PCI bus - Inform FW about host readiness - Provide HW interface to transport layer for control and messages - Interrupt handling and routing Signed-off-by: Srinivas Pandruvada

[RFC 3/4] hid: intel-ish-hid: ipc layer

From: Daniel Drubin This layer is responsible for - Enumerating over PCI bus - Inform FW about host readiness - Provide HW interface to transport layer for control and messages - Interrupt handling and routing Signed-off-by: Srinivas Pandruvada --- drivers/hid/intel-ish-hid/Kconfig

[RFC 0/4] Intel Integrated Sensor Hub Support (ISH)

Starting from Cherrytrail, multiple generation of Intel processors offers on package sensor hub. Several recent tablets, 2-in-1 convertible laptops are using ISH instead of external sensor hubs. This resulted in lack of support of sensor function like device rotation and auto backlight adjustment.

[RFC 0/4] Intel Integrated Sensor Hub Support (ISH)

Starting from Cherrytrail, multiple generation of Intel processors offers on package sensor hub. Several recent tablets, 2-in-1 convertible laptops are using ISH instead of external sensor hubs. This resulted in lack of support of sensor function like device rotation and auto backlight adjustment.

Re: WMI driver no longer load after switching to generic UUID library

Thanks guys. keyboard functions are working now. kui.z On Mon, May 30, 2016 at 7:40 AM, Andy Shevchenko wrote: > On Mon, 2016-05-30 at 12:52 +0200, Bjørn Mork wrote: >> How about the untested attached patch? >> > > Facepalm.jpg! > > Good catch! > > The

Re: WMI driver no longer load after switching to generic UUID library

Thanks guys. keyboard functions are working now. kui.z On Mon, May 30, 2016 at 7:40 AM, Andy Shevchenko wrote: > On Mon, 2016-05-30 at 12:52 +0200, Bjørn Mork wrote: >> How about the untested attached patch? >> > > Facepalm.jpg! > > Good catch! > > The question is how it passed in our

Re: [PATCHv3 00/48] thermal: reorganizing thermal core

Hi Eduardo, On Tuesday 31 May 2016 03:45 AM, Eduardo Valentin wrote: Folks, This is V3 of a patch series to improve thermal core. The idea here is to reorganize the code and improve the way we handle sysfs entries. The change in behavior is that now, thermal zones with empty .type will not be

Re: [PATCHv3 00/48] thermal: reorganizing thermal core

Hi Eduardo, On Tuesday 31 May 2016 03:45 AM, Eduardo Valentin wrote: Folks, This is V3 of a patch series to improve thermal core. The idea here is to reorganize the code and improve the way we handle sysfs entries. The change in behavior is that now, thermal zones with empty .type will not be

Re: shrink_active_list/try_to_release_page bug? (was Re: xfs trace in 4.4.2 / also in 4.3.3 WARNING fs/xfs/xfs_aops.c:1232 xfs_vm_releasepage)

On Tue, May 31, 2016 at 12:55:09PM +1000, Dave Chinner wrote: > On Tue, May 31, 2016 at 10:07:24AM +0900, Minchan Kim wrote: > > On Tue, May 31, 2016 at 08:36:57AM +1000, Dave Chinner wrote: > > > [adding lkml and linux-mm to the cc list] > > > > > > On Mon, May 30, 2016 at 09:23:48AM +0200,

Re: shrink_active_list/try_to_release_page bug? (was Re: xfs trace in 4.4.2 / also in 4.3.3 WARNING fs/xfs/xfs_aops.c:1232 xfs_vm_releasepage)

On Tue, May 31, 2016 at 12:55:09PM +1000, Dave Chinner wrote: > On Tue, May 31, 2016 at 10:07:24AM +0900, Minchan Kim wrote: > > On Tue, May 31, 2016 at 08:36:57AM +1000, Dave Chinner wrote: > > > [adding lkml and linux-mm to the cc list] > > > > > > On Mon, May 30, 2016 at 09:23:48AM +0200,

Re: [RFC PATCH 2/4] mm: Change the interface for __tlb_remove_page

> >> @@ -1202,7 +1205,12 @@ again: > >>if (force_flush) { > >>force_flush = 0; > >>tlb_flush_mmu_free(tlb); > >> - > >> + if (pending_page) { > >> + /* remove the page with new size */ > >> + __tlb_adjust_range(tlb, tlb->addr);

Re: [RFC PATCH 2/4] mm: Change the interface for __tlb_remove_page

> >> @@ -1202,7 +1205,12 @@ again: > >>if (force_flush) { > >>force_flush = 0; > >>tlb_flush_mmu_free(tlb); > >> - > >> + if (pending_page) { > >> + /* remove the page with new size */ > >> + __tlb_adjust_range(tlb, tlb->addr);

Re: [PATCH v3] sched: fix first task of a task group is attached twice

On Mon, May 30, 2016 at 05:52:20PM +0200, Vincent Guittot wrote: > The cfs_rq->avg.last_update_time is initialize to 0 with the main effect > that the 1st sched_entity that will be attached, will keep its > last_update_time set to 0 and will attached once again during the > enqueue. > Initialize

Re: [PATCH v3] sched: fix first task of a task group is attached twice

On Mon, May 30, 2016 at 05:52:20PM +0200, Vincent Guittot wrote: > The cfs_rq->avg.last_update_time is initialize to 0 with the main effect > that the 1st sched_entity that will be attached, will keep its > last_update_time set to 0 and will attached once again during the > enqueue. > Initialize

linux-next: Tree for May 31

Hi all, Changes since 20160530: My fixes tree contains: of: silence warnings due to max() usage The drm-intel tree gained conflicts against Linus' tree. Non-merge commits (relative to Linus' tree): 946 788 files changed, 26579 insertions(+), 12133 deletions

linux-next: Tree for May 31

Hi all, Changes since 20160530: My fixes tree contains: of: silence warnings due to max() usage The drm-intel tree gained conflicts against Linus' tree. Non-merge commits (relative to Linus' tree): 946 788 files changed, 26579 insertions(+), 12133 deletions

Re: [PATCH V2 2/2] vhost_net: conditionally enable tx polling

On 2016年05月30日 23:55, Michael S. Tsirkin wrote: On Mon, May 30, 2016 at 02:47:54AM -0400, Jason Wang wrote: We always poll tx for socket, this is sub optimal since: - it will be only used when we exceed the sndbuf of the socket. - since we use two independent polls for tx and vq, this will

Re: [PATCH V2 2/2] vhost_net: conditionally enable tx polling

On 2016年05月30日 23:55, Michael S. Tsirkin wrote: On Mon, May 30, 2016 at 02:47:54AM -0400, Jason Wang wrote: We always poll tx for socket, this is sub optimal since: - it will be only used when we exceed the sndbuf of the socket. - since we use two independent polls for tx and vq, this will

GRsecurity is preventing others from employing their rights under version 2 the GPL to redistribute source code

GRsecurity (Brad Spengler) is preventing others from employing their rights under version 2 the GPL to redistribute (by threatening them with a non-renewal of a contract to recive this patch to the linux kernel.) (GRsecurity is a derivative work of the linux kernel (it is a patch)) People who

GRsecurity is preventing others from employing their rights under version 2 the GPL to redistribute source code

GRsecurity (Brad Spengler) is preventing others from employing their rights under version 2 the GPL to redistribute (by threatening them with a non-renewal of a contract to recive this patch to the linux kernel.) (GRsecurity is a derivative work of the linux kernel (it is a patch)) People who

Re: [PATCH V2 1/2] vhost_net: stop polling socket during rx processing

On 2016年05月30日 23:47, Michael S. Tsirkin wrote: On Mon, May 30, 2016 at 02:47:53AM -0400, Jason Wang wrote: We don't stop rx polling socket during rx processing, this will lead unnecessary wakeups from under layer net devices (E.g sock_def_readable() form tun). Rx will be slowed down in this

Re: [PATCH V2 1/2] vhost_net: stop polling socket during rx processing

On 2016年05月30日 23:47, Michael S. Tsirkin wrote: On Mon, May 30, 2016 at 02:47:53AM -0400, Jason Wang wrote: We don't stop rx polling socket during rx processing, this will lead unnecessary wakeups from under layer net devices (E.g sock_def_readable() form tun). Rx will be slowed down in this

Re: [PATCH] ARM: dts: sun7i: Add dts file for Bananapi M1 Plus board

Hi, On Tue, May 31, 2016 at 3:43 AM, Maxime Ripard wrote: > Hi, > > On Mon, May 30, 2016 at 08:30:13PM +0800, luoyi...@gmail.com wrote: >> From: luoyi >> >> Add support for the Bananapi M1 Plus A20 development board from >> sinovoip.com.cn

Re: [PATCH] ARM: dts: sun7i: Add dts file for Bananapi M1 Plus board

Hi, On Tue, May 31, 2016 at 3:43 AM, Maxime Ripard wrote: > Hi, > > On Mon, May 30, 2016 at 08:30:13PM +0800, luoyi...@gmail.com wrote: >> From: luoyi >> >> Add support for the Bananapi M1 Plus A20 development board from >> sinovoip.com.cn . >> This board features 1G RAM, 2 USB A receptacles,

[BUG] Page allocation failures with newest kernels

Hi, After rebasing platform support of two different ARMv8 SoC's from v4.1 baseline to v4.4 it occurred that stressed systems tend to have page allocation problems, related to creating new slabs: http://pastebin.com/FhRW5DsF Steps to reproduce: - use SATA drive (on-board or over PCIe) with 2

[BUG] Page allocation failures with newest kernels

Hi, After rebasing platform support of two different ARMv8 SoC's from v4.1 baseline to v4.4 it occurred that stressed systems tend to have page allocation problems, related to creating new slabs: http://pastebin.com/FhRW5DsF Steps to reproduce: - use SATA drive (on-board or over PCIe) with 2

RE: [PATCH v2 3/3] ACPI / button: Send "open" state after boot/resume

Hi, > From: Benjamin Tissoires [mailto:benjamin.tissoi...@gmail.com] > Subject: Re: [PATCH v2 3/3] ACPI / button: Send "open" state after > boot/resume > > On Fri, May 27, 2016 at 9:16 AM, Lv Zheng wrote: > > Linux userspace (systemd-logind) keeps on rechecking lid state

RE: [PATCH v2 3/3] ACPI / button: Send "open" state after boot/resume

Hi, > From: Benjamin Tissoires [mailto:benjamin.tissoi...@gmail.com] > Subject: Re: [PATCH v2 3/3] ACPI / button: Send "open" state after > boot/resume > > On Fri, May 27, 2016 at 9:16 AM, Lv Zheng wrote: > > Linux userspace (systemd-logind) keeps on rechecking lid state when the > > lid state

Re: shrink_active_list/try_to_release_page bug? (was Re: xfs trace in 4.4.2 / also in 4.3.3 WARNING fs/xfs/xfs_aops.c:1232 xfs_vm_releasepage)

On Tue, May 31, 2016 at 10:07:24AM +0900, Minchan Kim wrote: > On Tue, May 31, 2016 at 08:36:57AM +1000, Dave Chinner wrote: > > [adding lkml and linux-mm to the cc list] > > > > On Mon, May 30, 2016 at 09:23:48AM +0200, Stefan Priebe - Profihost AG > > wrote: > > > Hi Dave, > > > Hi Brian, >

Re: shrink_active_list/try_to_release_page bug? (was Re: xfs trace in 4.4.2 / also in 4.3.3 WARNING fs/xfs/xfs_aops.c:1232 xfs_vm_releasepage)

On Tue, May 31, 2016 at 10:07:24AM +0900, Minchan Kim wrote: > On Tue, May 31, 2016 at 08:36:57AM +1000, Dave Chinner wrote: > > [adding lkml and linux-mm to the cc list] > > > > On Mon, May 30, 2016 at 09:23:48AM +0200, Stefan Priebe - Profihost AG > > wrote: > > > Hi Dave, > > > Hi Brian, >

linux-next: build warnings after merge of the rtc tree

Hi Alexandre, After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) produced these warnings: In file included from drivers/char/mwave/smapi.c:51:0: drivers/char/mwave/smapi.h:52:0: warning: "TRUE" redefined #define TRUE 1 ^ In file included from include/acpi/acpi.h:58:0,

linux-next: build warnings after merge of the rtc tree

Hi Alexandre, After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) produced these warnings: In file included from drivers/char/mwave/smapi.c:51:0: drivers/char/mwave/smapi.h:52:0: warning: "TRUE" redefined #define TRUE 1 ^ In file included from include/acpi/acpi.h:58:0,

Re: [gpio] 86ea8a95a4: kernel BUG at drivers/base/driver.c:153!

mu-system-i386 -enable-kvm -cpu Haswell,+smep,+smap -kernel > /pkg/linux/i386-randconfig-x0-05280946/gcc-6/86ea8a95a42f752fe0aa1c7ad1bfe8ce9be5d30e/vmlinuz-4.6.0-rc4-00031-g86ea8a9 > -append 'root=/dev/ram0 user=lkp > job=/lkp/scheduled/vm-vp-quantal-i386-61/bisect_boot-1-quantal-core-i386.cgz-i386-randconfig-x0-05280946-86ea8

Re: [gpio] 86ea8a95a4: kernel BUG at drivers/base/driver.c:153!

mu-system-i386 -enable-kvm -cpu Haswell,+smep,+smap -kernel > /pkg/linux/i386-randconfig-x0-05280946/gcc-6/86ea8a95a42f752fe0aa1c7ad1bfe8ce9be5d30e/vmlinuz-4.6.0-rc4-00031-g86ea8a9 > -append 'root=/dev/ram0 user=lkp > job=/lkp/scheduled/vm-vp-quantal-i386-61/bisect_boot-1-quantal-core-i386.cgz-i386-randconfig-x0-05280946-86ea8

Re: [PATCH v5 0/2] skb_array: array based FIFO for skbs

On 2016年05月30日 23:37, Michael S. Tsirkin wrote: On Mon, May 30, 2016 at 05:59:33PM +0800, Jason Wang wrote: On 2016年05月23日 18:43, Michael S. Tsirkin wrote: This is in response to the proposal by Jason to make tun rx packet queue lockless using a circular buffer. My testing seems to show

Re: [PATCH v3 1/1] ovl: setxattr: don't deadlock when called from ima_fix_xattr.

On Mon, 2016-05-30 at 16:10 +0200, Miklos Szeredi wrote: > On Fri, May 20, 2016 at 11:53:18PM +0300, Krisztian Litkey wrote: > > On Fri, May 20, 2016 at 8:00 PM, Mimi Zohar > > wrote: > > > > We deferred __fput() back in 2012 in order for IMA to safely take the > > >

Re: [PATCH v5 0/2] skb_array: array based FIFO for skbs

On 2016年05月30日 23:37, Michael S. Tsirkin wrote: On Mon, May 30, 2016 at 05:59:33PM +0800, Jason Wang wrote: On 2016年05月23日 18:43, Michael S. Tsirkin wrote: This is in response to the proposal by Jason to make tun rx packet queue lockless using a circular buffer. My testing seems to show

Re: [PATCH v3 1/1] ovl: setxattr: don't deadlock when called from ima_fix_xattr.

On Mon, 2016-05-30 at 16:10 +0200, Miklos Szeredi wrote: > On Fri, May 20, 2016 at 11:53:18PM +0300, Krisztian Litkey wrote: > > On Fri, May 20, 2016 at 8:00 PM, Mimi Zohar > > wrote: > > > > We deferred __fput() back in 2012 in order for IMA to safely take the > > > i_mutex and write

Re: [PATCH v4] Axi-usb: Add support for 64-bit addressing.

On Mon, May 30, 2016 at 10:16 PM, Nava kishore Manne wrote: > This patch updates the driver to support 64-bit DMA addressing. > > Signed-off-by: Nava kishore Manne > --- > Changes for v4: > -Used boolen property insted of addrwith property

Re: [PATCH v4] Axi-usb: Add support for 64-bit addressing.

On Mon, May 30, 2016 at 10:16 PM, Nava kishore Manne wrote: > This patch updates the driver to support 64-bit DMA addressing. > > Signed-off-by: Nava kishore Manne > --- > Changes for v4: > -Used boolen property insted of addrwith property in the DT > as

[gpio] 86ea8a95a4: kernel BUG at drivers/base/driver.c:153!

b=/lkp/scheduled/vm-vp-quantal-i386-61/bisect_boot-1-quantal-core-i386.cgz-i386-randconfig-x0-05280946-86ea8a95a42f752fe0aa1c7ad1bfe8ce9be5d30e-20160530-53474-w6nzwk-0.yaml ARCH=i386 kconfig=i386-randconfig-x0-05280946 branch=linux-devel/devel-spot-201605280759 commit=86ea8a95a42f752fe0aa1c7a

[gpio] 86ea8a95a4: kernel BUG at drivers/base/driver.c:153!

b=/lkp/scheduled/vm-vp-quantal-i386-61/bisect_boot-1-quantal-core-i386.cgz-i386-randconfig-x0-05280946-86ea8a95a42f752fe0aa1c7ad1bfe8ce9be5d30e-20160530-53474-w6nzwk-0.yaml ARCH=i386 kconfig=i386-randconfig-x0-05280946 branch=linux-devel/devel-spot-201605280759 commit=86ea8a95a42f752fe0aa1c7a

[gpio] cc736607c8: kernel BUG at drivers/base/driver.c:153!

FYI, we noticed the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit cc736607c86d39ea078519af0de6ee0fbf3096a6 ("gpio: ws16c48: Utilize the ISA bus driver") on test machine: vm-kbuild-yocto-i386: 2 threads qemu-system-i386 -enable-kvm with

[gpio] cc736607c8: kernel BUG at drivers/base/driver.c:153!

FYI, we noticed the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit cc736607c86d39ea078519af0de6ee0fbf3096a6 ("gpio: ws16c48: Utilize the ISA bus driver") on test machine: vm-kbuild-yocto-i386: 2 threads qemu-system-i386 -enable-kvm with

[gpio] 72bf7443ba: kernel BUG at drivers/base/driver.c:153!

FYI, we noticed the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit 72bf7443ba618b9f7a3167c1f591a0dc00faeb2d ("gpio: 104-idi-48: Utilize the ISA bus driver") on test machine: vm-vp-quantal-i386: 1 threads qemu-system-i386 -enable-kvm -cpu

[gpio] 72bf7443ba: kernel BUG at drivers/base/driver.c:153!

FYI, we noticed the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit 72bf7443ba618b9f7a3167c1f591a0dc00faeb2d ("gpio: 104-idi-48: Utilize the ISA bus driver") on test machine: vm-vp-quantal-i386: 1 threads qemu-system-i386 -enable-kvm -cpu

Re: [PATCH v3 1/1] ovl: setxattr: don't deadlock when called from ima_fix_xattr.

On Mon, 2016-05-30 at 17:50 +0100, Al Viro wrote: > Only tangentially related, but... that bug had been discussed, > without any results: the fallback in ima_d_path() to ->d_name.name is > completely broken. There is no warranty whatsoever that dentry won't be > renamed, with its earlier

Re: [PATCH v3 1/1] ovl: setxattr: don't deadlock when called from ima_fix_xattr.

On Mon, 2016-05-30 at 17:50 +0100, Al Viro wrote: > Only tangentially related, but... that bug had been discussed, > without any results: the fallback in ima_d_path() to ->d_name.name is > completely broken. There is no warranty whatsoever that dentry won't be > renamed, with its earlier

Re: [PATCH stable 3.16+] crypto: s5p-sss - Fix missed interrupts when working with 8 kB blocks

On Mon, May 30, 2016 at 12:09:28PM +0200, Krzysztof Kozlowski wrote: > commit 79152e8d085fd64484afd473ef6830b45518acba upstream. > > The tcrypt testing module on Exynos5422-based Odroid XU3/4 board failed on > testing 8 kB size blocks: > > $ sudo modprobe tcrypt sec=1 mode=500 >

Re: [PATCH stable 3.16+] crypto: s5p-sss - Fix missed interrupts when working with 8 kB blocks

On Mon, May 30, 2016 at 12:09:28PM +0200, Krzysztof Kozlowski wrote: > commit 79152e8d085fd64484afd473ef6830b45518acba upstream. > > The tcrypt testing module on Exynos5422-based Odroid XU3/4 board failed on > testing 8 kB size blocks: > > $ sudo modprobe tcrypt sec=1 mode=500 >

Re: [PATCH trivial] include/linux/memblock.h: Clean up code for several trivial details

On 2016年05月30日 22:33, Joe Perches wrote: > On Mon, 2016-05-30 at 22:21 +0800, Chen Gang wrote: >> No, they are not necessary. But for me, it will be more clearer, since >> in our kernel (at least in include/linux/), almost all Boolean functions >> use Boolean value or expression for return (and

Re: [PATCH trivial] include/linux/memblock.h: Clean up code for several trivial details

On 2016年05月30日 22:33, Joe Perches wrote: > On Mon, 2016-05-30 at 22:21 +0800, Chen Gang wrote: >> No, they are not necessary. But for me, it will be more clearer, since >> in our kernel (at least in include/linux/), almost all Boolean functions >> use Boolean value or expression for return (and

Re: building and using modules on arm64 hikey board

On Mon, 30 May 2016 20:54:33 +0200 Arend van Spriel wrote: > On 30-05-16 13:30, Ard Biesheuvel wrote: > > This is likely caused by the fact that the Android AArch64 toolchain uses > > -fpic by default. Could you try adding -fno-pic to the CFLAGS? > > I did only

Re: building and using modules on arm64 hikey board

On Mon, 30 May 2016 20:54:33 +0200 Arend van Spriel wrote: > On 30-05-16 13:30, Ard Biesheuvel wrote: > > This is likely caused by the fact that the Android AArch64 toolchain uses > > -fpic by default. Could you try adding -fno-pic to the CFLAGS? > > I did only to notice with 'make V=1 ...'

[PATCH V9 1/1] usb:serial: Add Fintek F81532/534 driver

This driver is for Fintek F81532/F81534 USB to Serial Ports IC. F81532 spec: https://drive.google.com/file/d/0B8vRwwYO7aMFOTRRMmhWQVNvajQ/view? usp=sharing F81534 spec: https://drive.google.com/file/d/0B8vRwwYO7aMFV29pQWJqbVBNc00/view? usp=sharing Features: 1. F81532 is 1-to-2 & F81534 is

[PATCH V9 1/1] usb:serial: Add Fintek F81532/534 driver

This driver is for Fintek F81532/F81534 USB to Serial Ports IC. F81532 spec: https://drive.google.com/file/d/0B8vRwwYO7aMFOTRRMmhWQVNvajQ/view? usp=sharing F81534 spec: https://drive.google.com/file/d/0B8vRwwYO7aMFV29pQWJqbVBNc00/view? usp=sharing Features: 1. F81532 is 1-to-2 & F81534 is

Re: [PATCH v2 3/3] cpufreq: schedutil: map raw required frequency to driver frequency

2016-05-30 22:25 GMT+08:00 Rafael J. Wysocki : > On Mon, May 30, 2016 at 12:18 PM, Viresh Kumar > wrote: >> On 29-05-16, 02:40, Rafael J. Wysocki wrote: >>> I can't really parse the above question, so I'm not going to try to >>> answer it. :-) >> >>

Re: [PATCH] usb:serial: Add Fintek F81532/534 driver

Hi, Ji-Ze Hong (Peter Hong) 於 2016/5/31 上午 09:33 寫道: This driver is for Fintek F81532/F81534 USB to Serial Ports IC. Sorry, I forgot to change the mail title for "PATCH V9". I'll resend a patch with title "PATCH V9". Thanks -- With Best Regards, Peter Hung

Re: [PATCH v2 3/3] cpufreq: schedutil: map raw required frequency to driver frequency

2016-05-30 22:25 GMT+08:00 Rafael J. Wysocki : > On Mon, May 30, 2016 at 12:18 PM, Viresh Kumar > wrote: >> On 29-05-16, 02:40, Rafael J. Wysocki wrote: >>> I can't really parse the above question, so I'm not going to try to >>> answer it. :-) >> >> Sorry about that :( >> >> IOW, I think that we

Re: [PATCH] usb:serial: Add Fintek F81532/534 driver

Hi, Ji-Ze Hong (Peter Hong) 於 2016/5/31 上午 09:33 寫道: This driver is for Fintek F81532/F81534 USB to Serial Ports IC. Sorry, I forgot to change the mail title for "PATCH V9". I'll resend a patch with title "PATCH V9". Thanks -- With Best Regards, Peter Hung

linux-next: build warnings after merge of the sound-asoc tree

Hi all, After merging the sound-asoc tree, today's linux-next build (x86_64 allmodconfig) produced these warnings: sound/soc/codecs/cs47l24.c: In function 'cs47l24_adsp2_irq' : sound/soc/codecs/cs47l24.c:1091:13: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]

linux-next: build warnings after merge of the sound-asoc tree

Hi all, After merging the sound-asoc tree, today's linux-next build (x86_64 allmodconfig) produced these warnings: sound/soc/codecs/cs47l24.c: In function 'cs47l24_adsp2_irq' : sound/soc/codecs/cs47l24.c:1091:13: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]

[PATCH] usb:serial: Add Fintek F81532/534 driver

This driver is for Fintek F81532/F81534 USB to Serial Ports IC. F81532 spec: https://drive.google.com/file/d/0B8vRwwYO7aMFOTRRMmhWQVNvajQ/view? usp=sharing F81534 spec: https://drive.google.com/file/d/0B8vRwwYO7aMFV29pQWJqbVBNc00/view? usp=sharing Features: 1. F81532 is 1-to-2 & F81534 is

[PATCH] usb:serial: Add Fintek F81532/534 driver

This driver is for Fintek F81532/F81534 USB to Serial Ports IC. F81532 spec: https://drive.google.com/file/d/0B8vRwwYO7aMFOTRRMmhWQVNvajQ/view? usp=sharing F81534 spec: https://drive.google.com/file/d/0B8vRwwYO7aMFV29pQWJqbVBNc00/view? usp=sharing Features: 1. F81532 is 1-to-2 & F81534 is

[PATCH v4 3/6] perf config: Use zfree() instead of free() at perf_config_set__delete()

perf_config_set__delete() delete allocated the config set but the global variable 'config_set' is used all around. So purge and zfree by an address of the global variable , i.e. 'struct perf_config_set **' type instead of using local variable 'set' of which type is 'struct perf_config_set *'.

[PATCH v4 3/6] perf config: Use zfree() instead of free() at perf_config_set__delete()

perf_config_set__delete() delete allocated the config set but the global variable 'config_set' is used all around. So purge and zfree by an address of the global variable , i.e. 'struct perf_config_set **' type instead of using local variable 'set' of which type is 'struct perf_config_set *'.

[PATCH v4 6/6] perf config: Reimplement show_config() using perf_config()

Old show_config() directly use config set so there are many duplicated code with perf_config_set__iter(). So reimplement show_config() using perf_config() that use perf_config_set__iter() with config set that already contains all configs. Cc: Namhyung Kim Cc: Jiri Olsa

[PATCH v4 5/6] perf config: Reset the config set at only 'config' sub-command

When first calling perf_config(), the config set is initialized collecting both user and system config files (i.e. user config ~/.perfconfig and system config $(sysconfdir)/perfconfig) so config set contains not only user config but also system config key-value pairs. (User config has higher

[PATCH v4 5/6] perf config: Reset the config set at only 'config' sub-command

When first calling perf_config(), the config set is initialized collecting both user and system config files (i.e. user config ~/.perfconfig and system config $(sysconfdir)/perfconfig) so config set contains not only user config but also system config key-value pairs. (User config has higher

[PATCH v4 6/6] perf config: Reimplement show_config() using perf_config()

Old show_config() directly use config set so there are many duplicated code with perf_config_set__iter(). So reimplement show_config() using perf_config() that use perf_config_set__iter() with config set that already contains all configs. Cc: Namhyung Kim Cc: Jiri Olsa Cc: Masami Hiramatsu

[PATCH v4 2/6] perf config: Add global variable 'config_set'

The config set is prepared by collecting all configs from config files (i.e. user config ~/.perfconfig and system config $(sysconfdir)/perfconfig) so the config set contains all config key-value pairs. We need to use it as global variable to share it. And in near future, the variable will be

[PATCH v4 4/6] perf config: Reimplement perf_config() using perf_config_set__iter()

Everytime perf_config() is called, perf_config() always read config files. (i.e. user config '~/.perfconfig' and system config '$(sysconfdir)/perfconfig') But we need to use the config set that already contains all config key-value pairs to avoid this repetitive work reading the config files in

  1   2   3   4   5   6   7   8   9   10   >