Re: [PATCH] crypto: ixp4xx - Use sg_virt()

From: Geliang Tang Date: Thu, 23 Mar 2017 21:16:30 +0800 > Use sg_virt() instead of open-coding it. > > Signed-off-by: Geliang Tang Acked-by: David S. Miller

Re: [PATCH] crypto: ixp4xx - Use sg_virt()

From: Geliang Tang Date: Thu, 23 Mar 2017 21:16:30 +0800 > Use sg_virt() instead of open-coding it. > > Signed-off-by: Geliang Tang Acked-by: David S. Miller

Re: [PATCH v3 1/3] kexec: Move vmcoreinfo out of the kernel's .bss section

Am Thu, 23 Mar 2017 17:23:53 +0800 schrieb Xunlei Pang : > On 03/23/2017 at 04:48 AM, Michael Holzheu wrote: > > Am Wed, 22 Mar 2017 12:30:04 +0800 > > schrieb Dave Young : > > > >> On 03/21/17 at 10:18pm, Eric W. Biederman wrote: > >>> Dave Young

Re: [PATCH v3 1/3] kexec: Move vmcoreinfo out of the kernel's .bss section

Am Thu, 23 Mar 2017 17:23:53 +0800 schrieb Xunlei Pang : > On 03/23/2017 at 04:48 AM, Michael Holzheu wrote: > > Am Wed, 22 Mar 2017 12:30:04 +0800 > > schrieb Dave Young : > > > >> On 03/21/17 at 10:18pm, Eric W. Biederman wrote: > >>> Dave Young writes: > >>> > > [snip] > > > I think

[PATCH V8 2/3] irq: Track the interrupt timings

The interrupt framework gives a lot of information about each interrupt. It does not keep track of when those interrupts occur though. This patch provides a mean to record the timestamp for each interrupt occurrences in a per-CPU circular buffer to help with the prediction of the next occurrence

[PATCH V8 2/3] irq: Track the interrupt timings

The interrupt framework gives a lot of information about each interrupt. It does not keep track of when those interrupts occur though. This patch provides a mean to record the timestamp for each interrupt occurrences in a per-CPU circular buffer to help with the prediction of the next occurrence

Re: RAID array is gone, please help

On Thu, Mar 23, 2017 at 05:49:05PM +0100, r...@mueller.org wrote: > I am hoping someone here will help me. Was reading this site... > > https://raid.wiki.kernel.org/index.php/Linux_Raid > > and it said to email this list if you've tried everything other than mdadm > --create. > > > I am

Re: RAID array is gone, please help

On Thu, Mar 23, 2017 at 05:49:05PM +0100, r...@mueller.org wrote: > I am hoping someone here will help me. Was reading this site... > > https://raid.wiki.kernel.org/index.php/Linux_Raid > > and it said to email this list if you've tried everything other than mdadm > --create. > > > I am

[PATCH V8 1/3] irq: Add flags to request_percpu_irq function

In the next changes, we track the interrupts but we discard the timers as that does not make sense. The next interrupt on a timer is predictable. But, the API request_percpu_irq does not allow to pass a flag, hence specifying if the interrupt type is a timer. Solve this by passing a 'flags'

[PATCH V8 3/3] irq: Compute the periodic interval for interrupts

An interrupt behaves with a burst of activity with periodic interval of time followed by one or two peaks of longer interval. As the time intervals are periodic, statistically speaking they follow a normal distribution and each interrupts can be tracked individually. This patch does statistics

[PATCH V8 3/3] irq: Compute the periodic interval for interrupts

An interrupt behaves with a burst of activity with periodic interval of time followed by one or two peaks of longer interval. As the time intervals are periodic, statistically speaking they follow a normal distribution and each interrupts can be tracked individually. This patch does statistics

[PATCH V8 1/3] irq: Add flags to request_percpu_irq function

In the next changes, we track the interrupts but we discard the timers as that does not make sense. The next interrupt on a timer is predictable. But, the API request_percpu_irq does not allow to pass a flag, hence specifying if the interrupt type is a timer. Solve this by passing a 'flags'

Re: [PATCH v12 6/9] mmc: cavium: Add MMC PCI driver for ThunderX SOCs

On 03/23/2017 02:28 AM, Ulf Hansson wrote: On 23 March 2017 at 09:58, Jan Glauber wrote: On Fri, Mar 17, 2017 at 03:58:26PM +0100, Ulf Hansson wrote: On 10 March 2017 at 14:25, Jan Glauber wrote: Add a platform driver for ThunderX ARM

Re: [PATCH v12 6/9] mmc: cavium: Add MMC PCI driver for ThunderX SOCs

On 03/23/2017 02:28 AM, Ulf Hansson wrote: On 23 March 2017 at 09:58, Jan Glauber wrote: On Fri, Mar 17, 2017 at 03:58:26PM +0100, Ulf Hansson wrote: On 10 March 2017 at 14:25, Jan Glauber wrote: Add a platform driver for ThunderX ARM SOCs. Signed-off-by: Jan Glauber ---

