Re: [PATCH v4] Input - surface3_spi: add new driver for the Surface 3

On Thu, May 19, 2016 at 10:32:35AM +0200, Benjamin Tissoires wrote: > This is a basic driver for the Surface 3. I am not so sure it will work > with any firmwares as most values are encoded, but given that I only have > access to my current device with its firmware and I don't have the >

Re: [PATCH v4] Input - surface3_spi: add new driver for the Surface 3

On Thu, May 19, 2016 at 10:32:35AM +0200, Benjamin Tissoires wrote: > This is a basic driver for the Surface 3. I am not so sure it will work > with any firmwares as most values are encoded, but given that I only have > access to my current device with its firmware and I don't have the >

Re: UBSAN whinge in ihci-hub.c

2016-05-18 22:28 GMT+03:00 Alan Stern : > On Wed, 18 May 2016, Andrey Ryabinin wrote: > >> 2016-05-18 19:09 GMT+03:00 Alan Stern : >> > On Wed, 18 May 2016, Andrey Ryabinin wrote: >> > >> >> 2016-05-18 17:40 GMT+03:00 Alan Stern

Re: UBSAN whinge in ihci-hub.c

2016-05-18 22:28 GMT+03:00 Alan Stern : > On Wed, 18 May 2016, Andrey Ryabinin wrote: > >> 2016-05-18 19:09 GMT+03:00 Alan Stern : >> > On Wed, 18 May 2016, Andrey Ryabinin wrote: >> > >> >> 2016-05-18 17:40 GMT+03:00 Alan Stern : >> >> >> >> > All right, I'm getting very tired of all these bug

[git pull] IOMMU Updates for Linux v4.7

