Commit-ID: fffa954fb528963c2fb7b0c0084eb77e2be7ab52
Gitweb: http://git.kernel.org/tip/fffa954fb528963c2fb7b0c0084eb77e2be7ab52
Author: Peter Zijlstra
AuthorDate: Wed, 22 Mar 2017 11:35:50 +0100
Committer: Thomas Gleixner
CommitDate: Thu, 23 Mar 2017 19:10:07 +0100
futex: Remove rt_mute
Commit-ID: 1b367ece0d7e696cab1c8501bab282cc6a538b3f
Gitweb: http://git.kernel.org/tip/1b367ece0d7e696cab1c8501bab282cc6a538b3f
Author: Peter Zijlstra
AuthorDate: Wed, 22 Mar 2017 11:35:49 +0100
Committer: Thomas Gleixner
CommitDate: Thu, 23 Mar 2017 19:10:06 +0100
futex: Use smp_store_
Commit-ID: 499f5aca2cdd5e958b27e2655e7e7f82524f46b1
Gitweb: http://git.kernel.org/tip/499f5aca2cdd5e958b27e2655e7e7f82524f46b1
Author: Peter Zijlstra
AuthorDate: Wed, 22 Mar 2017 11:35:48 +0100
Committer: Thomas Gleixner
CommitDate: Thu, 23 Mar 2017 19:10:06 +0100
futex: Cleanup variab
On Thu, 23 Mar 2017 15:56:10 +0100
Peter Zijlstra wrote:
> Previous patches changed the meaning of the return value of
> rt_mutex_slowunlock(); update comments and code to reflect this.
>
> Signed-off-by: Peter Zijlstra (Intel)
> ---
Acked-by: Steven Rostedt (VMware)
-- Steve
On Thu, Mar 23, 2017 at 06:28:39PM +0100, Borislav Petkov wrote:
> Meh, I don't like the idea of keeping an evergrowing list of PFNs we
> can't do anything about anyway.
Keeping every PFN would be overkill (most of them should be taken
offline with no issues). A fixed array of a few of them with
On Thu, 23 Mar 2017, Steven Rostedt wrote:
> --- a/arch/x86/kernel/ftrace_64.S
> +++ b/arch/x86/kernel/ftrace_64.S
> @@ -1,5 +1,5 @@
> /*
> - * linux/arch/x86_64/mcount_64.S
> + * linux/arch/x86_64/ftrace_64.S
Can we please get rid of that nonsense completely?
> *
> * Copyright (C) 2014
Since kernel 4.11-rc1, my desktop (Plasma5/KDE) has encountered intermittent
hangs with the following information in the logs:
linux-4v1g.suse kernel: [drm] GPU HANG: ecode 7:0:0xf3ce, in plasmashell
[1283], reason: Hang on render ring, action: reset
linux-4v1g.suse kernel: [drm] GPU hangs
On 23 March 2017 18:12:33 GMT+00:00, SIMRAN SINGHAL
wrote:
>On Thu, Mar 23, 2017 at 1:55 AM, Jonathan Cameron
>wrote:
>> On 21/03/17 18:03, simran singhal wrote:
>>> The IIO subsystem is redefining iio_dev->mlock to be used by
>>> the IIO core only for protecting device operating mode changes.
On 23-Mar 12:01, Tejun Heo wrote:
> Hello,
Hi Tejun,
> On Thu, Mar 23, 2017 at 10:32:54AM +, Patrick Bellasi wrote:
> > > But then we would lose out on being able to attach capacity
> > > constraints to specific tasks or groups of tasks?
> >
> > Yes, right. If CGroups are not available than
On Thu, Mar 23, 2017 at 1:55 AM, Jonathan Cameron wrote:
> On 21/03/17 18:03, simran singhal wrote:
>> The IIO subsystem is redefining iio_dev->mlock to be used by
>> the IIO core only for protecting device operating mode changes.
>> ie. Changes between INDIO_DIRECT_MODE, INDIO_BUFFER_* modes.
>>
On Thu, Mar 23, 2017 at 07:42:09PM +0300, Dan Carpenter wrote:
> On Thu, Mar 23, 2017 at 05:53:58PM +0200, Jarkko Sakkinen wrote:
> > On Wed, Mar 22, 2017 at 04:12:49PM +0300, Dan Carpenter wrote:
> > > On Wed, Mar 22, 2017 at 11:45:37AM +, Colin Ian King wrote:
> > > > On 22/03/17 11:42, Jarkk
Thank you very much or your reply.
I naively thought that starting without partitions would be the best
starting point, given 3 of the disks had been in a RAID5 array
previously (possibly with partitions, not sure), but that looks like
a bad choice, based on some other things I've googled. Less
On Thu, Mar 23, 2017 at 5:09 AM, Dmitry Vyukov wrote:
> Hello,
>
> I've got the following report while running syzkaller fuzzer. Note the
> preceding kmem_cache_alloc injected failure, it's most likely the root
> cause.
>
> FAULT_INJECTION: forcing a failure.
> name failslab, interval 1, probabili
On 03/23/2017 10:25 AM, Mike Kravetz wrote:
> 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 reg
On 23/03/2017 13:30, Wanpeng Li wrote:
> From: Wanpeng Li
>
> This can be reproduced by running L2 on L1, and disable VPID on L0
> if w/o commit "KVM: nVMX: Fix nested VPID vmx exec control", the L2
> crash as below:
>
> KVM: entry failed, hardware error 0x7
> EAX= EBX= ECX=0
On Tue, Mar 21, 2017 at 04:47:05PM -0600, Tyler Baicar wrote:
> Currently external aborts are unsupported by the guest abort
> handling. Add handling for SEAs so that the host kernel reports
> SEAs which occur in the guest kernel.
>
> Signed-off-by: Tyler Baicar
> ---
> arch/arm/include/asm/kvm_
Am Donnerstag, 23. März 2017, 17:51:53 CET schrieb John Keeping:
> On Thu, 23 Mar 2017 11:10:20 -0500, Julia Cartwright wrote:
> > One quick question below. Apologies if this has been covered, but just
> > want to be sure.
> >
> > On Thu, Mar 23, 2017 at 10:59:28AM +, John Keeping wrote:
> >
On Tue, Mar 21, 2017 at 04:47:00PM -0600, Tyler Baicar wrote:
> ARM APEI extension proposal added SEA (Synchronous External Abort)
> notification type for ARMv8.
> Add a new GHES error source handling function for SEA. If an error
> source's notification type is SEA, then this function can be regis
On Thu, 23 Mar 2017 11:10:20 -0500, Julia Cartwright wrote:
> One quick question below. Apologies if this has been covered, but just
> want to be sure.
>
> On Thu, Mar 23, 2017 at 10:59:28AM +, John Keeping wrote:
> > regmap_update_bits does its own locking and everything else accessed
> > h
Yeah I think this is ok, I’ll throw it on my queue for fixes for this cycle.
Thanks,
Josef
On 3/20/17, 6:58 PM, "Ming Lin" wrote:
From: Ratna Manoj Bolla
When a filesystem is mounted on a nbd device and on a disconnect, because
of kill_bdev(), and resetting bdev size to zero, buffer_head ma
> -Original Message-
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Thursday, March 23, 2017 9:04 AM
> To: Long Li
> Cc: KY Srinivasan ; Haiyang Zhang
> ; Stephen Hemminger
> ; de...@linuxdriverproject.org; linux-
> ker...@vger.kernel.org; sta...@vger.kernel.org
> Subject:
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
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 maked
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
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 running
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 on
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' param
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
---
drivers/mmc/host/
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.
>
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
+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.
>
> Signed-o
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)
> IP
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 capabiliti
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: sta...@vger.kern
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 a/MAINTAI
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
>
>>
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 iobu
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 restric
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 insertion(+)
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 t
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 reser
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
arch/x86/include/asm/pgtable_
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 CONFIG_ARCH_NO_
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 b/arch/ar
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 f2b0
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 err
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 CE
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 wri
>
> 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 of
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 Mar
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 Mon,
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 differen
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 read
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 pro
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 wrot
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 have
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,
> > > >
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.
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
>>>
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 arr
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 (8):
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 supporte
>
> 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, Dav
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
--- a/arch/arm64/
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
--- a/ar
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
> Committer
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
--- a/arch/arm
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
--- a/
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
--- a/drivers/pinctrl/m
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
--- a/driv
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
--- a/drivers/pinctr
Signed-off-by: Jerome Brunet
---
drivers/pinctrl/meson/pinctrl-meson-gxbb.c | 31 ++
1 file changed, 31 insertions(+)
diff --git a/drivers/pinctrl/meson/pinctrl-meson-gxbb.c
b/drivers/pinctrl/meson/pinctrl-meson-gxbb.c
index 7671424d46cb..8d5dd4772042 100644
--- a/dr
On Tue, 21 Mar 2017, Quentin Schulz wrote:
> This patch adds documentation for the A33 GPADC binding.
>
> Signed-off-by: Quentin Schulz
> ---
>
> v3:
> - fixed missing allwinner in front of compatible,
> - updated compatible to allwinner,sun8i-a33-ths to better reflect the
> datasheet's n
On Wed, 22 Mar 2017, Andy Shevchenko wrote:
> On Wed, 2017-03-22 at 12:29 +0100, Hans de Goede wrote:
> > The Crystal Cove PMIC provides an ACPI OPRegion handler, which must be
> > available before other drivers using it are loaded, which is why
> > INTEL_SOC_PMIC is a bool.
> >
> > Just having t
On 03/21/2017 06:43 PM, Ankur Arora wrote:
> This patch series re-enables the upload of PM data from initial-domain
> to Xen. This was broken in commit cd979883b9ede90643e019f33cb317933eb867b4.
>
> The upload now happens post-resume in workqueue context. From the
> POV of Xen, the PM upload might b
On Mon, 20 Mar 2017, Hans de Goede wrote:
> Add mfd driver for Intel CHT Whiskey Cove PMIC, based on various non
> upstreamed CHT Whiskey Cove PMIC patches.
>
> This is a somewhat minimal version which adds irqchip support and cells
> for: ACPI PMIC opregion support, the i2c-controller driving th
On Mon, Nov 14, 2016 at 10:43 AM, Dmitry Vyukov wrote:
> On Mon, Nov 14, 2016 at 10:34 AM, Paolo Bonzini wrote:
>>
>>
>> On 14/11/2016 10:03, Dmitry Vyukov wrote:
>>> Paolo,
>>> can you please also commit this test to tools/testing? We are
>>> frustrated by the situation that we reported hundreds
On Thu, Mar 23, 2017 at 05:53:58PM +0200, Jarkko Sakkinen wrote:
> On Wed, Mar 22, 2017 at 04:12:49PM +0300, Dan Carpenter wrote:
> > On Wed, Mar 22, 2017 at 11:45:37AM +, Colin Ian King wrote:
> > > On 22/03/17 11:42, Jarkko Sakkinen wrote:
> > > > On Mon, Mar 20, 2017 at 02:23:36PM +, Col
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 Mar 2017 13:07:16 +0800
> > Subject: [PATCH] virtio_p
Hi Ralph,
On sam., mars 18 2017, Ralph Sennhauser wrote:
It seems that I don't receive the 1st patch of the series.
Also could you refresh my mind to expose why these patchse were not
apply the first time and why we should apply them now?
Thanks,
Gregory
> From: Andrew Lunn
>
> Add prope
On Thu, 23 Mar 2017 17:20:48 +0100
David Hildenbrand wrote:
>
> > As this may set kvm->buses[bus_idx] to NULL, don't you also need to
> > guard for bus == NULL in kvm_io_bus_destroy()? (I looked at the code on
> > kvm/queue.)
>
> very right, so something like this?
>
> diff --git a/virt/kvm/kv
On Tue, Mar 14, 2017 at 4:17 PM, Radim Krčmář wrote:
> 2017-03-12 12:20+0100, Dmitry Vyukov:
>> On Tue, Jan 17, 2017 at 5:00 PM, Dmitry Vyukov wrote:
>>> On Tue, Jan 17, 2017 at 4:20 PM, Paolo Bonzini wrote:
On 13/01/2017 12:15, Dmitry Vyukov wrote:
>
> I've commented out
Hi,
On Thu, Mar 23, 2017 at 9:23 PM, Evgenii Shatokhin
wrote:
> On 23.03.2017 03:27, Kees Cook wrote:
>>
>> This is a modified revert of commit 65fe935dd238 ("x86/KASLR, x86/power:
>> Remove x86 hibernation restrictions"), since it appears that 32-bit
>> hibernation still can't support KASLR. 64-
The MIPS remote processor driver allows non-Linux firmware to take
control of and execute on one of the systems VPEs. If that VPE is
brought back under Linux, it is necessary to ensure that all GIC
interrupts are routed and masked as Linux expects them, as the firmware
can have done anything it lik
The MIPS remote processor driver (CONFIG_MIPS_REMOTEPROC) provides a
more standard mechanism for using one or more VPs as coprocessors
running separate firmware.
Here we deprecate this mechanism before it is removed.
Signed-off-by: Matt Redfearn
---
Changes in v6: None
Changes in v5: None
Chang
From: Lisa Parratt
VP(E) stealing provides a mechanism for removing an offline Virtual
Processor from the Linux kernel such that it is available to run bare
metal code.
Once the CPU has been offlined from Linux, the CPU can be given a task
to run via mips_cps_steal_cpu_and_execute(). The CPU is r
The MIPS remote processor driver allows non-Linux firmware to take
control of and execute on one of the systems VPEs, turning the system
into a hybrid of SMP Linux and AMP.
This is useful to allow running bare metal code, or an RTOS, on one or
more CPUs while allowing Linux to continue running on
This driver allows a MIPS processor offlined from Linux to be used as a
remote processor. The processor can then handle real-time tasks or
perform coprocessing while remaining processors are available to Linux,
effectively making the system hybrid of SMP Linux and AMP.
A sysfs interface is provide
On Thu, Mar 23, 2017 at 05:53:58PM +0200, Jarkko Sakkinen wrote:
> On Wed, Mar 22, 2017 at 04:12:49PM +0300, Dan Carpenter wrote:
> > On Wed, Mar 22, 2017 at 11:45:37AM +, Colin Ian King wrote:
> > > On 22/03/17 11:42, Jarkko Sakkinen wrote:
> > > > On Mon, Mar 20, 2017 at 02:23:36PM +, Col
On Mon, 20 Mar 2017, Jeremy Linton wrote:
> The hisi pmic requires an independent regulator driver to be
> loaded so that devices dependent on the pmic/regulator are
> started properly. Currently there is only a single compatible
> regulator driver in the tree, so reference it with a module soft
>
On Thu, Mar 23, 2017 at 2:27 AM, Linus Walleij wrote:
> On Mon, Mar 20, 2017 at 5:03 AM, Stephen Rothwell
> wrote:
>> Hi Linus,
>>
>> Today's linux-next merge of the gpio tree got a conflict in:
>>
>> drivers/input/misc/soc_button_array.c
>>
>> between commit:
>>
>> a01cd17000a4 ("Input: soc
Hi Ralph,
On jeu., mars 16 2017, Ralph Sennhauser wrote:
> Add appropriate properties to devices in the Linksys WRT AC Series for the
> mvneta driver to use hardware buffer management.
>
> Also update "soc" ranges property and set the status of bm and bm-bppi
> to "okay" (SRAM).
>
> Signed-off
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi
b/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi
index fe11b5f..64f4b6e 100644
--- a/arch/arm64/boot/dts/amlogic/meson-gxl.dts
Signed-off-by: Neil Armstrong
---
arch/arm/boot/dts/meson8.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/meson8.dtsi b/arch/arm/boot/dts/meson8.dtsi
index 45619f6..ebc763e 100644
--- a/arch/arm/boot/dts/meson8.dtsi
+++ b/arch/arm/boot/dts/meson8.dtsi
@@ -106,6 +106,
Whem trying to add a gpio hog to enable the USB Hub on the Odroid-C2, I
encountered a strange bug where when calling gpiochip_add_data() the gpiolib
code was trying to add the Hog but failed because the gpio ranges were missing.
In the meson-pinctrl driver, the gpio ranges are added manually /afte
Signed-off-by: Neil Armstrong
---
arch/arm/boot/dts/meson8b.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/meson8b.dtsi b/arch/arm/boot/dts/meson8b.dtsi
index 41fd536..828aa49 100644
--- a/arch/arm/boot/dts/meson8b.dtsi
+++ b/arch/arm/boot/dts/meson8b.dtsi
@@ -198,6
When trying to add a gpio-hog, we enter a weird loop where the gpio-ranges
is needed when gpiochip_add_data() is called but in the current implementation
the ranges are added from the driver afterwards.
A simple solution is to rely on the DR gpio-ranges attribute and remove the
call to gpiochip_ad
The ODroid-C2 on-board USB Hub needs to to have it's reset signal set to
high level in order to be enumerated by the USB Host Controller.
But this management must be part of the currently in-development Generic
Power Sequence patch that will allow a USB Controller driver to start and stop
a power
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
index 04b3324..84c590b 100644
--- a/arch/arm64/boot/dts/amlogic/meson-gxbb
Hi Geert,
On dim., mars 12 2017, Geert Uytterhoeven wrote:
> Submitters of device tree binding documentation may forget to CC
> the subsystem maintainer if this is missing.
>
> Signed-off-by: Geert Uytterhoeven
> Cc: Jason Cooper
> Cc: Andrew Lunn
> Cc: Sebastian Hesselbarth
> Cc: Gregory
401 - 500 of 1018 matches
Mail list logo