Re: [PATCH v5 1/6] mtd: spi-nor: introduce more SPI protocols and the Dual Transfer Mode

On 03/23/2017 12:33 AM, Cyrille Pitchen wrote: > This patch changes the prototype of spi_nor_scan(): its 3rd parameter > is replaced by a 'struct spi_nor_hwcaps' pointer, which tells the spi-nor > framework about the actual hardware capabilities supported by the SPI > controller and its driver. >

Re: [PATCH v5 1/6] mtd: spi-nor: introduce more SPI protocols and the Dual Transfer Mode

On 03/23/2017 12:33 AM, Cyrille Pitchen wrote: > This patch changes the prototype of spi_nor_scan(): its 3rd parameter > is replaced by a 'struct spi_nor_hwcaps' pointer, which tells the spi-nor > framework about the actual hardware capabilities supported by the SPI > controller and its driver. >

Re: [PATCH 00/13] Add HD44780 Character LCD support

Hi Geert, On Mon, Feb 06, 2017 at 03:38:02PM +0100, Geert Uytterhoeven wrote: > Hi all, > > Character LCDs are currently typically driven from userspace, either > directly through bit-banging, or via some kind of serial (UART/i2c) > interface. > > This patch series adds kernel support for

Re: [PATCH 00/13] Add HD44780 Character LCD support

Hi Geert, On Mon, Feb 06, 2017 at 03:38:02PM +0100, Geert Uytterhoeven wrote: > Hi all, > > Character LCDs are currently typically driven from userspace, either > directly through bit-banging, or via some kind of serial (UART/i2c) > interface. > > This patch series adds kernel support for

Re: [PATCH] arc: vdk: Fix support of UIO

+CC Jos ! -Vineet On 03/23/2017 10:34 AM, Alexey Brodkin wrote: > MotherBoard section has its "ranges" set to 0xE000_-0xF000_. > But UIO node maps 4 different areas in different memory locations > and all outside MB's ranges. > > That obviously breaks UIO mappings in runtime. > >

Re: [PATCH] arc: vdk: Fix support of UIO

+CC Jos ! -Vineet On 03/23/2017 10:34 AM, Alexey Brodkin wrote: > MotherBoard section has its "ranges" set to 0xE000_-0xF000_. > But UIO node maps 4 different areas in different memory locations > and all outside MB's ranges. > > That obviously breaks UIO mappings in runtime. > >

Re: [PATCH 00/13] Add HD44780 Character LCD support

Hi again, On Thu, Mar 23, 2017 at 06:15:01PM +0100, Willy TARREAU wrote: > So I finally had the time to give it a try by applying your patchset > on top of our 4.9 prod kernel. For now I'm getting a panic at boot : > > BUG: unable to handle kernel NULL pointer dereference at (null) >

Re: [PATCH 00/13] Add HD44780 Character LCD support

Hi again, On Thu, Mar 23, 2017 at 06:15:01PM +0100, Willy TARREAU wrote: > So I finally had the time to give it a try by applying your patchset > on top of our 4.9 prod kernel. For now I'm getting a panic at boot : > > BUG: unable to handle kernel NULL pointer dereference at (null) >

[PATCH] Input: synaptics - do not mix logical and bitwise operations

Let's stop using !!x to reduce value of trackstick button expression to 0/1 and use shift instead. This removes the following sparse warning: CHECK drivers/input/mouse/synaptics.c drivers/input/mouse/synaptics.c:943:79: warning: dubious: !x | y Also, the bits we are testing are not

[PATCH] Input: synaptics - do not mix logical and bitwise operations

Let's stop using !!x to reduce value of trackstick button expression to 0/1 and use shift instead. This removes the following sparse warning: CHECK drivers/input/mouse/synaptics.c drivers/input/mouse/synaptics.c:943:79: warning: dubious: !x | y Also, the bits we are testing are not

[PATCH] arc: vdk: Fix support of UIO

MotherBoard section has its "ranges" set to 0xE000_-0xF000_. But UIO node maps 4 different areas in different memory locations and all outside MB's ranges. That obviously breaks UIO mappings in runtime. Signed-off-by: Alexey Brodkin Cc: Vineet Gupta

[PATCH] arc: vdk: Fix support of UIO

MotherBoard section has its "ranges" set to 0xE000_-0xF000_. But UIO node maps 4 different areas in different memory locations and all outside MB's ranges. That obviously breaks UIO mappings in runtime. Signed-off-by: Alexey Brodkin Cc: Vineet Gupta Cc: Ruud Derwig Cc:

[PATCH] MAINTAINERS: separate out kernfs maintainership

Separate out kernfs from driver core and add myself as a co-maintainer. Signed-off-by: Tejun Heo --- Hello, Greg. So that I get cc'd on kernfs changes. Should have done this earlier. Thanks! MAINTAINERS | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-)