Hi Linus, The following changes since commit 44549e8f5eea4e0a41b487b63e616cb089922b99: Linux 4.6-rc7 (2016-05-08 14:38:32 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-updates-v4.7 for you to fetch changes up to

[git pull] IOMMU Updates for Linux v4.7

Hi Linus, The following changes since commit 44549e8f5eea4e0a41b487b63e616cb089922b99: Linux 4.6-rc7 (2016-05-08 14:38:32 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-updates-v4.7 for you to fetch changes up to

Re: [PATCH V5 3/3] soc/tegra: pmc: Add support for IO pads power state and voltage

On Thursday 19 May 2016 09:24 PM, Jon Hunter wrote: On 12/05/16 13:21, Laxman Dewangan wrote: The IO pins of Tegra SoCs are grouped for common control of IO interface like setting voltage signal levels and power state of the interface. The group is generally referred as IO pads. The power

Re: [PATCH V5 3/3] soc/tegra: pmc: Add support for IO pads power state and voltage

On Thursday 19 May 2016 09:24 PM, Jon Hunter wrote: On 12/05/16 13:21, Laxman Dewangan wrote: The IO pins of Tegra SoCs are grouped for common control of IO interface like setting voltage signal levels and power state of the interface. The group is generally referred as IO pads. The power

Re: [PATCH 3/4] rcutorture: Make -soundhw a x86 specific option

On Thu, May 19, 2016 at 08:40:42AM -0700, Josh Triplett wrote: > On Thu, May 19, 2016 at 07:10:13AM -0700, Paul E. McKenney wrote: > > On Wed, May 18, 2016 at 09:23:10PM -0700, Josh Triplett wrote: > > > On Thu, May 19, 2016 at 11:42:23AM +0800, Boqun Feng wrote: > > > > The option "-soundhw

Re: [PATCH 3/4] rcutorture: Make -soundhw a x86 specific option

On Thu, May 19, 2016 at 08:40:42AM -0700, Josh Triplett wrote: > On Thu, May 19, 2016 at 07:10:13AM -0700, Paul E. McKenney wrote: > > On Wed, May 18, 2016 at 09:23:10PM -0700, Josh Triplett wrote: > > > On Thu, May 19, 2016 at 11:42:23AM +0800, Boqun Feng wrote: > > > > The option "-soundhw

Re: [PATCH 1/3] spi/rockchip: add rk3036/rk3228/rk3368 socs for spi document

Am Freitag, 20. Mai 2016, 00:04:07 schrieb Caesar Wang: > 在 2016年05月19日 23:51, Heiko Stuebner 写道: > > Am Donnerstag, 19. Mai 2016, 23:47:02 schrieb Caesar Wang: > >> We had supported the rk3036/rk3066/rk3188/rk3228/rk3288/rk3368/rk3399 > >> family SoCs in linux kernel. > >> > >> Let's add the

Re: [PATCH 1/3] spi/rockchip: add rk3036/rk3228/rk3368 socs for spi document

Am Freitag, 20. Mai 2016, 00:04:07 schrieb Caesar Wang: > 在 2016年05月19日 23:51, Heiko Stuebner 写道: > > Am Donnerstag, 19. Mai 2016, 23:47:02 schrieb Caesar Wang: > >> We had supported the rk3036/rk3066/rk3188/rk3228/rk3288/rk3368/rk3399 > >> family SoCs in linux kernel. > >> > >> Let's add the

Re: [PATCHv8 26/32] thp: update Documentation/vm/transhuge.txt

Hello Kirill, On 12/05/16 16:41, Kirill A. Shutemov wrote: Add info about tmpfs/shmem with huge pages. Signed-off-by: Kirill A. Shutemov --- Documentation/vm/transhuge.txt | 130 + 1 file changed, 93 insertions(+), 37

Re: [PATCHv8 26/32] thp: update Documentation/vm/transhuge.txt

Hello Kirill, On 12/05/16 16:41, Kirill A. Shutemov wrote: Add info about tmpfs/shmem with huge pages. Signed-off-by: Kirill A. Shutemov --- Documentation/vm/transhuge.txt | 130 + 1 file changed, 93 insertions(+), 37 deletions(-) diff --git

Re: [PATCH v4 2/6] perf tools: Promote proper messages for cross-platform unwind

On Thu, May 19, 2016 at 11:50:10AM -0300, Arnaldo Carvalho de Melo wrote: > Em Thu, May 19, 2016 at 11:47:38AM +, He Kuang escreveu: > > Currently, perf script uses host unwind methods to parse perf.data > > callchain info regardless of the target architecture. So we get wrong > > result and

Re: [PATCH v4 2/6] perf tools: Promote proper messages for cross-platform unwind

On Thu, May 19, 2016 at 11:50:10AM -0300, Arnaldo Carvalho de Melo wrote: > Em Thu, May 19, 2016 at 11:47:38AM +, He Kuang escreveu: > > Currently, perf script uses host unwind methods to parse perf.data > > callchain info regardless of the target architecture. So we get wrong > > result and

[PATCH v2 3/5] ACPI: table upgrade: move arch-specific symbol to asm/acpi.h

The constant that defines max phys address where the new upgraded ACPI table should be allocated is arch-specific. Move it to Signed-off-by: Aleksey Makarov --- arch/x86/include/asm/acpi.h | 2 ++ drivers/acpi/tables.c | 3 ++- 2 files changed, 4

[PATCH v2 3/5] ACPI: table upgrade: move arch-specific symbol to asm/acpi.h

The constant that defines max phys address where the new upgraded ACPI table should be allocated is arch-specific. Move it to Signed-off-by: Aleksey Makarov --- arch/x86/include/asm/acpi.h | 2 ++ drivers/acpi/tables.c | 3 ++- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git

[PATCH v2 1/5] ACPI: table upgrade: use cacheable map for tables

The new memory allocated in acpi_table_initrd_init() is used to copy the upgraded tables to it. So it should be mapped with early_memunmap() instead of early_ioremap(). This is critical for ARM. Signed-off-by: Aleksey Makarov Acked-by: Lv Zheng

[PATCH v2 4/5] ACPI: table upgrade: introduce ARCH_HAS_ACPI_TABLE_UPGRADE

We want to use the table upgrade feature in ARM64. Introduce a new configuration option that allows that. Signed-off-by: Aleksey Makarov --- arch/x86/Kconfig | 1 + drivers/acpi/Kconfig | 5 - 2 files changed, 5 insertions(+), 1 deletion(-) diff --git

[PATCH v2 1/5] ACPI: table upgrade: use cacheable map for tables

The new memory allocated in acpi_table_initrd_init() is used to copy the upgraded tables to it. So it should be mapped with early_memunmap() instead of early_ioremap(). This is critical for ARM. Signed-off-by: Aleksey Makarov Acked-by: Lv Zheng --- drivers/acpi/tables.c | 6 +++--- 1 file

[PATCH v2 4/5] ACPI: table upgrade: introduce ARCH_HAS_ACPI_TABLE_UPGRADE

We want to use the table upgrade feature in ARM64. Introduce a new configuration option that allows that. Signed-off-by: Aleksey Makarov --- arch/x86/Kconfig | 1 + drivers/acpi/Kconfig | 5 - 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/arch/x86/Kconfig

[PATCH v2 2/5] ACPI: table upgrade: refactor function definitions

Refer initrd_start, initrd_end directly from drivers/acpi/tables.c. This allows to use the table upgrade feature in architectures other than x86. Also this simplifies header files. The patch renames acpi_table_initrd_init() to acpi_table_upgrade() (what reflects the purpose of the function) and

[PATCH v2 2/5] ACPI: table upgrade: refactor function definitions

Refer initrd_start, initrd_end directly from drivers/acpi/tables.c. This allows to use the table upgrade feature in architectures other than x86. Also this simplifies header files. The patch renames acpi_table_initrd_init() to acpi_table_upgrade() (what reflects the purpose of the function) and

[PATCH v2 5/5] ACPI: ARM64: support for ACPI_TABLE_UPGRADE

From: Jon Masters This patch adds support for ACPI_TABLE_UPGRADE for ARM64 To access initrd image we need to move initialization of linear mapping a bit earlier. The implementation of the feature acpi_table_upgrade() (drivers/acpi/tables.c) works with initrd data represented

[PATCH v2 5/5] ACPI: ARM64: support for ACPI_TABLE_UPGRADE

From: Jon Masters This patch adds support for ACPI_TABLE_UPGRADE for ARM64 To access initrd image we need to move initialization of linear mapping a bit earlier. The implementation of the feature acpi_table_upgrade() (drivers/acpi/tables.c) works with initrd data represented as an array in

[PATCH v2 0/5] ACPI: ARM64: support for ACPI_TABLE_UPGRADE

access to the destination of new ACPI tables as suggested by Mark Rutland [2] and enables the feature for ARM64 It was first sent by Jon Masters [3] to linaro-acpi in December 2015 Tested on QEMU (arm64 and x86) and ThunderX Should be applied to next-20160519 v2: - add Acked-by: Lv Zheng <lv

[PATCH v2 0/5] ACPI: ARM64: support for ACPI_TABLE_UPGRADE

access to the destination of new ACPI tables as suggested by Mark Rutland [2] and enables the feature for ARM64 It was first sent by Jon Masters [3] to linaro-acpi in December 2015 Tested on QEMU (arm64 and x86) and ThunderX Should be applied to next-20160519 v2: - add Acked-by: Lv Zheng - replace

Re: Input: two merge window build fixes

On Thu, May 19, 2016 at 03:52:23PM +0200, Arnd Bergmann wrote: > Hi Dmitry, > > I ran into two new build regressions in the input subsystem with > today's linux-next, maybe you can apply these fixes before sending > off the pull request for v4.7. > > Arnd > > [PATCH 1/2] Input: atmel

Re: Input: two merge window build fixes

On Thu, May 19, 2016 at 03:52:23PM +0200, Arnd Bergmann wrote: > Hi Dmitry, > > I ran into two new build regressions in the input subsystem with > today's linux-next, maybe you can apply these fixes before sending > off the pull request for v4.7. > > Arnd > > [PATCH 1/2] Input: atmel

Re: [PATCH] fbcon: use default if cursor blink interval is not valid

On 05/18/2016 09:21 PM, Scot Doyle wrote: Two current [1] and three previous [2] systems locked during boot because the cursor flash timer was set using an ops->cur_blink_jiffies value of 0. Previous patches attempted to solve the problem by moving variable initialization earlier in the setup

Re: [PATCH] fbcon: use default if cursor blink interval is not valid

On 05/18/2016 09:21 PM, Scot Doyle wrote: Two current [1] and three previous [2] systems locked during boot because the cursor flash timer was set using an ops->cur_blink_jiffies value of 0. Previous patches attempted to solve the problem by moving variable initialization earlier in the setup

Re: [PATCH 1/3] spi/rockchip: add rk3036/rk3228/rk3368 socs for spi document

在 2016年05月19日 23:51, Heiko Stuebner 写道: Am Donnerstag, 19. Mai 2016, 23:47:02 schrieb Caesar Wang: We had supported the rk3036/rk3066/rk3188/rk3228/rk3288/rk3368/rk3399 family SoCs in linux kernel. Let's add the other SoCs, in order to a better understanding from the rockchip spi document.

Re: [PATCH 1/3] spi/rockchip: add rk3036/rk3228/rk3368 socs for spi document

在 2016年05月19日 23:51, Heiko Stuebner 写道: Am Donnerstag, 19. Mai 2016, 23:47:02 schrieb Caesar Wang: We had supported the rk3036/rk3066/rk3188/rk3228/rk3288/rk3368/rk3399 family SoCs in linux kernel. Let's add the other SoCs, in order to a better understanding from the rockchip spi document.

Re: [PATCH v4 1/6] perf tools: Set buildid dir under symfs when --symfs is provided

On Thu, May 19, 2016 at 11:47:37AM +, He Kuang wrote: > This patch moves the reference of buildid dir to 'symfs/.debug' and > skips the local buildid dir when '--symfs' is given, so that every > single file opened by perf is relateive to symfs directory now. > > Signed-off-by: He Kuang

Re: [PATCH v4 1/6] perf tools: Set buildid dir under symfs when --symfs is provided

On Thu, May 19, 2016 at 11:47:37AM +, He Kuang wrote: > This patch moves the reference of buildid dir to 'symfs/.debug' and > skips the local buildid dir when '--symfs' is given, so that every > single file opened by perf is relateive to symfs directory now. > > Signed-off-by: He Kuang

SCHED_DEADLINE cpudeadline.{h,c} fixup

Hi all, I took Luca's advice to isolate the deadline wrap-around bugfix with a first minimally invasive patch (1-line). This leaves some weirdness in how cpudl_change_key() is called. Therefore, the second patch does a minimum of refactory to make things more explicit and clear. The 3rd patch

SCHED_DEADLINE cpudeadline.{h,c} fixup

Hi all, I took Luca's advice to isolate the deadline wrap-around bugfix with a first minimally invasive patch (1-line). This leaves some weirdness in how cpudl_change_key() is called. Therefore, the second patch does a minimum of refactory to make things more explicit and clear. The 3rd patch

[RFC PATCH 1/4] Minimally invasive deadline wrap-around bugfix for the SCHED_DEADLINE cpu heap.

--- kernel/sched/cpudeadline.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/cpudeadline.c b/kernel/sched/cpudeadline.c index 5be5882..d418449 100644 --- a/kernel/sched/cpudeadline.c +++ b/kernel/sched/cpudeadline.c @@ -168,7 +168,7 @@ void cpudl_set(struct

Re: [GIT PULL 0/7] ARM: SoC changes for 4.7

On Tue, May 17, 2016 at 5:07 PM, Arnd Bergmann wrote: > Hi Linus, > > These are the first seven pull requests for arm-soc this time, there is > one small follow-up coming once the dependencies for that have landed > in your tree. > > Things remain relatively calm for us. We merged

[RFC PATCH 1/4] Minimally invasive deadline wrap-around bugfix for the SCHED_DEADLINE cpu heap.

--- kernel/sched/cpudeadline.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/cpudeadline.c b/kernel/sched/cpudeadline.c index 5be5882..d418449 100644 --- a/kernel/sched/cpudeadline.c +++ b/kernel/sched/cpudeadline.c @@ -168,7 +168,7 @@ void cpudl_set(struct

Re: [GIT PULL 0/7] ARM: SoC changes for 4.7

On Tue, May 17, 2016 at 5:07 PM, Arnd Bergmann wrote: > Hi Linus, > > These are the first seven pull requests for arm-soc this time, there is > one small follow-up coming once the dependencies for that have landed > in your tree. > > Things remain relatively calm for us. We merged 122 pull

[RFC PATCH 3/4] Make deadline max-heap faster avoiding real swaps on heapify ops.

--- kernel/sched/cpudeadline.c | 114 +++-- 1 file changed, 69 insertions(+), 45 deletions(-) diff --git a/kernel/sched/cpudeadline.c b/kernel/sched/cpudeadline.c index 3c42702..60f933a 100644 --- a/kernel/sched/cpudeadline.c +++

[RFC PATCH 3/4] Make deadline max-heap faster avoiding real swaps on heapify ops.

--- kernel/sched/cpudeadline.c | 114 +++-- 1 file changed, 69 insertions(+), 45 deletions(-) diff --git a/kernel/sched/cpudeadline.c b/kernel/sched/cpudeadline.c index 3c42702..60f933a 100644 --- a/kernel/sched/cpudeadline.c +++

[RFC PATCH 2/4] SCHED_DEADLINE cpu heap code clarification/refactory: - heapify_up factored out in new dedicated function (avoids repeatition of same code) - call to cpudl_change_key replaced with h

--- kernel/sched/cpudeadline.c | 38 +++--- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/kernel/sched/cpudeadline.c b/kernel/sched/cpudeadline.c index d418449..3c42702 100644 --- a/kernel/sched/cpudeadline.c +++ b/kernel/sched/cpudeadline.c @@

[RFC PATCH 2/4] SCHED_DEADLINE cpu heap code clarification/refactory: - heapify_up factored out in new dedicated function (avoids repeatition of same code) - call to cpudl_change_key replaced with h

--- kernel/sched/cpudeadline.c | 38 +++--- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/kernel/sched/cpudeadline.c b/kernel/sched/cpudeadline.c index d418449..3c42702 100644 --- a/kernel/sched/cpudeadline.c +++ b/kernel/sched/cpudeadline.c @@

[RFC PATCH 4/4] Split cpudl_set() into cpudl_set() and cpudl_clear(). These 2 exercise independent code paths and need different arguments.

--- kernel/sched/cpudeadline.c | 71 +- kernel/sched/cpudeadline.h | 3 +- kernel/sched/deadline.c| 10 +++ 3 files changed, 52 insertions(+), 32 deletions(-) diff --git a/kernel/sched/cpudeadline.c b/kernel/sched/cpudeadline.c index

[RFC PATCH 4/4] Split cpudl_set() into cpudl_set() and cpudl_clear(). These 2 exercise independent code paths and need different arguments.

--- kernel/sched/cpudeadline.c | 71 +- kernel/sched/cpudeadline.h | 3 +- kernel/sched/deadline.c| 10 +++ 3 files changed, 52 insertions(+), 32 deletions(-) diff --git a/kernel/sched/cpudeadline.c b/kernel/sched/cpudeadline.c index

[GIT PULL] sound updates for 4.7-rc1

Linus, please pull sound fixes for v4.7-rc1 from: git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git tags/sound-4.7-rc1 The topmost commit is 17e1717c11a34f9b0956e33e0c4a4e4ae8c51a57 sound updates for 4.7-rc1 This

[GIT PULL] sound updates for 4.7-rc1

Linus, please pull sound fixes for v4.7-rc1 from: git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git tags/sound-4.7-rc1 The topmost commit is 17e1717c11a34f9b0956e33e0c4a4e4ae8c51a57 sound updates for 4.7-rc1 This

Re: [PATCH V5 3/3] soc/tegra: pmc: Add support for IO pads power state and voltage

On 12/05/16 13:21, Laxman Dewangan wrote: > The IO pins of Tegra SoCs are grouped for common control of IO > interface like setting voltage signal levels and power state of > the interface. The group is generally referred as IO pads. The > power state and voltage control of IO pins can be done at

Re: [PATCH V5 3/3] soc/tegra: pmc: Add support for IO pads power state and voltage

On 12/05/16 13:21, Laxman Dewangan wrote: > The IO pins of Tegra SoCs are grouped for common control of IO > interface like setting voltage signal levels and power state of > the interface. The group is generally referred as IO pads. The > power state and voltage control of IO pins can be done at

Re: [PATCH 1/3] spi/rockchip: add rk3036/rk3228/rk3368 socs for spi document

Am Donnerstag, 19. Mai 2016, 23:47:02 schrieb Caesar Wang: > We had supported the rk3036/rk3066/rk3188/rk3228/rk3288/rk3368/rk3399 > family SoCs in linux kernel. > > Let's add the other SoCs, in order to a better understanding from the > rockchip spi document. > > Signed-off-by: Caesar Wang

Re: [PATCH 1/3] spi/rockchip: add rk3036/rk3228/rk3368 socs for spi document

Am Donnerstag, 19. Mai 2016, 23:47:02 schrieb Caesar Wang: > We had supported the rk3036/rk3066/rk3188/rk3228/rk3288/rk3368/rk3399 > family SoCs in linux kernel. > > Let's add the other SoCs, in order to a better understanding from the > rockchip spi document. > > Signed-off-by: Caesar Wang >

[PATCH v3 7/8] crypto: caam - add ARCH_LAYERSCAPE to supported architectures

This basically adds support for ls1043a platform. Signed-off-by: Horia Geantă --- drivers/crypto/caam/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/crypto/caam/Kconfig b/drivers/crypto/caam/Kconfig index d2c2909a4020..ff54c42e6e51

[PATCH v3 7/8] crypto: caam - add ARCH_LAYERSCAPE to supported architectures

This basically adds support for ls1043a platform. Signed-off-by: Horia Geantă --- drivers/crypto/caam/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/crypto/caam/Kconfig b/drivers/crypto/caam/Kconfig index d2c2909a4020..ff54c42e6e51 100644 ---

[GIT PULL] PCI changes for v4.7

Hi Linus, Here are the PCI changes I intend for v4.7. There is a silent conflict that needs to be resolved when you pull this: - e3156048346c ("iommu/amd: Fix checking of pci dma aliases"), which is already in your tree, added a use of PCI_DEV_FLAGS_DMA_ALIAS_DEVFN. - 338c3149a221

[GIT PULL] PCI changes for v4.7

Hi Linus, Here are the PCI changes I intend for v4.7. There is a silent conflict that needs to be resolved when you pull this: - e3156048346c ("iommu/amd: Fix checking of pci dma aliases"), which is already in your tree, added a use of PCI_DEV_FLAGS_DMA_ALIAS_DEVFN. - 338c3149a221

[PATCH 3/3] ARM: dts: rockchip: fixes the spi compatible for rk3036

That's seem the incorrect string to match the spi driver. Fixes commit f629fcfab2cd ("ARM: dts: rockchip: support the spi for rk3036") Signed-off-by: Caesar Wang Cc: Heiko Stuebner Cc: linux-rockc...@lists.infradead.org --- arch/arm/boot/dts/rk3036.dtsi

[PATCH 3/3] ARM: dts: rockchip: fixes the spi compatible for rk3036

That's seem the incorrect string to match the spi driver. Fixes commit f629fcfab2cd ("ARM: dts: rockchip: support the spi for rk3036") Signed-off-by: Caesar Wang Cc: Heiko Stuebner Cc: linux-rockc...@lists.infradead.org --- arch/arm/boot/dts/rk3036.dtsi | 2 +- 1 file changed, 1

[PATCH 2/3] spi/rockchip: add the rk3036/rk3228/rk3368 to match for driver

In gerenal, the "rockchip,rockchip-spi" string will match the dts that's great in spi driver. After all the most of rockchip SoCs ar same spi controller. Then, we should keep the old style to match the dts various. Signed-off-by: Caesar Wang Cc: Mark Brown

[PATCH 2/3] spi/rockchip: add the rk3036/rk3228/rk3368 to match for driver

In gerenal, the "rockchip,rockchip-spi" string will match the dts that's great in spi driver. After all the most of rockchip SoCs ar same spi controller. Then, we should keep the old style to match the dts various. Signed-off-by: Caesar Wang Cc: Mark Brown Cc: Heiko Stuebner Cc:

[PATCH 1/3] spi/rockchip: add rk3036/rk3228/rk3368 socs for spi document

We had supported the rk3036/rk3066/rk3188/rk3228/rk3288/rk3368/rk3399 family SoCs in linux kernel. Let's add the other SoCs, in order to a better understanding from the rockchip spi document. Signed-off-by: Caesar Wang Cc: Rob Herring Cc: Mark Brown

[PATCH 1/3] spi/rockchip: add rk3036/rk3228/rk3368 socs for spi document

We had supported the rk3036/rk3066/rk3188/rk3228/rk3288/rk3368/rk3399 family SoCs in linux kernel. Let's add the other SoCs, in order to a better understanding from the rockchip spi document. Signed-off-by: Caesar Wang Cc: Rob Herring Cc: Mark Brown Cc: Heiko Stuebner Cc:

Re: [RFC PATCHv2] usb: USB Type-C Connector Class

On Thu, May 19, 2016 at 04:48:46PM +0200, Oliver Neukum wrote: > On Thu, 2016-05-19 at 15:44 +0300, Heikki Krogerus wrote: > > > + dev->class = _class; > > + dev->parent = parent; > > + dev->type = _partner_dev_type; > > + dev_set_name(dev, "%s-partner", dev_name(>dev)); > > + > > + ret

Re: [RFC PATCHv2] usb: USB Type-C Connector Class

On Thu, May 19, 2016 at 04:48:46PM +0200, Oliver Neukum wrote: > On Thu, 2016-05-19 at 15:44 +0300, Heikki Krogerus wrote: > > > + dev->class = _class; > > + dev->parent = parent; > > + dev->type = _partner_dev_type; > > + dev_set_name(dev, "%s-partner", dev_name(>dev)); > > + > > + ret

[PATCH net-next] tools: hv: Add a script for bonding synthetic and VF NICs

This example script creates bonding network devices based on synthetic NIC (the virtual network adapter usually provided by Hyper-V) and the matching VF NIC (SRIOV virtual function). So the synthetic NIC and VF NIC can function as one network device, and fail over to the synthetic NIC if VF is

[PATCH net-next] tools: hv: Add a script for bonding synthetic and VF NICs

This example script creates bonding network devices based on synthetic NIC (the virtual network adapter usually provided by Hyper-V) and the matching VF NIC (SRIOV virtual function). So the synthetic NIC and VF NIC can function as one network device, and fail over to the synthetic NIC if VF is

Re: [PATCH v2] KVM: halt-polling: poll if emulated lapic timer will fire soon

On 05/19/2016 05:06 PM, Paolo Bonzini wrote: > > > On 19/05/2016 17:03, Christian Borntraeger wrote: Would this work too and be simpler? Hmm, your patch does only fiddle with the grow/shrink logic (which might be a good idea independently of this change), but the original patch

Re: [PATCH v2] KVM: halt-polling: poll if emulated lapic timer will fire soon

On 05/19/2016 05:06 PM, Paolo Bonzini wrote: > > > On 19/05/2016 17:03, Christian Borntraeger wrote: Would this work too and be simpler? Hmm, your patch does only fiddle with the grow/shrink logic (which might be a good idea independently of this change), but the original patch

Re: [PATCH 3/4] rcutorture: Make -soundhw a x86 specific option

On Thu, May 19, 2016 at 07:10:13AM -0700, Paul E. McKenney wrote: > On Wed, May 18, 2016 at 09:23:10PM -0700, Josh Triplett wrote: > > On Thu, May 19, 2016 at 11:42:23AM +0800, Boqun Feng wrote: > > > The option "-soundhw pcspk" gives me a error on PPC as follow: > > > > > > qemu-system-ppc64:

Re: [PATCH 3/4] rcutorture: Make -soundhw a x86 specific option

On Thu, May 19, 2016 at 07:10:13AM -0700, Paul E. McKenney wrote: > On Wed, May 18, 2016 at 09:23:10PM -0700, Josh Triplett wrote: > > On Thu, May 19, 2016 at 11:42:23AM +0800, Boqun Feng wrote: > > > The option "-soundhw pcspk" gives me a error on PPC as follow: > > > > > > qemu-system-ppc64:

Re: [tip:sched/core] sched/fair: Correct unit of load_above_capacity

On Fri, May 13, 2016 at 10:22:19AM +0200, Vincent Guittot wrote: > On 12 May 2016 at 23:48, Yuyang Du wrote: > > On Thu, May 12, 2016 at 03:31:51AM -0700, tip-bot for Morten Rasmussen > > wrote: > >> Commit-ID: cfa10334318d8212d007da8c771187643c9cef35 > >> Gitweb: > >>

Re: [tip:sched/core] sched/fair: Correct unit of load_above_capacity

On Fri, May 13, 2016 at 10:22:19AM +0200, Vincent Guittot wrote: > On 12 May 2016 at 23:48, Yuyang Du wrote: > > On Thu, May 12, 2016 at 03:31:51AM -0700, tip-bot for Morten Rasmussen > > wrote: > >> Commit-ID: cfa10334318d8212d007da8c771187643c9cef35 > >> Gitweb: > >>

Re: [PATCH] fbcon: use default if cursor blink interval is not valid

On Thu, May 19, 2016 at 10:22 PM, Scot Doyle wrote: > On Thu, 19 May 2016, Pavel Machek wrote: >> Hi! >> >> > Two current [1] and three previous [2] systems locked during boot >> > because the cursor flash timer was set using an ops->cur_blink_jiffies >> > value of 0.

Re: [PATCH] fbcon: use default if cursor blink interval is not valid

On Thu, May 19, 2016 at 10:22 PM, Scot Doyle wrote: > On Thu, 19 May 2016, Pavel Machek wrote: >> Hi! >> >> > Two current [1] and three previous [2] systems locked during boot >> > because the cursor flash timer was set using an ops->cur_blink_jiffies >> > value of 0. Previous patches attempted

Re: [RFC 0/8] usb: phy: msm: various cleanups

On 19 May 2016 at 01:52, Peter Chen wrote: > > > On Thu, May 19, 2016 at 5:24 AM, Arnd Bergmann wrote: >> >> I stumbled over this warning last week, which showed up after I had >> removed an incorrect patch from my randconfig build setup: >> >>

Re: [RFC 0/8] usb: phy: msm: various cleanups

On 19 May 2016 at 01:52, Peter Chen wrote: > > > On Thu, May 19, 2016 at 5:24 AM, Arnd Bergmann wrote: >> >> I stumbled over this warning last week, which showed up after I had >> removed an incorrect patch from my randconfig build setup: >> >> drivers/usb/phy/phy-msm-usb.c: In function

Re: [PATCH v2 2/3] drm/arm: Add support for Mali Display Processors

On Mon, Apr 25, 2016 at 03:19:23PM +0100, Liviu Dudau wrote: > Add support for the new family of Display Processors from ARM Ltd. > This commit adds basic support for Mali DP500, DP550 and DP650 > parts, with only the display engine being supported at the moment. > > Cc: David Brown

Re: [PATCH v2 2/3] drm/arm: Add support for Mali Display Processors

On Mon, Apr 25, 2016 at 03:19:23PM +0100, Liviu Dudau wrote: > Add support for the new family of Display Processors from ARM Ltd. > This commit adds basic support for Mali DP500, DP550 and DP650 > parts, with only the display engine being supported at the moment. > > Cc: David Brown > Cc: Brian

[PATCH v3 0/8] crypto: caam - add support for LS1043A SoC

v3: -DT maintainers - please ack patch 8/8 "arm64: dts: ls1043a: add crypto node" (to go into kernel 4.8 via crypto tree) -Fixed typo in pdb.h: s/be32/__be32 -Appended Acks (from v2) into commit messages -Tested that current patch set works on top of RSA support being added by Tudor Ambarus:

[PATCH v3 0/8] crypto: caam - add support for LS1043A SoC

v3: -DT maintainers - please ack patch 8/8 "arm64: dts: ls1043a: add crypto node" (to go into kernel 4.8 via crypto tree) -Fixed typo in pdb.h: s/be32/__be32 -Appended Acks (from v2) into commit messages -Tested that current patch set works on top of RSA support being added by Tudor Ambarus:

[PATCHv2] mm/zsmalloc: don't fail if can't create debugfs info

Change the return type of zs_pool_stat_create() to void, and remove the logic to abort pool creation if the stat debugfs dir/file could not be created. The debugfs stat file is for debugging/information only, and doesn't affect operation of zsmalloc; there is no reason to abort creating the pool

[PATCHv2] mm/zsmalloc: don't fail if can't create debugfs info

Change the return type of zs_pool_stat_create() to void, and remove the logic to abort pool creation if the stat debugfs dir/file could not be created. The debugfs stat file is for debugging/information only, and doesn't affect operation of zsmalloc; there is no reason to abort creating the pool

Re: [PATCH 2/2] lightnvm: hold nvm_lock until finish the target creation

Okay, I will rebase it on for-4.8/core. 2016-05-19 20:42 GMT+08:00 Matias Bjørling : > On 05/19/2016 08:38 AM, Wenwei Tao wrote: >> >> From: Wenwei Tao >> >> When create a target, we check whether the target is >> already exist first. If the answer is no,

Re: [PATCH 2/2] lightnvm: hold nvm_lock until finish the target creation

Okay, I will rebase it on for-4.8/core. 2016-05-19 20:42 GMT+08:00 Matias Bjørling : > On 05/19/2016 08:38 AM, Wenwei Tao wrote: >> >> From: Wenwei Tao >> >> When create a target, we check whether the target is >> already exist first. If the answer is no, we release >> the lock and continue the

[RFC PATCH v2 3/3] arch/powerpc : Enable optprobes support in powerpc

Signed-off-by: Anju T --- Documentation/features/debug/optprobes/arch-support.txt | 2 +- arch/powerpc/Kconfig| 1 + arch/powerpc/kernel/Makefile| 1 + 3 files changed, 3 insertions(+), 1 deletion(-) diff

[RFC PATCH v2 3/3] arch/powerpc : Enable optprobes support in powerpc

Signed-off-by: Anju T --- Documentation/features/debug/optprobes/arch-support.txt | 2 +- arch/powerpc/Kconfig| 1 + arch/powerpc/kernel/Makefile| 1 + 3 files changed, 3 insertions(+), 1 deletion(-) diff --git

Re: [PATCH 1/2] lightnvm: break the loop when rqd is not null

That is okay with me. 2016-05-19 20:40 GMT+08:00 Matias Bjørling : > On 05/19/2016 08:38 AM, Wenwei Tao wrote: >> >> From: Wenwei Tao >> >> Break the loop when rqd is not null to reduce >> unnecessary schedule. >> >> Signed-off-by: Wenwei Tao

Re: [PATCH 1/2] lightnvm: break the loop when rqd is not null

That is okay with me. 2016-05-19 20:40 GMT+08:00 Matias Bjørling : > On 05/19/2016 08:38 AM, Wenwei Tao wrote: >> >> From: Wenwei Tao >> >> Break the loop when rqd is not null to reduce >> unnecessary schedule. >> >> Signed-off-by: Wenwei Tao >> --- >> drivers/lightnvm/rrpc.c | 3 +++ >> 1

[PATCH v3 2/8] asm-generic/io.h: add io{read,write}64 accessors

This will allow device drivers to consistently use io{read,write}XX also for 64-bit accesses. Acked-by: Arnd Bergmann Signed-off-by: Horia Geantă --- include/asm-generic/io.h| 63 + include/asm-generic/iomap.h

[RFC PATCH v2 0/3] OPTPROBES for powerpc

Here are the RFC patchset of the kprobes jump optimization (a.k.a OPTPROBES)for powerpc. Kprobe being an inevitable tool for kernel developers,enhancing the performance of kprobe has got much importance. Currently kprobes inserts a trap instruction to probe a running kernel. Jump optimization

[PATCH v3 2/8] asm-generic/io.h: add io{read,write}64 accessors

This will allow device drivers to consistently use io{read,write}XX also for 64-bit accesses. Acked-by: Arnd Bergmann Signed-off-by: Horia Geantă --- include/asm-generic/io.h| 63 + include/asm-generic/iomap.h | 8 ++ 2 files changed, 71

[RFC PATCH v2 0/3] OPTPROBES for powerpc

Here are the RFC patchset of the kprobes jump optimization (a.k.a OPTPROBES)for powerpc. Kprobe being an inevitable tool for kernel developers,enhancing the performance of kprobe has got much importance. Currently kprobes inserts a trap instruction to probe a running kernel. Jump optimization

[RFC PATCH v2 2/3] arch/powerpc : optprobes for powerpc core

ppc_get_optinsn_slot() and ppc_free_optinsn_slot() are geared towards the allocation and freeing of memory from the area reserved for detour buffer. Signed-off-by: Anju T --- arch/powerpc/kernel/optprobes.c | 480 1 file

[PATCH v3 1/8] asm-generic/io.h: allow barriers in io{read,write}{16,32}be

While reviewing the addition of io{read,write}64be accessors, Arnd -finds a potential problem: "If an architecture overrides readq/writeq to have barriers but does not override ioread64be/iowrite64be, this will lack the barriers and behave differently from the little-endian version. I think the

[RFC PATCH v2 2/3] arch/powerpc : optprobes for powerpc core

ppc_get_optinsn_slot() and ppc_free_optinsn_slot() are geared towards the allocation and freeing of memory from the area reserved for detour buffer. Signed-off-by: Anju T --- arch/powerpc/kernel/optprobes.c | 480 1 file changed, 480 insertions(+)

[PATCH v3 1/8] asm-generic/io.h: allow barriers in io{read,write}{16,32}be

While reviewing the addition of io{read,write}64be accessors, Arnd -finds a potential problem: "If an architecture overrides readq/writeq to have barriers but does not override ioread64be/iowrite64be, this will lack the barriers and behave differently from the little-endian version. I think the

Re: [PATCH v12 07/13] task_isolation: add debug boot flag

(Resending in text/plain. I just screwed around with my Thunderbird config some more in hopes of getting it to pay attention to all the settings that say "use plain text for LKML", but, we'll see.) On 5/18/2016 1:06 PM, Peter Zijlstra wrote: On Wed, May 18, 2016 at 12:35:19PM -0400, Chris

Re: [PATCH v12 07/13] task_isolation: add debug boot flag

(Resending in text/plain. I just screwed around with my Thunderbird config some more in hopes of getting it to pay attention to all the settings that say "use plain text for LKML", but, we'll see.) On 5/18/2016 1:06 PM, Peter Zijlstra wrote: On Wed, May 18, 2016 at 12:35:19PM -0400, Chris

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