Re: [PATCH v4 01/29] bluetooth: Switch SMP to crypto_cipher_encrypt_one()

Hi Andy, > SMP does ECB crypto on stack buffers. This is complicated and > fragile, and it will not work if the stack is virtually allocated. > > Switch to the crypto_cipher interface, which is simpler and safer. > > Cc: Marcel Holtmann > Cc: Gustavo Padovan

Re: [PATCH v4 01/29] bluetooth: Switch SMP to crypto_cipher_encrypt_one()

Hi Andy, > SMP does ECB crypto on stack buffers. This is complicated and > fragile, and it will not work if the stack is virtually allocated. > > Switch to the crypto_cipher interface, which is simpler and safer. > > Cc: Marcel Holtmann > Cc: Gustavo Padovan > Cc: Johan Hedberg > Cc: "David

Re: [PATCH] cpufreq: dt: call of_node_put() before error out

On 27-06-16, 14:50, Masahiro Yamada wrote: > If of_match_node() fails, this init function bails out without > calling of_node_put(). > > I also changed of_node_put(of_root) to of_node_put(np); both of them > hold the same pointer, but it seems better to call of_node_put() > against the node

Re: [PATCH] cpufreq: dt: call of_node_put() before error out

On 27-06-16, 14:50, Masahiro Yamada wrote: > If of_match_node() fails, this init function bails out without > calling of_node_put(). > > I also changed of_node_put(of_root) to of_node_put(np); both of them > hold the same pointer, but it seems better to call of_node_put() > against the node

Re: [PATCH v2 3/4] iio: potentiometer: mcp4531: Add device tree binding

Hi Peter, Le 27. 06. 16 à 00:12, Peter Rosin a écrit : > Hi Florian, > > On 2016-06-26 22:22, Florian Vaussard wrote: >> This patch adds the necessary device tree binding to allow DT probing of >> currently supported parts. >> >> Signed-off-by: Florian Vaussard >>

Re: [PATCH v2 3/4] iio: potentiometer: mcp4531: Add device tree binding

Hi Peter, Le 27. 06. 16 à 00:12, Peter Rosin a écrit : > Hi Florian, > > On 2016-06-26 22:22, Florian Vaussard wrote: >> This patch adds the necessary device tree binding to allow DT probing of >> currently supported parts. >> >> Signed-off-by: Florian Vaussard >> --- >>

Re: [PATCH v2 2/4] iio: potentiometer: mcp4531: Add device tree binding documentation

Hello Peter, Le 26. 06. 16 à 23:38, Peter Rosin a écrit : > On 2016-06-26 22:22, Florian Vaussard wrote: >> Add the device tree documentation for all the supported parts. Apart the >> compatible string and standard I2C binding, no other binding is currently >> needed. >> >> Signed-off-by: Florian

Re: [PATCH 2/2] leds: Add driver for NCP5623 3-channel I2C LED driver