[PATCH] MAINTAINERS: separate out kernfs maintainership

Separate out kernfs from driver core and add myself as a co-maintainer. Signed-off-by: Tejun Heo --- Hello, Greg. So that I get cc'd on kernfs changes. Should have done this earlier. Thanks! MAINTAINERS | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git

Re: [PATCH] selinux: Remove unnecessary check of array base in selinux_set_mapping()

On Thu, Mar 23, 2017 at 5:08 AM, Paul Moore wrote: > On Wed, Mar 22, 2017 at 8:28 PM, Grant Grundler wrote: >> Ping? Any feedback on this patch? > > It's on my list of patches to review, patience please. No problem! Thank you! just wanted

Re: [PATCH] selinux: Remove unnecessary check of array base in selinux_set_mapping()

On Thu, Mar 23, 2017 at 5:08 AM, Paul Moore wrote: > On Wed, Mar 22, 2017 at 8:28 PM, Grant Grundler wrote: >> Ping? Any feedback on this patch? > > It's on my list of patches to review, patience please. No problem! Thank you! just wanted confirmation it wasn't overlooked. cheers, grant > >>

Re: [PATCH v2] KVM: kvm_io_bus_unregister_dev() should never fail

On Thu, 23 Mar 2017 18:24:19 +0100 David Hildenbrand wrote: > No caller currently checks the return value of > kvm_io_bus_unregister_dev(). This is evil, as all callers silently go on > freeing their device. A stale reference will remain in the io_bus, > getting at least used

Re: [PATCH v2] KVM: kvm_io_bus_unregister_dev() should never fail

On Thu, 23 Mar 2017 18:24:19 +0100 David Hildenbrand wrote: > No caller currently checks the return value of > kvm_io_bus_unregister_dev(). This is evil, as all callers silently go on > freeing their device. A stale reference will remain in the io_bus, > getting at least used again, when the

Re: [PATCH v2 06/18] arm64: arch_timer: Add infrastructure for multiple erratum detection methods

On Wed, Mar 22, 2017 at 03:59:21PM +, Marc Zyngier wrote: > [Sorry, sent too quickly] > > On 22/03/17 15:41, Daniel Lezcano wrote: > > On Mon, Mar 20, 2017 at 05:48:17PM +, Marc Zyngier wrote: > >> We're currently stuck with DT when it comes to handling errata, which > >> is pretty

Re: [PATCH v2 06/18] arm64: arch_timer: Add infrastructure for multiple erratum detection methods

On Wed, Mar 22, 2017 at 03:59:21PM +, Marc Zyngier wrote: > [Sorry, sent too quickly] > > On 22/03/17 15:41, Daniel Lezcano wrote: > > On Mon, Mar 20, 2017 at 05:48:17PM +, Marc Zyngier wrote: > >> We're currently stuck with DT when it comes to handling errata, which > >> is pretty

Re: [PATCH v3 5/5] ARM: configs: Add watchdog support in STM32 defconfig

Hi, On 03/22/2017 04:04 PM, Yannick Fertre wrote: This patch adds STM32 watchdog support in stm32_defconfig file Signed-off-by: Yannick Fertre --- Update commit header please (ARM: configs: stm32: Add watchdog support) arch/arm/configs/stm32_defconfig | 1 + 1 file

Re: [PATCH v3 5/5] ARM: configs: Add watchdog support in STM32 defconfig

Hi, On 03/22/2017 04:04 PM, Yannick Fertre wrote: This patch adds STM32 watchdog support in stm32_defconfig file Signed-off-by: Yannick Fertre --- Update commit header please (ARM: configs: stm32: Add watchdog support) arch/arm/configs/stm32_defconfig | 1 + 1 file changed, 1

Re: [PATCH 3/4] RAS: Add a Corrected Errors Collector

On Thu, Mar 23, 2017 at 10:20:31AM -0700, Luck, Tony wrote: > It can happen if Linux didn't actually take the page offline > (because it was a kernel page). The CEC code only knows that > it queued this page to be taken offline ... and has no way > to know if that succeeded or not. Right, that's

Re: [PATCH 3/4] RAS: Add a Corrected Errors Collector

On Thu, Mar 23, 2017 at 10:20:31AM -0700, Luck, Tony wrote: > It can happen if Linux didn't actually take the page offline > (because it was a kernel page). The CEC code only knows that > it queued this page to be taken offline ... and has no way > to know if that succeeded or not. Right, that's

Re: mm: BUG in resv_map_release

On 03/23/2017 03:19 AM, Dmitry Vyukov wrote: > Hello, > > I've got the following BUG while running syzkaller fuzzer. > Note the injected kmalloc failure, most likely it's the root cause. Thanks Dmitry, The BUG indicates someone called region_chg() in the process of adding a hugetlbfs page

Re: mm: BUG in resv_map_release

On 03/23/2017 03:19 AM, Dmitry Vyukov wrote: > Hello, > > I've got the following BUG while running syzkaller fuzzer. > Note the injected kmalloc failure, most likely it's the root cause. Thanks Dmitry, The BUG indicates someone called region_chg() in the process of adding a hugetlbfs page

[PATCH v5 2/4] x86/syscalls: Specific usage of verify_pre_usermode_state

Implement specific usage of verify_pre_usermode_state for user-mode returns for x86. --- Based on next-20170322 --- arch/x86/Kconfig| 1 + arch/x86/entry/common.c | 3 +++ arch/x86/entry/entry_64.S | 8

[PATCH v5 2/4] x86/syscalls: Specific usage of verify_pre_usermode_state

Implement specific usage of verify_pre_usermode_state for user-mode returns for x86. --- Based on next-20170322 --- arch/x86/Kconfig| 1 + arch/x86/entry/common.c | 3 +++ arch/x86/entry/entry_64.S | 8

[PATCH v5 1/4] syscalls: Restore address limit after a syscall

This patch ensures a syscall does not return to user-mode with a kernel address limit. If that happened, a process can corrupt kernel-mode memory and elevate privileges. For example, it would mitigation this bug: - https://bugs.chromium.org/p/project-zero/issues/detail?id=990 The

[PATCH v5 1/4] syscalls: Restore address limit after a syscall

This patch ensures a syscall does not return to user-mode with a kernel address limit. If that happened, a process can corrupt kernel-mode memory and elevate privileges. For example, it would mitigation this bug: - https://bugs.chromium.org/p/project-zero/issues/detail?id=990 The

[PATCH v5 3/4] arm/syscalls: Specific usage of verify_pre_usermode_state

Implement specific usage of verify_pre_usermode_state for user-mode returns for arm. --- Based on next-20170322 --- arch/arm/Kconfig | 1 + arch/arm/kernel/entry-common.S | 16 +++- 2 files changed, 16 insertions(+), 1 deletion(-) diff --git a/arch/arm/Kconfig

[PATCH v5 3/4] arm/syscalls: Specific usage of verify_pre_usermode_state

Implement specific usage of verify_pre_usermode_state for user-mode returns for arm. --- Based on next-20170322 --- arch/arm/Kconfig | 1 + arch/arm/kernel/entry-common.S | 16 +++- 2 files changed, 16 insertions(+), 1 deletion(-) diff --git a/arch/arm/Kconfig

[PATCH v5 4/4] arm64/syscalls: Specific usage of verify_pre_usermode_state

Implement specific usage of verify_pre_usermode_state for user-mode returns for arm64. --- Based on next-20170322 --- arch/arm64/Kconfig| 1 + arch/arm64/kernel/entry.S | 15 +++ 2 files changed, 16 insertions(+) diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index

[PATCH v5 4/4] arm64/syscalls: Specific usage of verify_pre_usermode_state

Implement specific usage of verify_pre_usermode_state for user-mode returns for arm64. --- Based on next-20170322 --- arch/arm64/Kconfig| 1 + arch/arm64/kernel/entry.S | 15 +++ 2 files changed, 16 insertions(+) diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index

[PATCH v2] KVM: kvm_io_bus_unregister_dev() should never fail

No caller currently checks the return value of kvm_io_bus_unregister_dev(). This is evil, as all callers silently go on freeing their device. A stale reference will remain in the io_bus, getting at least used again, when the iobus gets teared down on kvm_destroy_vm() - leading to use after free

[PATCH v2] KVM: kvm_io_bus_unregister_dev() should never fail

No caller currently checks the return value of kvm_io_bus_unregister_dev(). This is evil, as all callers silently go on freeing their device. A stale reference will remain in the io_bus, getting at least used again, when the iobus gets teared down on kvm_destroy_vm() - leading to use after free

Re: [PATCH 3/4] RAS: Add a Corrected Errors Collector

On Thu, Mar 23, 2017 at 04:22:28PM +0100, Borislav Petkov wrote: > On Wed, Mar 22, 2017 at 07:03:39PM +0100, Borislav Petkov wrote: > > Lemme try to write a small script exercising exactly that scenario to > > see whether I'm actually not talking crap here :-) > > Ok, here's a snapshot from the

Re: [PATCH 3/4] RAS: Add a Corrected Errors Collector

On Thu, Mar 23, 2017 at 04:22:28PM +0100, Borislav Petkov wrote: > On Wed, Mar 22, 2017 at 07:03:39PM +0100, Borislav Petkov wrote: > > Lemme try to write a small script exercising exactly that scenario to > > see whether I'm actually not talking crap here :-) > > Ok, here's a snapshot from the

Re: [PATCH 12/13] powerpc/perf: Thread imc cpuhotplug support