Hi Pavel, Le 26. 06. 16 à 23:49, Pavel Machek a écrit : > Hi! > >>> +struct ncp5623_led { >>> + bool active; >>> + unsigned int led_no; >>> + struct led_classdev ldev; >>> + struct work_struct work; >>> + struct ncp5623_priv *priv; >>> +}; >>> + >>> +struct ncp5623_priv { >>> +

Re: [PATCH v2 2/4] iio: potentiometer: mcp4531: Add device tree binding documentation

Hello Peter, Le 26. 06. 16 à 23:38, Peter Rosin a écrit : > On 2016-06-26 22:22, Florian Vaussard wrote: >> Add the device tree documentation for all the supported parts. Apart the >> compatible string and standard I2C binding, no other binding is currently >> needed. >> >> Signed-off-by: Florian

Re: [PATCH 2/2] leds: Add driver for NCP5623 3-channel I2C LED driver

Hi Pavel, Le 26. 06. 16 à 23:49, Pavel Machek a écrit : > Hi! > >>> +struct ncp5623_led { >>> + bool active; >>> + unsigned int led_no; >>> + struct led_classdev ldev; >>> + struct work_struct work; >>> + struct ncp5623_priv *priv; >>> +}; >>> + >>> +struct ncp5623_priv { >>> +

Re: [PATCH v6v3 02/12] mm: migrate: support non-lru movable page migration

On 06/16/2016 11:07 AM, Minchan Kim wrote: > On Thu, Jun 16, 2016 at 09:12:07AM +0530, Anshuman Khandual wrote: >> On 06/16/2016 05:56 AM, Minchan Kim wrote: >>> On Wed, Jun 15, 2016 at 12:15:04PM +0530, Anshuman Khandual wrote: On 06/15/2016 08:02 AM, Minchan Kim wrote: > Hi, > >

Re: [PATCH v6v3 02/12] mm: migrate: support non-lru movable page migration

On 06/16/2016 11:07 AM, Minchan Kim wrote: > On Thu, Jun 16, 2016 at 09:12:07AM +0530, Anshuman Khandual wrote: >> On 06/16/2016 05:56 AM, Minchan Kim wrote: >>> On Wed, Jun 15, 2016 at 12:15:04PM +0530, Anshuman Khandual wrote: On 06/15/2016 08:02 AM, Minchan Kim wrote: > Hi, > >

[PATCH] cpufreq: dt: call of_node_put() before error out

If of_match_node() fails, this init function bails out without calling of_node_put(). I also changed of_node_put(of_root) to of_node_put(np); both of them hold the same pointer, but it seems better to call of_node_put() against the node returned by of_find_node_by_path(). Signed-off-by: Masahiro

[PATCH] cpufreq: dt: call of_node_put() before error out

If of_match_node() fails, this init function bails out without calling of_node_put(). I also changed of_node_put(of_root) to of_node_put(np); both of them hold the same pointer, but it seems better to call of_node_put() against the node returned by of_find_node_by_path(). Signed-off-by: Masahiro

Re: [PATCH v3 0/9] reduce memory usage by page_owner

On Fri, Jun 24, 2016 at 04:19:35PM -0700, Andrew Morton wrote: > On Fri, 17 Jun 2016 16:57:30 +0900 js1...@gmail.com wrote: > > > There was a bug reported by Sasha and minor fixes is needed > > so I send v3. > > > > o fix a bg reported by Sasha (mm/compaction: split freepages > > without holding

Re: [PATCH v3 0/9] reduce memory usage by page_owner

On Fri, Jun 24, 2016 at 04:19:35PM -0700, Andrew Morton wrote: > On Fri, 17 Jun 2016 16:57:30 +0900 js1...@gmail.com wrote: > > > There was a bug reported by Sasha and minor fixes is needed > > so I send v3. > > > > o fix a bg reported by Sasha (mm/compaction: split freepages > > without holding

Re: [PATCH] ilp32: fix {GET,SET}SIGMASK request for ptrace

Hi Zhou, Thank you for the patch. The idea is ok, but patch format got broken for some reason. Could you re-send it? Yury. On Mon, Jun 27, 2016 at 12:49:05PM +0800, zhouchengming wrote: > atus: RO > Content-Length: 4732 > Lines: 181 > > The function compat_ptrace_request(used by ilp32) don't

Re: [PATCH] ilp32: fix {GET,SET}SIGMASK request for ptrace

Hi Zhou, Thank you for the patch. The idea is ok, but patch format got broken for some reason. Could you re-send it? Yury. On Mon, Jun 27, 2016 at 12:49:05PM +0800, zhouchengming wrote: > atus: RO > Content-Length: 4732 > Lines: 181 > > The function compat_ptrace_request(used by ilp32) don't

Re: undefined reference to `printk'

On Sun, 12 Jun 2016 13:38:10 +0900, Josh Triplett wrote: > > [Adding LKML, linux-arch, and Linus.] > > On Sun, Jun 12, 2016 at 10:17:01AM +0800, kbuild test robot wrote: > > All errors (new ones prefixed by >>): > > > >arch/m32r/kernel/built-in.o: In function `default_eit_handler': > > >>

Re: undefined reference to `printk'

On Sun, 12 Jun 2016 13:38:10 +0900, Josh Triplett wrote: > > [Adding LKML, linux-arch, and Linus.] > > On Sun, Jun 12, 2016 at 10:17:01AM +0800, kbuild test robot wrote: > > All errors (new ones prefixed by >>): > > > >arch/m32r/kernel/built-in.o: In function `default_eit_handler': > > >>

Re: [PATCH v3 2/2] phy: add a driver for the Rockchip SoC internal PCIe PHY

Hi, On Friday 24 June 2016 05:07 AM, Brian Norris wrote: > Hi, > > On Thu, Jun 23, 2016 at 10:30:17AM +0800, Shawn Lin wrote: >> 在 2016/6/20 14:36, Kishon Vijay Abraham I 写道: >>> On Monday 20 June 2016 06:28 AM, Shawn Lin wrote: On 2016/6/17 21:08, Kishon Vijay Abraham I wrote: > On

Re: [PATCH v3 2/2] phy: add a driver for the Rockchip SoC internal PCIe PHY

Hi, On Friday 24 June 2016 05:07 AM, Brian Norris wrote: > Hi, > > On Thu, Jun 23, 2016 at 10:30:17AM +0800, Shawn Lin wrote: >> 在 2016/6/20 14:36, Kishon Vijay Abraham I 写道: >>> On Monday 20 June 2016 06:28 AM, Shawn Lin wrote: On 2016/6/17 21:08, Kishon Vijay Abraham I wrote: > On

kthread_stop insanity (Re: [[DEBUG] force] 2642458962: BUG: unable to handle kernel paging request at ffffc90000997f18)

My v4 series was doing pretty well until this explosion: On Sun, Jun 26, 2016 at 9:41 PM, kernel test robot wrote: > > > FYI, we noticed the following commit: > > https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/vmap_stack > commit

kthread_stop insanity (Re: [[DEBUG] force] 2642458962: BUG: unable to handle kernel paging request at ffffc90000997f18)

My v4 series was doing pretty well until this explosion: On Sun, Jun 26, 2016 at 9:41 PM, kernel test robot wrote: > > > FYI, we noticed the following commit: > > https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/vmap_stack > commit 26424589626d7f82d09d4e7c0569f9487b2e810a

Re: [RFC v4 0/7] extcon: usb-gpio: fixes and improvements

On 06/26/2016 06:39 PM, Tobias Jakobi wrote: > Hello Krzysztof, > > just wanted to ask on which kernel branch the patchset is based on. At > least for me the set doesn't apply cleanly to 4.7-rc4. Hi, It was based on next-20160608. Best regards, Krzysztof

Re: [RFC v4 0/7] extcon: usb-gpio: fixes and improvements

On 06/26/2016 06:39 PM, Tobias Jakobi wrote: > Hello Krzysztof, > > just wanted to ask on which kernel branch the patchset is based on. At > least for me the set doesn't apply cleanly to 4.7-rc4. Hi, It was based on next-20160608. Best regards, Krzysztof

Re: undefined reference to `printk'

I think fix it. default_eit_handler rewritten in C, it is best way. But it test difficult. Signed-off-by: Yoshinori Sato --- arch/m32r/kernel/entry.S | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/m32r/kernel/entry.S b/arch/m32r/kernel/entry.S index

Re: undefined reference to `printk'

I think fix it. default_eit_handler rewritten in C, it is best way. But it test difficult. Signed-off-by: Yoshinori Sato --- arch/m32r/kernel/entry.S | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/m32r/kernel/entry.S b/arch/m32r/kernel/entry.S index c639bfa..a71105c 100644 ---

[PATCH net-next 6/6] r8152: add byte_enable for ocp_read_word function

Add byte_enable for ocp_read_word() to replace reading 4 bytes data with reading the desired 2 bytes data. This is used to avoid the issue which is described in commit:b4d99def. The origin method always reads 4 bytes data, and it may have problem when reading the PHY regiters. The new method is

[PATCH net-next 6/6] r8152: add byte_enable for ocp_read_word function

Add byte_enable for ocp_read_word() to replace reading 4 bytes data with reading the desired 2 bytes data. This is used to avoid the issue which is described in commit:b4d99def. The origin method always reads 4 bytes data, and it may have problem when reading the PHY regiters. The new method is

[PATCH net-next 1/6] r8152: add aldps_enable for rtl_ops

Add aldps_enable() for rtl_ops. Signed-off-by: Hayes Wang --- drivers/net/usb/r8152.c | 19 ++- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c index 11178f9..b253003 100644 ---

[PATCH net-next 1/6] r8152: add aldps_enable for rtl_ops

Add aldps_enable() for rtl_ops. Signed-off-by: Hayes Wang --- drivers/net/usb/r8152.c | 19 ++- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c index 11178f9..b253003 100644 --- a/drivers/net/usb/r8152.c +++

Re: [PATCH RFC 0/2] rtc-cmos: Workaround unwanted interrupt generation

On 21/06/2016:10:25:34 AM, Pratyush Anand wrote: > We have observed on few machines with rtc-cmos device that > hpet_rtc_interrupt() is called before cmos_do_probe() could call > hpet_rtc_timer_init(). It has not been observed during normal boot/reboot > of machines. It *sometime* happens when

Re: [PATCH RFC 0/2] rtc-cmos: Workaround unwanted interrupt generation

On 21/06/2016:10:25:34 AM, Pratyush Anand wrote: > We have observed on few machines with rtc-cmos device that > hpet_rtc_interrupt() is called before cmos_do_probe() could call > hpet_rtc_timer_init(). It has not been observed during normal boot/reboot > of machines. It *sometime* happens when

Re: linux-next: manual merge of the net-next tree with the net tree

On Mon, 2016-06-27 at 11:46 +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the net-next tree got a conflict in: > > net/sched/sch_netem.c > > between commit: > > 21de12ee5568 ("netem: fix a use after free") > > from the net tree and commit: > > 520ac30f4551

Re: linux-next: manual merge of the net-next tree with the net tree

On Mon, 2016-06-27 at 11:46 +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the net-next tree got a conflict in: > > net/sched/sch_netem.c > > between commit: > > 21de12ee5568 ("netem: fix a use after free") > > from the net tree and commit: > > 520ac30f4551

Re: [PATCH 18/21] usb: chipidea: msm: Add reset controller for PHY POR bit

Hi, [auto build test ERROR on peter.chen-usb/ci-for-usb-next] [also build test ERROR on v4.7-rc5 next-20160624] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 18/21] usb: chipidea: msm: Add reset controller for PHY POR bit

Hi, [auto build test ERROR on peter.chen-usb/ci-for-usb-next] [also build test ERROR on v4.7-rc5 next-20160624] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH] ilp32: fix {GET,SET}SIGMASK request for ptrace

The function compat_ptrace_request(used by ilp32) don't handle {GET,SET}SIGMASK request, so it will be handled by ptrace_request. But it's wrong because the compat_sigset_t of ilp32 differs from the sigset_t of aarch64. The patch fixes it. Signed-off-by: Zhou Chengming

[PATCH] ilp32: fix {GET,SET}SIGMASK request for ptrace

The function compat_ptrace_request(used by ilp32) don't handle {GET,SET}SIGMASK request, so it will be handled by ptrace_request. But it's wrong because the compat_sigset_t of ilp32 differs from the sigset_t of aarch64. The patch fixes it. Signed-off-by: Zhou Chengming ---

[PATCH] [perf]: update makefile message for installing required libs

From: Neeraj Badlani In case of missing library (libslang), give hint to install library (libslang2-dev) Since libslang-dev is not provided by Ubuntu's apt-package --- tools/perf/config/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] [perf]: update makefile message for installing required libs

From: Neeraj Badlani In case of missing library (libslang), give hint to install library (libslang2-dev) Since libslang-dev is not provided by Ubuntu's apt-package --- tools/perf/config/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/perf/config/Makefile

Re: [PATCH 12/19] arm64: ptrace: handle ptrace_request differently for aarch32 and ilp32

The {GET,SET}SIGMASK request of ptrace on ilp32 is wrong, it's handled by ptrace_request(like aarch64). So I write a patch to fix it(just for ilp32). I will send the patch next. Thanks! On 2016/6/18 7:54, Yury Norov wrote: Here new aarch32 ptrace syscall handler is introsuced to avoid run-time

Re: [PATCH 12/19] arm64: ptrace: handle ptrace_request differently for aarch32 and ilp32

The {GET,SET}SIGMASK request of ptrace on ilp32 is wrong, it's handled by ptrace_request(like aarch64). So I write a patch to fix it(just for ilp32). I will send the patch next. Thanks! On 2016/6/18 7:54, Yury Norov wrote: Here new aarch32 ptrace syscall handler is introsuced to avoid run-time

[[DEBUG] force] 2642458962: BUG: unable to handle kernel paging request at ffffc90000997f18

FYI, we noticed the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/vmap_stack commit 26424589626d7f82d09d4e7c0569f9487b2e810a ("[DEBUG] force-enable CONFIG_VMAP_STACK") on test machine: vm-intel12-yocto-x86_64: 2 threads qemu-system-x86_64 -enable-kvm

[[DEBUG] force] 2642458962: BUG: unable to handle kernel paging request at ffffc90000997f18

FYI, we noticed the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/vmap_stack commit 26424589626d7f82d09d4e7c0569f9487b2e810a ("[DEBUG] force-enable CONFIG_VMAP_STACK") on test machine: vm-intel12-yocto-x86_64: 2 threads qemu-system-x86_64 -enable-kvm

Re: [v3 PATCH 3/5] phy: Add USB Type-C PHY driver for rk3399

Hi Guenter On 06/27/2016 12:01 PM, Guenter Roeck wrote: On Sun, Jun 26, 2016 at 7:19 PM, Chris Zhong wrote: Hi Heiko On 06/25/2016 03:39 AM, Heiko Stuebner wrote: Am Donnerstag, 23. Juni 2016, 18:27:52 schrieb Kishon Vijay Abraham I: Hi, On Thursday 23 June 2016

Re: [v3 PATCH 3/5] phy: Add USB Type-C PHY driver for rk3399

Hi Guenter On 06/27/2016 12:01 PM, Guenter Roeck wrote: On Sun, Jun 26, 2016 at 7:19 PM, Chris Zhong wrote: Hi Heiko On 06/25/2016 03:39 AM, Heiko Stuebner wrote: Am Donnerstag, 23. Juni 2016, 18:27:52 schrieb Kishon Vijay Abraham I: Hi, On Thursday 23 June 2016 06:21 PM, Chris Zhong

Re: [PATCH] Decouple CFG and IO in Designware PCIe Driver

On Wed, Jun 22, 2016 at 1:54 PM, dongbo (E) wrote: > From: Dong Bo > > In designware PCIe driver, the iatu0 is used for both CFG and IO accesses. > When PCIe sends CFGs to peripherals (e.g. lspci), > iatu0 frequently switches between CFG and IO

Re: [PATCH] Decouple CFG and IO in Designware PCIe Driver

On Wed, Jun 22, 2016 at 1:54 PM, dongbo (E) wrote: > From: Dong Bo > > In designware PCIe driver, the iatu0 is used for both CFG and IO accesses. > When PCIe sends CFGs to peripherals (e.g. lspci), > iatu0 frequently switches between CFG and IO alternatively. > > If the LIMIT of MEMORY is a

[PATCH V5 1/2] cpufreq: Handle sorted frequency tables more efficiently

cpufreq drivers aren't required to provide a sorted frequency table today, and even the ones which provide a sorted table aren't handled efficiently by cpufreq core. This patch adds infrastructure to verify if the freq-table provided by the drivers is sorted or not, and use efficient helpers if

[PATCH V5 1/2] cpufreq: Handle sorted frequency tables more efficiently

cpufreq drivers aren't required to provide a sorted frequency table today, and even the ones which provide a sorted table aren't handled efficiently by cpufreq core. This patch adds infrastructure to verify if the freq-table provided by the drivers is sorted or not, and use efficient helpers if

[PATCH V5 2/2] cpufreq: Reuse new freq-table helpers

This patch migrates few users of cpufreq tables to the new helpers that work on sorted freq-tables. Signed-off-by: Viresh Kumar --- drivers/cpufreq/acpi-cpufreq.c | 14 -- drivers/cpufreq/amd_freq_sensitivity.c | 4 ++--

[PATCH V5 0/2] cpufreq: Sorted policy->freq_table

Hi Rafael, This series is aimed to make traversing of cpufreq table more efficient for platforms that already sort the frequency tables. The cpufreq core now checks if the freq table is sorted and applies a different set of helpers on such tables while traversing them. All the patches are pushed

[PATCH V5 2/2] cpufreq: Reuse new freq-table helpers

This patch migrates few users of cpufreq tables to the new helpers that work on sorted freq-tables. Signed-off-by: Viresh Kumar --- drivers/cpufreq/acpi-cpufreq.c | 14 -- drivers/cpufreq/amd_freq_sensitivity.c | 4 ++-- drivers/cpufreq/cpufreq_ondemand.c | 6 ++

[PATCH V5 0/2] cpufreq: Sorted policy->freq_table

Hi Rafael, This series is aimed to make traversing of cpufreq table more efficient for platforms that already sort the frequency tables. The cpufreq core now checks if the freq table is sorted and applies a different set of helpers on such tables while traversing them. All the patches are pushed

linux-next: manual merge of the kvm-ppc-paulus tree with the powerpc tree

Hi Paul, Today's linux-next merge of the kvm-ppc-paulus tree got a conflict in: arch/powerpc/kernel/traps.c between commit: 42f5b4cacd78 ("powerpc: Introduce asm-prototypes.h") from the powerpc tree and commit: fd7bacbca47a ("KVM: PPC: Book3S HV: Fix TB corruption in guest exit path on

linux-next: manual merge of the kvm-ppc-paulus tree with the powerpc tree

Hi Paul, Today's linux-next merge of the kvm-ppc-paulus tree got a conflict in: arch/powerpc/kernel/traps.c between commit: 42f5b4cacd78 ("powerpc: Introduce asm-prototypes.h") from the powerpc tree and commit: fd7bacbca47a ("KVM: PPC: Book3S HV: Fix TB corruption in guest exit path on

Re: [patch V3 00/22] timer: Refactor the timer wheel

On Fri, Jun 24, 2016 at 02:32:00PM -, Thomas Gleixner wrote: > This is the third version of the timer wheel rework series. The previous > versions can be found here: > > V1: http://lkml.kernel.org/r/20160613070440.950649...@linutronix.de > V2:

Re: [patch V3 00/22] timer: Refactor the timer wheel

On Fri, Jun 24, 2016 at 02:32:00PM -, Thomas Gleixner wrote: > This is the third version of the timer wheel rework series. The previous > versions can be found here: > > V1: http://lkml.kernel.org/r/20160613070440.950649...@linutronix.de > V2:

[PATCH v2] Bluetooth: btmrvl: fix slab-out-of-bounds access in btmrvl_sdio

Kasan reported slab-out-of-bounds access in btmrvl_sdio: [ 33.055400] == [ 33.062585] BUG: KASAN: slab-out-of-bounds in memcpy+0x24/0x50 at addr ffc0d89b4a00 [ 33.070529] Read of size 256 by task btmrvl_main_ser/3576 [

[PATCH v2] Bluetooth: btmrvl: fix slab-out-of-bounds access in btmrvl_sdio

Kasan reported slab-out-of-bounds access in btmrvl_sdio: [ 33.055400] == [ 33.062585] BUG: KASAN: slab-out-of-bounds in memcpy+0x24/0x50 at addr ffc0d89b4a00 [ 33.070529] Read of size 256 by task btmrvl_main_ser/3576 [

Re: Re: [PATCH] arm:swiotlb:keep disabled in default configuration

>> > >> > From: Rohit Thapliyal >> > >> > swiotlb implementation not required to be enabled in arm and >> > disabling it reduces uImage size by 16KB. >> > >> >> How so? There are no DMA operations on ARM? >Xen actively uses the swiotlb on ARM, see

Re: Re: [PATCH] arm:swiotlb:keep disabled in default configuration

>> > >> > From: Rohit Thapliyal >> > >> > swiotlb implementation not required to be enabled in arm and >> > disabling it reduces uImage size by 16KB. >> > >> >> How so? There are no DMA operations on ARM? >Xen actively uses the swiotlb on ARM, see

[PATCH] Bluetooth: btmrvl: fix slab-out-of-bounds access in btmrvl_sdio

Kasan reported slab-out-of-bounds access in btmrvl_sdio: [ 33.055400] == [ 33.062585] BUG: KASAN: slab-out-of-bounds in memcpy+0x24/0x50 at addr ffc0d89b4a00 [ 33.070529] Read of size 256 by task btmrvl_main_ser/3576 [

[PATCH] Bluetooth: btmrvl: fix slab-out-of-bounds access in btmrvl_sdio

Kasan reported slab-out-of-bounds access in btmrvl_sdio: [ 33.055400] == [ 33.062585] BUG: KASAN: slab-out-of-bounds in memcpy+0x24/0x50 at addr ffc0d89b4a00 [ 33.070529] Read of size 256 by task btmrvl_main_ser/3576 [

Re: [PATCH 02/21] usb: ulpi: Support device discovery via DT

Hi, [auto build test ERROR on peter.chen-usb/ci-for-usb-next] [also build test ERROR on v4.7-rc5 next-20160624] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 02/21] usb: ulpi: Support device discovery via DT

Hi, [auto build test ERROR on peter.chen-usb/ci-for-usb-next] [also build test ERROR on v4.7-rc5 next-20160624] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[x86] ddf4847e6f: BUG: unable to handle kernel paging request at ffffffff03862040

FYI, we noticed the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/vmap_stack commit ddf4847e6f114c522fefb24c16fc7a1d75138f9f ("x86: Move thread_info into task_struct") on test machine: vm-kbuild-yocto-x86_64: 1 threads qemu-system-x86_64 -enable-kvm

[x86] ddf4847e6f: BUG: unable to handle kernel paging request at ffffffff03862040

FYI, we noticed the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/vmap_stack commit ddf4847e6f114c522fefb24c16fc7a1d75138f9f ("x86: Move thread_info into task_struct") on test machine: vm-kbuild-yocto-x86_64: 1 threads qemu-system-x86_64 -enable-kvm

Re: [v3 PATCH 3/5] phy: Add USB Type-C PHY driver for rk3399

On Sun, Jun 26, 2016 at 7:19 PM, Chris Zhong wrote: > Hi Heiko > > > On 06/25/2016 03:39 AM, Heiko Stuebner wrote: >> >> Am Donnerstag, 23. Juni 2016, 18:27:52 schrieb Kishon Vijay Abraham I: >>> >>> Hi, >>> >>> On Thursday 23 June 2016 06:21 PM, Chris Zhong wrote:

Re: [v3 PATCH 3/5] phy: Add USB Type-C PHY driver for rk3399

On Sun, Jun 26, 2016 at 7:19 PM, Chris Zhong wrote: > Hi Heiko > > > On 06/25/2016 03:39 AM, Heiko Stuebner wrote: >> >> Am Donnerstag, 23. Juni 2016, 18:27:52 schrieb Kishon Vijay Abraham I: >>> >>> Hi, >>> >>> On Thursday 23 June 2016 06:21 PM, Chris Zhong wrote: Add a PHY provider

Re: [PATCH 2/2] mm: workingset: printk missing log level, use pr_info()

On Mon, 2016-06-27 at 09:01 +1000, Anton Blanchard wrote: > commit 612e44939c3c ("mm: workingset: eviction buckets for bigmem/lowbit > machines") added a printk without a log level. Quieten it by using > pr_info(). [] > diff --git a/mm/workingset.c b/mm/workingset.c [] > @@ -491,7 +491,7 @@ static

Re: [PATCH 2/2] mm: workingset: printk missing log level, use pr_info()

On Mon, 2016-06-27 at 09:01 +1000, Anton Blanchard wrote: > commit 612e44939c3c ("mm: workingset: eviction buckets for bigmem/lowbit > machines") added a printk without a log level. Quieten it by using > pr_info(). [] > diff --git a/mm/workingset.c b/mm/workingset.c [] > @@ -491,7 +491,7 @@ static

Re: [PATCH] m32r: fix build warning about putc

Hi, [auto build test WARNING on v4.7-rc5] [also build test WARNING on next-20160624] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] m32r: fix build warning about putc

Hi, [auto build test WARNING on v4.7-rc5] [also build test WARNING on next-20160624] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

linux-next: manual merge of the devicetree tree with the arm-soc tree

Hi Rob, Today's linux-next merge of the devicetree tree got a conflict in: arch/arm/mach-bcm/board_bcm21664.c between commit: 406c8f6c9954 ("ARM: bcm21664: Remove reset code") from the arm-soc tree and commit: 850bea2335e4 ("arm: Remove unnecessary of_platform_populate with default

linux-next: manual merge of the devicetree tree with the arm-soc tree

Hi Rob, Today's linux-next merge of the devicetree tree got a conflict in: arch/arm/mach-bcm/board_bcm21664.c between commit: 406c8f6c9954 ("ARM: bcm21664: Remove reset code") from the arm-soc tree and commit: 850bea2335e4 ("arm: Remove unnecessary of_platform_populate with default

Re: [PATCH 18/21] usb: chipidea: msm: Add reset controller for PHY POR bit

Hi, [auto build test ERROR on peter.chen-usb/ci-for-usb-next] [also build test ERROR on v4.7-rc5 next-20160624] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 18/21] usb: chipidea: msm: Add reset controller for PHY POR bit

Hi, [auto build test ERROR on peter.chen-usb/ci-for-usb-next] [also build test ERROR on v4.7-rc5 next-20160624] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2 2/2] namespaces: add transparent user namespaces

Hi Jann, Patches such as this really should CC linux-api@ (added). On Sat, Jun 25, 2016 at 2:23 AM, Jann Horn wrote: > This allows the admin of a user namespace to mark the namespace as > transparent. All other namespaces, by default, are opaque. > > While the current behavior

Re: [PATCH v2 2/2] namespaces: add transparent user namespaces

Hi Jann, Patches such as this really should CC linux-api@ (added). On Sat, Jun 25, 2016 at 2:23 AM, Jann Horn wrote: > This allows the admin of a user namespace to mark the namespace as > transparent. All other namespaces, by default, are opaque. > > While the current behavior of user

linux-next: manual merge of the jc_docs tree with the drm tree

Hi Jonathan, Today's linux-next merge of the jc_docs tree got a conflict in: Documentation/index.rst between commit: cb597fcea5c2 ("Documentation/gpu: add new gpu.rst converted from DocBook gpu.tmpl") from the drm tree and commit: 17defc282fe6 ("Documentation: add meta-documentation

linux-next: manual merge of the jc_docs tree with the drm tree

Hi Jonathan, Today's linux-next merge of the jc_docs tree got a conflict in: Documentation/index.rst between commit: cb597fcea5c2 ("Documentation/gpu: add new gpu.rst converted from DocBook gpu.tmpl") from the drm tree and commit: 17defc282fe6 ("Documentation: add meta-documentation

Re: [RESEND PATCH v11] mtd: spi-nor: add hisilicon spi-nor flash controller driver

Hi Brian, I haven't received more other comments for two weeks since I resent this patch except a compiling error. Could you help me merge this patch into the -next tree after I fix the compiling error? If so, I'll send out the new version as soon as possible. Thank you very much! Regards,

Re: [RESEND PATCH v11] mtd: spi-nor: add hisilicon spi-nor flash controller driver

Hi Brian, I haven't received more other comments for two weeks since I resent this patch except a compiling error. Could you help me merge this patch into the -next tree after I fix the compiling error? If so, I'll send out the new version as soon as possible. Thank you very much! Regards,

[PATCH v14 01/10] arm64: Add HAVE_REGS_AND_STACK_ACCESS_API feature

From: "David A. Long" Add HAVE_REGS_AND_STACK_ACCESS_API feature for arm64, including supporting functions and defines. Signed-off-by: David A. Long --- arch/arm64/Kconfig | 1 + arch/arm64/include/asm/ptrace.h | 52

[PATCH v14 01/10] arm64: Add HAVE_REGS_AND_STACK_ACCESS_API feature

From: "David A. Long" Add HAVE_REGS_AND_STACK_ACCESS_API feature for arm64, including supporting functions and defines. Signed-off-by: David A. Long --- arch/arm64/Kconfig | 1 + arch/arm64/include/asm/ptrace.h | 52 ++ arch/arm64/kernel/ptrace.c | 118

[PATCH v14 06/10] arm64: Treat all entry code as non-kprobe-able

From: Pratyush Anand Entry symbols are not kprobe safe. So blacklist them for kprobing. Signed-off-by: Pratyush Anand Signed-off-by: David A. Long Acked-by: Masami Hiramatsu --- arch/arm64/kernel/entry.S

[PATCH v14 05/10] arm64: Blacklist non-kprobe-able symbol

From: Pratyush Anand Add all function symbols which are called from do_debug_exception under NOKPROBE_SYMBOL, as they can not kprobed. Signed-off-by: Pratyush Anand --- arch/arm64/kernel/arm64ksyms.c | 2 ++ arch/arm64/kernel/debug-monitors.c | 17

[PATCH v14 06/10] arm64: Treat all entry code as non-kprobe-able

From: Pratyush Anand Entry symbols are not kprobe safe. So blacklist them for kprobing. Signed-off-by: Pratyush Anand Signed-off-by: David A. Long Acked-by: Masami Hiramatsu --- arch/arm64/kernel/entry.S | 3 +++ arch/arm64/kernel/kprobes/kprobes.c | 26 ++

[PATCH v14 05/10] arm64: Blacklist non-kprobe-able symbol

From: Pratyush Anand Add all function symbols which are called from do_debug_exception under NOKPROBE_SYMBOL, as they can not kprobed. Signed-off-by: Pratyush Anand --- arch/arm64/kernel/arm64ksyms.c | 2 ++ arch/arm64/kernel/debug-monitors.c | 17 +

[PATCH v14 02/10] arm64: Add more test functions to insn.c

From: "David A. Long" Certain instructions are hard to execute correctly out-of-line (as in kprobes). Test functions are added to insn.[hc] to identify these. The instructions include any that use PC-relative addressing, change the PC, or change interrupt masking. For

[PATCH v14 02/10] arm64: Add more test functions to insn.c

From: "David A. Long" Certain instructions are hard to execute correctly out-of-line (as in kprobes). Test functions are added to insn.[hc] to identify these. The instructions include any that use PC-relative addressing, change the PC, or change interrupt masking. For efficiency and simplicity

[PATCH v14 04/10] arm64: Kprobes with single stepping support

From: Sandeepa Prabhu Add support for basic kernel probes(kprobes) and jump probes (jprobes) for ARM64. Kprobes utilizes software breakpoint and single step debug exceptions supported on ARM v8. A software breakpoint is placed at the probe address to trap the

[PATCH v14 09/10] arm64: Add kernel return probes support (kretprobes)

From: Sandeepa Prabhu The pre-handler of this special 'trampoline' kprobe executes the return probe handler functions and restores original return address in ELR_EL1. This way the saved pt_regs still hold the original register context to be carried back to the probed

[PATCH v14 10/10] kprobes: Add arm64 case in kprobe example module

From: Sandeepa Prabhu Add info prints in sample kprobe handlers for ARM64 Signed-off-by: Sandeepa Prabhu Signed-off-by: David A. Long --- samples/kprobes/kprobe_example.c | 9 + 1 file changed, 9

[PATCH v14 04/10] arm64: Kprobes with single stepping support

From: Sandeepa Prabhu Add support for basic kernel probes(kprobes) and jump probes (jprobes) for ARM64. Kprobes utilizes software breakpoint and single step debug exceptions supported on ARM v8. A software breakpoint is placed at the probe address to trap the kernel execution into the kprobe

[PATCH v14 09/10] arm64: Add kernel return probes support (kretprobes)

From: Sandeepa Prabhu The pre-handler of this special 'trampoline' kprobe executes the return probe handler functions and restores original return address in ELR_EL1. This way the saved pt_regs still hold the original register context to be carried back to the probed kernel function.

[PATCH v14 10/10] kprobes: Add arm64 case in kprobe example module

From: Sandeepa Prabhu Add info prints in sample kprobe handlers for ARM64 Signed-off-by: Sandeepa Prabhu Signed-off-by: David A. Long --- samples/kprobes/kprobe_example.c | 9 + 1 file changed, 9 insertions(+) diff --git a/samples/kprobes/kprobe_example.c

  1   2   3   4   5   6   7   8   9   >