Hi Maddy, Anju, On Thu, Mar 16, 2017 at 01:05:06PM +0530, Madhavan Srinivasan wrote: > From: Anju T Sudhakar > > This patch adds support for thread IMC on cpuhotplug. > > When a cpu goes offline, the LDBAR for that cpu is disabled, and when it comes > back online the

Re: [PATCH 12/13] powerpc/perf: Thread imc cpuhotplug support

Hi Maddy, Anju, On Thu, Mar 16, 2017 at 01:05:06PM +0530, Madhavan Srinivasan wrote: > From: Anju T Sudhakar > > This patch adds support for thread IMC on cpuhotplug. > > When a cpu goes offline, the LDBAR for that cpu is disabled, and when it comes > back online the previous ldbar value is

Re: [PATCH v1] KVM: kvm_io_bus_unregister_dev() should never fail

> > Either that, or an early exit for bus == NULL in kvm_io_bus_destroy(). > (I think the second option is more straightforward.) I prefer to have the checks where kvm->buses[x] is actually accessed. So the chance of missing yet another check is easier to verify. Will send out v2 in a couple

Re: [REGRESSION] 07ec51480b5e ("virtio_pci: use shared interrupts for virtqueues") causes crashes in guest

On 23.03.2017 17:41, Michael S. Tsirkin wrote: > On Thu, Mar 23, 2017 at 03:19:07PM +, Richard W.M. Jones wrote: >> On Thu, Mar 23, 2017 at 01:13:50PM +0800, Jason Wang wrote: >>> >From 312859b596e83a2164a8430343d31fce2a5ad808 Mon Sep 17 00:00:00 2001 >>> From: Jason Wang

Re: [PATCH v1] KVM: kvm_io_bus_unregister_dev() should never fail

> > Either that, or an early exit for bus == NULL in kvm_io_bus_destroy(). > (I think the second option is more straightforward.) I prefer to have the checks where kvm->buses[x] is actually accessed. So the chance of missing yet another check is easier to verify. Will send out v2 in a couple

Re: [REGRESSION] 07ec51480b5e ("virtio_pci: use shared interrupts for virtqueues") causes crashes in guest

On 23.03.2017 17:41, Michael S. Tsirkin wrote: > On Thu, Mar 23, 2017 at 03:19:07PM +, Richard W.M. Jones wrote: >> On Thu, Mar 23, 2017 at 01:13:50PM +0800, Jason Wang wrote: >>> >From 312859b596e83a2164a8430343d31fce2a5ad808 Mon Sep 17 00:00:00 2001 >>> From: Jason Wang >>> Date: Thu, 23

Re: Dell Inspiron 5558/0VNM2T hangs at resume from suspend when USB 3 is enabled

On Thu, Mar 23, 2017 at 2:02 PM, Mathias Nyman wrote: > On 22.03.2017 19:51, Mathias Nyman wrote: >> >> On 22.03.2017 00:52, Diego Viola wrote: >>> >>> On Tue, Mar 21, 2017 at 12:29 PM, Diego Viola >>> wrote: On Tue, Mar 21, 2017 at

Re: Dell Inspiron 5558/0VNM2T hangs at resume from suspend when USB 3 is enabled

On Thu, Mar 23, 2017 at 2:02 PM, Mathias Nyman wrote: > On 22.03.2017 19:51, Mathias Nyman wrote: >> >> On 22.03.2017 00:52, Diego Viola wrote: >>> >>> On Tue, Mar 21, 2017 at 12:29 PM, Diego Viola >>> wrote: On Tue, Mar 21, 2017 at 10:04 AM, Diego Viola wrote: > > On

Re: [PATCH 0/2] serial: Add name field to uart_port

On Thu, Mar 23, 2017 at 2:22 PM, Vignesh R wrote: > On Thursday 23 March 2017 12:16 AM, Andy Shevchenko wrote: >> On Tue, Mar 21, 2017 at 3:36 PM, Vignesh R wrote: >>> This series adds name attribute to uart_port struct inorder to store >>> name of the tty port

Re: [PATCH 0/2] serial: Add name field to uart_port

On Thu, Mar 23, 2017 at 2:22 PM, Vignesh R wrote: > On Thursday 23 March 2017 12:16 AM, Andy Shevchenko wrote: >> On Tue, Mar 21, 2017 at 3:36 PM, Vignesh R wrote: >>> This series adds name attribute to uart_port struct inorder to store >>> name of the tty port that will help in identify

Re: [RFC PATCH v0.2] PCI: Add support for tango PCIe host bridge

On 23/03/2017 15:22, Marc Zyngier wrote: > On 23/03/17 13:05, Mason wrote: > >> +#define MSI_COUNT 32 > > Is this something that is hardcoded? Unlikely to ever change? The host bridge actually supports 256 MSIs. IIUC, what you suggested on IRC is that I support 256 in the driver, and only

Re: [RFC PATCH v0.2] PCI: Add support for tango PCIe host bridge

On 23/03/2017 15:22, Marc Zyngier wrote: > On 23/03/17 13:05, Mason wrote: > >> +#define MSI_COUNT 32 > > Is this something that is hardcoded? Unlikely to ever change? The host bridge actually supports 256 MSIs. IIUC, what you suggested on IRC is that I support 256 in the driver, and only

Re: [PATCH V13 04/10] arm64: exception: handle Synchronous External Abort

On Tue, Mar 21, 2017 at 04:46:59PM -0600, Tyler Baicar wrote: > SEA exceptions are often caused by an uncorrected hardware > error, and are handled when data abort and instruction abort > exception classes have specific values for their Fault Status > Code. > When SEA occurs, before killing the

Re: [PATCH V13 04/10] arm64: exception: handle Synchronous External Abort

On Tue, Mar 21, 2017 at 04:46:59PM -0600, Tyler Baicar wrote: > SEA exceptions are often caused by an uncorrected hardware > error, and are handled when data abort and instruction abort > exception classes have specific values for their Fault Status > Code. > When SEA occurs, before killing the

Re: Dell Inspiron 5558/0VNM2T hangs at resume from suspend when USB 3 is enabled

On 22.03.2017 19:51, Mathias Nyman wrote: On 22.03.2017 00:52, Diego Viola wrote: On Tue, Mar 21, 2017 at 12:29 PM, Diego Viola wrote: On Tue, Mar 21, 2017 at 10:04 AM, Diego Viola wrote: On Mon, Mar 20, 2017 at 8:15 PM, Diego Viola

Re: Dell Inspiron 5558/0VNM2T hangs at resume from suspend when USB 3 is enabled

On 22.03.2017 19:51, Mathias Nyman wrote: On 22.03.2017 00:52, Diego Viola wrote: On Tue, Mar 21, 2017 at 12:29 PM, Diego Viola wrote: On Tue, Mar 21, 2017 at 10:04 AM, Diego Viola wrote: On Mon, Mar 20, 2017 at 8:15 PM, Diego Viola wrote: On Mon, Mar 20, 2017 at 3:27 PM, Diego Viola

ATM Department Center for urgent delivery

Your ATM CARD of USD2.800,000 : 00USD.is with us with registration code of (Shipment Code 11684990) contact us with your delivery information such as, Your Name, Your Address and Your Telephone Number, Your passport or ID card. Contact Email:(simnico...@gmail.com) Finally, be informed that we

ATM Department Center for urgent delivery

Your ATM CARD of USD2.800,000 : 00USD.is with us with registration code of (Shipment Code 11684990) contact us with your delivery information such as, Your Name, Your Address and Your Telephone Number, Your passport or ID card. Contact Email:(simnico...@gmail.com) Finally, be informed that we

Re: [BUG] 4.11.0-rc3 xterm hung in D state on exit, wchan is tty_release_struct

On Thu, Mar 23, 2017 at 08:46:03AM -0500, Rob Herring wrote: > On Thu, Mar 23, 2017 at 12:30:18AM -0700, l...@pengaru.com wrote: > > On Wed, Mar 22, 2017 at 11:44:18PM -0700, l...@pengaru.com wrote: > > > On Wed, Mar 22, 2017 at 07:08:46PM -0700, l...@pengaru.com wrote: > > > > Hello list, > > > >

Re: [PATCH v2 2/2] iio: Aspeed AST2400/AST2500 ADC

On Thu, Mar 23, 2017 at 12:52 AM, Quentin Schulz wrote: > Hi, > > On 22/03/2017 21:46, Rick Altherr wrote: >> On Wed, Mar 22, 2017 at 12:21 AM, Quentin Schulz >> wrote: >>> Hi, >>> >>> On 21/03/2017 21:48, Rick Altherr wrote:

Re: [PATCH v2 2/2] iio: Aspeed AST2400/AST2500 ADC

Restoring the list after an accidental direct reply. On Wed, Mar 22, 2017 at 2:32 PM, Rick Altherr wrote: > On Wed, Mar 22, 2017 at 2:47 AM, Joel Stanley wrote: >> On Wed, Mar 22, 2017 at 7:18 AM, Rick Altherr wrote: >>> Aspeed

Re: [BUG] 4.11.0-rc3 xterm hung in D state on exit, wchan is tty_release_struct

On Thu, Mar 23, 2017 at 08:46:03AM -0500, Rob Herring wrote: > On Thu, Mar 23, 2017 at 12:30:18AM -0700, l...@pengaru.com wrote: > > On Wed, Mar 22, 2017 at 11:44:18PM -0700, l...@pengaru.com wrote: > > > On Wed, Mar 22, 2017 at 07:08:46PM -0700, l...@pengaru.com wrote: > > > > Hello list, > > > >

Re: [PATCH v2 2/2] iio: Aspeed AST2400/AST2500 ADC

On Thu, Mar 23, 2017 at 12:52 AM, Quentin Schulz wrote: > Hi, > > On 22/03/2017 21:46, Rick Altherr wrote: >> On Wed, Mar 22, 2017 at 12:21 AM, Quentin Schulz >> wrote: >>> Hi, >>> >>> On 21/03/2017 21:48, Rick Altherr wrote: Aspeed AST2400/AST2500 BMC SoCs include a 16 channel, 10-bit ADC.

Re: [PATCH v2 2/2] iio: Aspeed AST2400/AST2500 ADC

Restoring the list after an accidental direct reply. On Wed, Mar 22, 2017 at 2:32 PM, Rick Altherr wrote: > On Wed, Mar 22, 2017 at 2:47 AM, Joel Stanley wrote: >> On Wed, Mar 22, 2017 at 7:18 AM, Rick Altherr wrote: >>> Aspeed AST2400/AST2500 BMC SoCs include a 16 channel, 10-bit ADC. Low >>>

RAID array is gone, please help

I am hoping someone here will help me. Was reading this site... https://raid.wiki.kernel.org/index.php/Linux_Raid and it said to email this list if you've tried everything other than mdadm --create. I am running Ubuntu 16.04. Machine name is fred. I used webmin to create a 4 disk RAID10

RAID array is gone, please help

I am hoping someone here will help me. Was reading this site... https://raid.wiki.kernel.org/index.php/Linux_Raid and it said to email this list if you've tried everything other than mdadm --create. I am running Ubuntu 16.04. Machine name is fred. I used webmin to create a 4 disk RAID10

[PATCH 0/8] pinctrl: meson: add audio output pins

This patchset adds the pinctrl definition and the related device-tree bindings of the i2s output and spdif output pins on the meson gxbb and gxl SoCs. This is part of the ongoing work to bring audio output suppot on the meson family. It was tested on the gxbb p200 and gxl p230. Jerome Brunet

[PATCH 0/8] pinctrl: meson: add audio output pins

This patchset adds the pinctrl definition and the related device-tree bindings of the i2s output and spdif output pins on the meson gxbb and gxl SoCs. This is part of the ongoing work to bring audio output suppot on the meson family. It was tested on the gxbb p200 and gxl p230. Jerome Brunet

Re: [PATCH v2 2/2] iio: Aspeed AST2400/AST2500 ADC

Restoring the list after an accidental direct reply. On Wed, Mar 22, 2017 at 1:30 PM, Rick Altherr wrote: > On Tue, Mar 21, 2017 at 2:14 PM, Peter Meerwald-Stadler > wrote: >> >>> Aspeed AST2400/AST2500 BMC SoCs include a 16 channel, 10-bit ADC. Low >>>

Re: [PATCH v2 2/2] iio: Aspeed AST2400/AST2500 ADC

Restoring the list after an accidental direct reply. On Wed, Mar 22, 2017 at 1:30 PM, Rick Altherr wrote: > On Tue, Mar 21, 2017 at 2:14 PM, Peter Meerwald-Stadler > wrote: >> >>> Aspeed AST2400/AST2500 BMC SoCs include a 16 channel, 10-bit ADC. Low >>> and high threshold interrupts are

Re: run_timer_softirq gpf. [smc]

> > From: Thomas Gleixner > To: Dave Jones > Cc: Linux Kernel , Steven Rostedt > , Ursula Braun , > net...@vger.kernel.org > Date: 21.03.2017 22:46 >

Re: run_timer_softirq gpf. [smc]

> > From: Thomas Gleixner > To: Dave Jones > Cc: Linux Kernel , Steven Rostedt > , Ursula Braun , > net...@vger.kernel.org > Date: 21.03.2017 22:46 > Subject:Re: run_timer_softirq gpf. [smc] > Sent by:netdev-ow...@vger.kernel.org > > > > On Tue, 21 Mar 2017,

[PATCH 8/8] ARM64: dts: meson-gxl: add spdif output pins

Signed-off-by: Jerome Brunet --- arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 21 + 1 file changed, 21 insertions(+) diff --git a/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi b/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi index 88ad3490c124..8f57e74b719c

[PATCH 7/8] ARM64: dts: meson-gxl: add i2s output pins

Signed-off-by: Jerome Brunet --- arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 62 ++ 1 file changed, 62 insertions(+) diff --git a/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi b/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi index

[PATCH 8/8] ARM64: dts: meson-gxl: add spdif output pins

Signed-off-by: Jerome Brunet --- arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 21 + 1 file changed, 21 insertions(+) diff --git a/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi b/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi index 88ad3490c124..8f57e74b719c 100644 ---

[PATCH 7/8] ARM64: dts: meson-gxl: add i2s output pins

Signed-off-by: Jerome Brunet --- arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 62 ++ 1 file changed, 62 insertions(+) diff --git a/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi b/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi index fe11b5fc61f7..88ad3490c124 100644 ---

[PATCH 6/8] ARM64: dts: meson-gxbb: add spdif output pins

Signed-off-by: Jerome Brunet --- arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 21 + 1 file changed, 21 insertions(+) diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi index

Re: [tip:sched/urgent] sched/clock: Fix clear_sched_clock_stable() preempt wobbly

On Thu, Mar 23, 2017 at 02:10:47AM -0700, tip-bot for Peter Zijlstra wrote: > Commit-ID: 71fdb70eb48784c1f28cdf2e67c4c587dd7f2594 > Gitweb: http://git.kernel.org/tip/71fdb70eb48784c1f28cdf2e67c4c587dd7f2594 > Author: Peter Zijlstra > AuthorDate: Mon, 13 Mar 2017

Re: [tip:sched/urgent] sched/clock: Fix clear_sched_clock_stable() preempt wobbly

On Thu, Mar 23, 2017 at 02:10:47AM -0700, tip-bot for Peter Zijlstra wrote: > Commit-ID: 71fdb70eb48784c1f28cdf2e67c4c587dd7f2594 > Gitweb: http://git.kernel.org/tip/71fdb70eb48784c1f28cdf2e67c4c587dd7f2594 > Author: Peter Zijlstra > AuthorDate: Mon, 13 Mar 2017 13:46:21 +0100 >

[PATCH 6/8] ARM64: dts: meson-gxbb: add spdif output pins

Signed-off-by: Jerome Brunet --- arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 21 + 1 file changed, 21 insertions(+) diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi index 5ce70e1ec9ae..e5fd88e2c5f7 100644 ---

[PATCH 5/8] ARM64: dts: meson-gxbb: add i2s output pins

Signed-off-by: Jerome Brunet --- arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 63 + 1 file changed, 63 insertions(+) diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi index

[PATCH 4/8] pinctrl: meson: gxl: add spdif output pins

Signed-off-by: Jerome Brunet --- drivers/pinctrl/meson/pinctrl-meson-gxl.c | 18 ++ 1 file changed, 18 insertions(+) diff --git a/drivers/pinctrl/meson/pinctrl-meson-gxl.c b/drivers/pinctrl/meson/pinctrl-meson-gxl.c index a022a9e49113..a5a9b4f78636 100644

[PATCH 5/8] ARM64: dts: meson-gxbb: add i2s output pins

Signed-off-by: Jerome Brunet --- arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 63 + 1 file changed, 63 insertions(+) diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi index 04b3324bc132..5ce70e1ec9ae 100644 ---

[PATCH 4/8] pinctrl: meson: gxl: add spdif output pins

Signed-off-by: Jerome Brunet --- drivers/pinctrl/meson/pinctrl-meson-gxl.c | 18 ++ 1 file changed, 18 insertions(+) diff --git a/drivers/pinctrl/meson/pinctrl-meson-gxl.c b/drivers/pinctrl/meson/pinctrl-meson-gxl.c index a022a9e49113..a5a9b4f78636 100644 ---

[PATCH 3/8] pinctrl: meson: gxl: add i2s output pins

Signed-off-by: Jerome Brunet --- drivers/pinctrl/meson/pinctrl-meson-gxl.c | 31 +++ 1 file changed, 31 insertions(+) diff --git a/drivers/pinctrl/meson/pinctrl-meson-gxl.c b/drivers/pinctrl/meson/pinctrl-meson-gxl.c index

[PATCH 3/8] pinctrl: meson: gxl: add i2s output pins

Signed-off-by: Jerome Brunet --- drivers/pinctrl/meson/pinctrl-meson-gxl.c | 31 +++ 1 file changed, 31 insertions(+) diff --git a/drivers/pinctrl/meson/pinctrl-meson-gxl.c b/drivers/pinctrl/meson/pinctrl-meson-gxl.c index a0a7936f8f0d..a022a9e49113 100644 ---

[PATCH 2/8] pinctrl: meson: gxbb: add spdif output pins

Signed-off-by: Jerome Brunet --- drivers/pinctrl/meson/pinctrl-meson-gxbb.c | 18 ++ 1 file changed, 18 insertions(+) diff --git a/drivers/pinctrl/meson/pinctrl-meson-gxbb.c b/drivers/pinctrl/meson/pinctrl-meson-gxbb.c index 8d5dd4772042..9bae2e3968af

[PATCH 2/8] pinctrl: meson: gxbb: add spdif output pins

Signed-off-by: Jerome Brunet --- drivers/pinctrl/meson/pinctrl-meson-gxbb.c | 18 ++ 1 file changed, 18 insertions(+) diff --git a/drivers/pinctrl/meson/pinctrl-meson-gxbb.c b/drivers/pinctrl/meson/pinctrl-meson-gxbb.c index 8d5dd4772042..9bae2e3968af 100644 ---

<    4   5   6   7   8   9   10   11   12   13   >