Signed-off-by: Vitaly Kuznetsov
---
x86/Makefile.common| 3 +
x86/hyperv.h | 7 ++
x86/hyperv_stimer_direct.c | 250 +
x86/unittests.cfg | 6 +
4 files changed, 266 insertions(+)
create mode 100644
Signed-off-by: Vitaly Kuznetsov
---
linux-headers/linux/kvm.h | 1 +
target/i386/cpu.c | 1 +
target/i386/cpu.h | 1 +
target/i386/hyperv-proto.h | 1 +
target/i386/kvm.c | 11 +++
5 files changed, 15 insertions(+)
diff --git a/linux-headers/linux/kvm.h
Signed-off-by: Vitaly Kuznetsov
---
x86/Makefile.common| 3 +
x86/hyperv.h | 7 ++
x86/hyperv_stimer_direct.c | 250 +
x86/unittests.cfg | 6 +
4 files changed, 266 insertions(+)
create mode 100644
Signed-off-by: Vitaly Kuznetsov
---
linux-headers/linux/kvm.h | 1 +
target/i386/cpu.c | 1 +
target/i386/cpu.h | 1 +
target/i386/hyperv-proto.h | 1 +
target/i386/kvm.c | 11 +++
5 files changed, 15 insertions(+)
diff --git a/linux-headers/linux/kvm.h
As a preparation to implementing Direct Mode for Hyper-V synthetic
timers switch to using stimer config definition from hyperv-tlfs.h.
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/include/asm/hyperv-tlfs.h | 6 --
arch/x86/include/asm/kvm_host.h| 2 +-
arch/x86/kvm/hyperv.c
As a preparation to implementing Direct Mode for Hyper-V synthetic
timers switch to using stimer config definition from hyperv-tlfs.h.
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/include/asm/hyperv-tlfs.h | 6 --
arch/x86/include/asm/kvm_host.h| 2 +-
arch/x86/kvm/hyperv.c
Turns out Hyper-V on KVM (as of 2016) will only use synthetic timers
if direct mode is available. With direct mode we notify the guest by
asserting APIC irq instead of sending a SynIC message.
The series was tested with Hyper-V on KVM as well as kvm-unit-tests.
I'm including Qemu a kvm-unit-tests
We implement Hyper-V SynIC and synthetic timers in KVM too so there's some
room for code sharing.
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/include/asm/hyperv-tlfs.h | 69 ++
drivers/hv/hv.c| 2 +-
drivers/hv/hyperv_vmbus.h | 68
Turns out Hyper-V on KVM (as of 2016) will only use synthetic timers
if direct mode is available. With direct mode we notify the guest by
asserting APIC irq instead of sending a SynIC message.
The series was tested with Hyper-V on KVM as well as kvm-unit-tests.
I'm including Qemu a kvm-unit-tests
We implement Hyper-V SynIC and synthetic timers in KVM too so there's some
room for code sharing.
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/include/asm/hyperv-tlfs.h | 69 ++
drivers/hv/hv.c| 2 +-
drivers/hv/hyperv_vmbus.h | 68
selinux_sctp_bind_connect() must verify if the address buffer has
sufficient length before accessing the 'sa_family' field. See
__sctp_connect() for a similar check.
The length of the whole address ('len') is already checked in the
callees.
Reported-by: Qian Cai
Fixes: d452930fd3b9 ("selinux:
selinux_sctp_bind_connect() must verify if the address buffer has
sufficient length before accessing the 'sa_family' field. See
__sctp_connect() for a similar check.
The length of the whole address ('len') is already checked in the
callees.
Reported-by: Qian Cai
Fixes: d452930fd3b9 ("selinux:
Hello.
As an outcome of https://lkml.org/lkml/2018/10/19/786 discussion there was
an interest in stress/performance test suite. It was developed to analyse
a vmalloc allocator from performance, stability point of view and compare
the new approach with current one.
I have explained in the commit
This patch pulls the trigger for multi-page bvecs.
Now any request queue which supports queue cluster will see multi-page
bvecs.
Cc: Christoph Hellwig
Signed-off-by: Ming Lei
---
block/bio.c | 24 ++--
1 file changed, 18 insertions(+), 6 deletions(-)
diff --git
Hello.
As an outcome of https://lkml.org/lkml/2018/10/19/786 discussion there was
an interest in stress/performance test suite. It was developed to analyse
a vmalloc allocator from performance, stability point of view and compare
the new approach with current one.
I have explained in the commit
This patch pulls the trigger for multi-page bvecs.
Now any request queue which supports queue cluster will see multi-page
bvecs.
Cc: Christoph Hellwig
Signed-off-by: Ming Lei
---
block/bio.c | 24 ++--
1 file changed, 18 insertions(+), 6 deletions(-)
diff --git
This adds a new kernel module for analysis of vmalloc allocator. It is
only enabled as a module. There are two main reasons this module should
be used for. Those are performance evaluation and stressing of vmalloc
subsystem.
It consists of several test cases. As of now there are 8. The module
has
This adds a new kernel module for analysis of vmalloc allocator. It is
only enabled as a module. There are two main reasons this module should
be used for. Those are performance evaluation and stressing of vmalloc
subsystem.
It consists of several test cases. As of now there are 8. The module
has
On 11/12/18 11:43 AM, Joseph Myers wrote:
> On Sun, 11 Nov 2018, Florian Weimer wrote:
>
>> People may have disappeared from glibc development who have objected to
>> gettid. I thought this was the case with strlcpy/strlcat, but it was
>> not.
>
> Well, I know of two main people who were
On 11/12/18 11:43 AM, Joseph Myers wrote:
> On Sun, 11 Nov 2018, Florian Weimer wrote:
>
>> People may have disappeared from glibc development who have objected to
>> gettid. I thought this was the case with strlcpy/strlcat, but it was
>> not.
>
> Well, I know of two main people who were
Once multi-page bvec is enabled, the last bvec may include more than one
page, this patch use bvec_last_segment() to truncate the bio.
Cc: Christoph Hellwig
Cc: linux-fsde...@vger.kernel.org
Signed-off-by: Ming Lei
---
fs/buffer.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff
Once multi-page bvec is enabled, the last bvec may include more than one
page, this patch use bvec_last_segment() to truncate the bio.
Cc: Christoph Hellwig
Cc: linux-fsde...@vger.kernel.org
Signed-off-by: Ming Lei
---
fs/buffer.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff
On Tue, Nov 13, 2018 at 02:40:05PM +1100, Tom Burkart wrote:
> The change from integer based GPIO API to the descriptor based API
> breaks backward compatibility for the devicetree. This is due to
> the descriptor based API appending "-gpio" or "-gpios" (see
> Documentation/gpio/base.txt.)
On Tue, Nov 13, 2018 at 02:40:05PM +1100, Tom Burkart wrote:
> The change from integer based GPIO API to the descriptor based API
> breaks backward compatibility for the devicetree. This is due to
> the descriptor based API appending "-gpio" or "-gpios" (see
> Documentation/gpio/base.txt.)
On 11-Nov 18:08, Peter Zijlstra wrote:
> On Mon, Oct 29, 2018 at 06:33:01PM +, Patrick Bellasi wrote:
> > When a util_max clamped task sleeps, its clamp constraints are removed
> > from the CPU. However, the blocked utilization on that CPU can still be
> > higher than the max clamp value
On 11-Nov 18:08, Peter Zijlstra wrote:
> On Mon, Oct 29, 2018 at 06:33:01PM +, Patrick Bellasi wrote:
> > When a util_max clamped task sleeps, its clamp constraints are removed
> > from the CPU. However, the blocked utilization on that CPU can still be
> > higher than the max clamp value
Hi Philipp,
On Mon, Oct 8, 2018 at 2:55 PM Philipp Zabel wrote:
> On Mon, 2018-10-08 at 13:15 +0200, Geert Uytterhoeven wrote:
> > Grammar and indentation fixes.
> >
> > Signed-off-by: Geert Uytterhoeven
> > ---
> > include/linux/reset.h | 8
> > 1 file changed, 4 insertions(+), 4
Hi Philipp,
On Mon, Oct 8, 2018 at 2:55 PM Philipp Zabel wrote:
> On Mon, 2018-10-08 at 13:15 +0200, Geert Uytterhoeven wrote:
> > Grammar and indentation fixes.
> >
> > Signed-off-by: Geert Uytterhoeven
> > ---
> > include/linux/reset.h | 8
> > 1 file changed, 4 insertions(+), 4
On 11-Nov 17:47, Peter Zijlstra wrote:
> On Mon, Oct 29, 2018 at 06:32:59PM +, Patrick Bellasi wrote:
> > +static inline void uclamp_cpu_update(struct rq *rq, unsigned int clamp_id)
> > +{
> > + unsigned int group_id;
> > + int max_value = 0;
> > +
> > + for (group_id = 0; group_id <
On 11-Nov 17:47, Peter Zijlstra wrote:
> On Mon, Oct 29, 2018 at 06:32:59PM +, Patrick Bellasi wrote:
> > +static inline void uclamp_cpu_update(struct rq *rq, unsigned int clamp_id)
> > +{
> > + unsigned int group_id;
> > + int max_value = 0;
> > +
> > + for (group_id = 0; group_id <
On Tue, Nov 13, 2018 at 03:54:53PM +0200, Ville Syrjälä wrote:
> Hi Paul,
>
> After 4.20-rc1 some of my 32bit UP machines no longer reboot/shutdown.
> I bisected this down to commit 45975c7d21a1 ("rcu: Define RCU-sched
> API in terms of RCU for Tree RCU PREEMPT builds").
>
> I traced the hang
On Tue, Nov 13, 2018 at 03:54:53PM +0200, Ville Syrjälä wrote:
> Hi Paul,
>
> After 4.20-rc1 some of my 32bit UP machines no longer reboot/shutdown.
> I bisected this down to commit 45975c7d21a1 ("rcu: Define RCU-sched
> API in terms of RCU for Tree RCU PREEMPT builds").
>
> I traced the hang
On Tue, Nov 13, 2018 at 01:28:04PM +, Shameerali Kolothum Thodi wrote:
>
> > -Original Message-
> > From: mika.westerb...@linux.intel.com
> > [mailto:mika.westerb...@linux.intel.com]
> > Sent: 13 November 2018 12:59
> > To: Shameerali Kolothum Thodi
> > Cc: linux-...@vger.kernel.org;
On Tue, Nov 13, 2018 at 01:28:04PM +, Shameerali Kolothum Thodi wrote:
>
> > -Original Message-
> > From: mika.westerb...@linux.intel.com
> > [mailto:mika.westerb...@linux.intel.com]
> > Sent: 13 November 2018 12:59
> > To: Shameerali Kolothum Thodi
> > Cc: linux-...@vger.kernel.org;
Hi Shawn,
On Tue, 13 Nov 2018 at 15:42, Shawn Guo wrote:
>
> On Mon, Nov 05, 2018 at 10:12:30AM +0100, Martin Kaiser wrote:
> > Hi,
> >
> > Thus wrote Shawn Guo (shawn...@kernel.org):
> >
> > > On Thu, Nov 01, 2018 at 06:32:47PM +0100, Martin Kaiser wrote:
> > > > The i.MX25 contains two EPIT
Hi Shawn,
On Tue, 13 Nov 2018 at 15:42, Shawn Guo wrote:
>
> On Mon, Nov 05, 2018 at 10:12:30AM +0100, Martin Kaiser wrote:
> > Hi,
> >
> > Thus wrote Shawn Guo (shawn...@kernel.org):
> >
> > > On Thu, Nov 01, 2018 at 06:32:47PM +0100, Martin Kaiser wrote:
> > > > The i.MX25 contains two EPIT
From: Li, Aubrey
> Sent: 13 November 2018 13:07
...
> > Isn't there an obvious optimisation to execute VZEROALL during system call
> > entry?
>
> I'm not aware of this in the kernel, maybe you are talking about some
> optimization in glibc?
I've not seen it anywhere either.
IIRC all the xmm and
From: Li, Aubrey
> Sent: 13 November 2018 13:07
...
> > Isn't there an obvious optimisation to execute VZEROALL during system call
> > entry?
>
> I'm not aware of this in the kernel, maybe you are talking about some
> optimization in glibc?
I've not seen it anywhere either.
IIRC all the xmm and
On Mon, 12 Nov 2018 10:32:51 +,
Parthiban Nallathambi wrote:
>
>
>
> On 11/8/18 6:03 PM, Marc Zyngier wrote:
> > On 26/08/18 16:20, Parthiban Nallathambi wrote:
> >> Hello Marc,
> >>
> >> Thanks for your feedback.
> >>
> >> On 8/13/18 1:46 PM, Marc Zyngier wrote:
> >>> On 12/08/18 13:22,
On Mon, 12 Nov 2018 10:32:51 +,
Parthiban Nallathambi wrote:
>
>
>
> On 11/8/18 6:03 PM, Marc Zyngier wrote:
> > On 26/08/18 16:20, Parthiban Nallathambi wrote:
> >> Hello Marc,
> >>
> >> Thanks for your feedback.
> >>
> >> On 8/13/18 1:46 PM, Marc Zyngier wrote:
> >>> On 12/08/18 13:22,
On 13.11.18 07:33, Arun KS wrote:
> totalram_pages, zone->managed_pages and totalhigh_pages updates
> are protected by managed_page_count_lock, but readers never care
> about it. Convert these variables to atomic to avoid readers
> potentially seeing a store tear.
>
> This patch converts
On 13.11.18 07:33, Arun KS wrote:
> totalram_pages, zone->managed_pages and totalhigh_pages updates
> are protected by managed_page_count_lock, but readers never care
> about it. Convert these variables to atomic to avoid readers
> potentially seeing a store tear.
>
> This patch converts
On Mon 12-11-18 12:54:45, Chanho Min wrote:
> Suspend fails due to the exec family of functions blocking the freezer.
> The casue is that de_thread() sleeps in TASK_UNINTERRUPTIBLE waiting for
> all sub-threads to die, and we have the deadlock if one of them is frozen.
> This also can occur with
On Mon 12-11-18 12:54:45, Chanho Min wrote:
> Suspend fails due to the exec family of functions blocking the freezer.
> The casue is that de_thread() sleeps in TASK_UNINTERRUPTIBLE waiting for
> all sub-threads to die, and we have the deadlock if one of them is frozen.
> This also can occur with
On 13.11.18 07:33, Arun KS wrote:
> This patch is in preparation to a later patch which converts totalram_pages
> and zone->managed_pages to atomic variables. Please note that re-reading
> the value might lead to a different value and as such it could lead to
> unexpected behavior. There are no
On 13.11.18 07:33, Arun KS wrote:
> This patch is in preparation to a later patch which converts totalram_pages
> and zone->managed_pages to atomic variables. Please note that re-reading
> the value might lead to a different value and as such it could lead to
> unexpected behavior. There are no
Define a hwspinlock to be used by irq controller
Signed-off-by: Benjamin Gaignard
---
arch/arm/boot/dts/stm32mp157c.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/stm32mp157c.dtsi
b/arch/arm/boot/dts/stm32mp157c.dtsi
index 98f824d8b0f0..7c9ee32b775d 100644
---
Define a hwspinlock to be used by irq controller
Signed-off-by: Benjamin Gaignard
---
arch/arm/boot/dts/stm32mp157c.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/stm32mp157c.dtsi
b/arch/arm/boot/dts/stm32mp157c.dtsi
index 98f824d8b0f0..7c9ee32b775d 100644
---
Add hwlocks as optional property
Signed-off-by: Benjamin Gaignard
---
.../devicetree/bindings/interrupt-controller/st,stm32-exti.txt| 4
1 file changed, 4 insertions(+)
diff --git
a/Documentation/devicetree/bindings/interrupt-controller/st,stm32-exti.txt
Add hwlocks as optional property
Signed-off-by: Benjamin Gaignard
---
.../devicetree/bindings/interrupt-controller/st,stm32-exti.txt| 4
1 file changed, 4 insertions(+)
diff --git
a/Documentation/devicetree/bindings/interrupt-controller/st,stm32-exti.txt
If a hwspinlock is defined in device tree use it to protect
configuration registers.
Signed-off-by: Benjamin Gaignard
---
drivers/irqchip/irq-stm32-exti.c | 36 ++--
1 file changed, 30 insertions(+), 6 deletions(-)
diff --git a/drivers/irqchip/irq-stm32-exti.c
This series allow to protect STM32 interrupt controller configuration registers
with a hwspinlock to avoid conflicting accesses between processors.
Benjamin Gaignard (3):
dt-bindings: interrupt-controller: stm32: Document hwlock properties
irqchip: stm32: protect configuration registers with
If a hwspinlock is defined in device tree use it to protect
configuration registers.
Signed-off-by: Benjamin Gaignard
---
drivers/irqchip/irq-stm32-exti.c | 36 ++--
1 file changed, 30 insertions(+), 6 deletions(-)
diff --git a/drivers/irqchip/irq-stm32-exti.c
This series allow to protect STM32 interrupt controller configuration registers
with a hwspinlock to avoid conflicting accesses between processors.
Benjamin Gaignard (3):
dt-bindings: interrupt-controller: stm32: Document hwlock properties
irqchip: stm32: protect configuration registers with
[+cc Martin, Rafael, Len, linux-acpi]
On Tue, Nov 13, 2018 at 11:20:04AM +0100, Borislav Petkov wrote:
> On Tue, Nov 13, 2018 at 08:17:12AM +0100, Ingo Molnar wrote:
> >
> > * Bjorn Helgaas wrote:
> >
> > > PCI changes:
> > >
> > > - Pay attention to device-specific _PXM node values
[+cc Martin, Rafael, Len, linux-acpi]
On Tue, Nov 13, 2018 at 11:20:04AM +0100, Borislav Petkov wrote:
> On Tue, Nov 13, 2018 at 08:17:12AM +0100, Ingo Molnar wrote:
> >
> > * Bjorn Helgaas wrote:
> >
> > > PCI changes:
> > >
> > > - Pay attention to device-specific _PXM node values
Set the according constraints for PM_SUSPEND_STANDBY case.
Previously, only suspend to mem/disk were taken into
consideration.
Signed-off-by: Andrei Stefanescu
---
drivers/regulator/of_regulator.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
Set the according constraints for PM_SUSPEND_STANDBY case.
Previously, only suspend to mem/disk were taken into
consideration.
Signed-off-by: Andrei Stefanescu
---
drivers/regulator/of_regulator.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
For state-mem and state-disk regulators can have
various parameters applied such as enabled/disabled,
current mode, voltage etc.
This patch adds documentation on how to set these parameters
in the device tree for the standby state.
Signed-off-by: Andrei Stefanescu
---
This patch series adds support for setting the regulator constraints
when entering standby Linux state.
The new bindings are called regulator-state-standby and have
the same syntax as regulator-state-mem/disk.
Before this patch, if the regulator driver implemented
set_suspend_voltage/mode the
For state-mem and state-disk regulators can have
various parameters applied such as enabled/disabled,
current mode, voltage etc.
This patch adds documentation on how to set these parameters
in the device tree for the standby state.
Signed-off-by: Andrei Stefanescu
---
This patch series adds support for setting the regulator constraints
when entering standby Linux state.
The new bindings are called regulator-state-standby and have
the same syntax as regulator-state-mem/disk.
Before this patch, if the regulator driver implemented
set_suspend_voltage/mode the
Hi,
This series + the core NMI patches can be fetched from:
git clone http://linux-arm.org/linux-jt.gitv4.20-pseudo-nmi
Thanks,
Julien
On 12/11/18 11:56, Julien Thierry wrote:
Hi,
This series is a continuation of the work started by Daniel [1]. The goal
is to use GICv3 interrupt
Hi,
This series + the core NMI patches can be fetched from:
git clone http://linux-arm.org/linux-jt.gitv4.20-pseudo-nmi
Thanks,
Julien
On 12/11/18 11:56, Julien Thierry wrote:
Hi,
This series is a continuation of the work started by Daniel [1]. The goal
is to use GICv3 interrupt
Hi Alex,
On 11/9/18 11:09 PM, Alex Williamson wrote:
> In commit 61d792562b53 ("vfio-pci: Use mutex around open, release, and
> remove") a mutex was added to freeze the refcnt for a device so that
> we can handle errors and perform bus resets on final close. However,
> bus resets can be rather
On Tue, Nov 13, 2018 at 1:40 PM Mika Westerberg
wrote:
>
> On Tue, Nov 13, 2018 at 01:13:31PM +0200, Yehezkel Bernat wrote:
> > On Tue, Nov 13, 2018 at 12:56 PM Mika Westerberg
> > wrote:
> > >
> > > > Just one point:
> > > > Have you considered the option to add this property per (TBT?) device?
Hi Alex,
On 11/9/18 11:09 PM, Alex Williamson wrote:
> In commit 61d792562b53 ("vfio-pci: Use mutex around open, release, and
> remove") a mutex was added to freeze the refcnt for a device so that
> we can handle errors and perform bus resets on final close. However,
> bus resets can be rather
On Tue, Nov 13, 2018 at 1:40 PM Mika Westerberg
wrote:
>
> On Tue, Nov 13, 2018 at 01:13:31PM +0200, Yehezkel Bernat wrote:
> > On Tue, Nov 13, 2018 at 12:56 PM Mika Westerberg
> > wrote:
> > >
> > > > Just one point:
> > > > Have you considered the option to add this property per (TBT?) device?
On Mon, Nov 05, 2018 at 10:12:30AM +0100, Martin Kaiser wrote:
> Hi,
>
> Thus wrote Shawn Guo (shawn...@kernel.org):
>
> > On Thu, Nov 01, 2018 at 06:32:47PM +0100, Martin Kaiser wrote:
> > > The i.MX25 contains two EPIT (Enhanced Periodic Interrupt Timer)
> > > function blocks. Add their ipg
On Mon, Nov 05, 2018 at 10:12:30AM +0100, Martin Kaiser wrote:
> Hi,
>
> Thus wrote Shawn Guo (shawn...@kernel.org):
>
> > On Thu, Nov 01, 2018 at 06:32:47PM +0100, Martin Kaiser wrote:
> > > The i.MX25 contains two EPIT (Enhanced Periodic Interrupt Timer)
> > > function blocks. Add their ipg
On 11/13/2018 04:20 AM, Borislav Petkov wrote:
> On Tue, Nov 13, 2018 at 08:17:12AM +0100, Ingo Molnar wrote:
>>
>> * Bjorn Helgaas wrote:
>>
>>> PCI changes:
>>>
>>> - Pay attention to device-specific _PXM node values (Jonathan Cameron)
>>
>> There's a new boot regression, my AMD ThreadRipper
On 11/13/2018 04:20 AM, Borislav Petkov wrote:
> On Tue, Nov 13, 2018 at 08:17:12AM +0100, Ingo Molnar wrote:
>>
>> * Bjorn Helgaas wrote:
>>
>>> PCI changes:
>>>
>>> - Pay attention to device-specific _PXM node values (Jonathan Cameron)
>>
>> There's a new boot regression, my AMD ThreadRipper
On Tue, Nov 13, 2018 at 8:52 AM Qian Cai wrote:
> On 11/13/18 at 8:33 AM, Paul Moore wrote:
> > On Mon, Nov 12, 2018 at 10:11 PM Qian Cai wrote:
> > > > On Nov 12, 2018, at 10:09 PM, Paul Moore wrote:
> > > >
> > > > On Mon, Nov 12, 2018 at 7:59 PM Qian Cai wrote:
> > > >>> On Nov 12, 2018, at
On Tue, Nov 13, 2018 at 8:52 AM Qian Cai wrote:
> On 11/13/18 at 8:33 AM, Paul Moore wrote:
> > On Mon, Nov 12, 2018 at 10:11 PM Qian Cai wrote:
> > > > On Nov 12, 2018, at 10:09 PM, Paul Moore wrote:
> > > >
> > > > On Mon, Nov 12, 2018 at 7:59 PM Qian Cai wrote:
> > > >>> On Nov 12, 2018, at
Hi Geert,
On Mon, 2018-10-08 at 13:15 +0200, Geert Uytterhoeven wrote:
> Grammar and indentation fixes.
>
> Signed-off-by: Geert Uytterhoeven
> ---
> include/linux/reset.h | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/include/linux/reset.h
Hi Geert,
On Mon, 2018-10-08 at 13:15 +0200, Geert Uytterhoeven wrote:
> Grammar and indentation fixes.
>
> Signed-off-by: Geert Uytterhoeven
> ---
> include/linux/reset.h | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/include/linux/reset.h
On Sat, Nov 10, 2018 at 04:05:44PM +, A.s. Dong wrote:
> Hi Stephen,
>
> [...]
> > > I already sent the 12th version of this current patch series and I
> > > would really like to get this in ASAP so that the booting up of imx8mq
> > > will
> > not be delayed.
> > >
> >
> > Ok. Well we're in
On Sat, Nov 10, 2018 at 04:05:44PM +, A.s. Dong wrote:
> Hi Stephen,
>
> [...]
> > > I already sent the 12th version of this current patch series and I
> > > would really like to get this in ASAP so that the booting up of imx8mq
> > > will
> > not be delayed.
> > >
> >
> > Ok. Well we're in
Commit-ID: 83a204daa40315a38204493f60768910c8604e9c
Gitweb: https://git.kernel.org/tip/83a204daa40315a38204493f60768910c8604e9c
Author: Borislav Petkov
AuthorDate: Fri, 9 Nov 2018 23:13:13 +0100
Committer: Borislav Petkov
CommitDate: Tue, 13 Nov 2018 14:55:08 +0100
x86/mce: Fix
Commit-ID: 83a204daa40315a38204493f60768910c8604e9c
Gitweb: https://git.kernel.org/tip/83a204daa40315a38204493f60768910c8604e9c
Author: Borislav Petkov
AuthorDate: Fri, 9 Nov 2018 23:13:13 +0100
Committer: Borislav Petkov
CommitDate: Tue, 13 Nov 2018 14:55:08 +0100
x86/mce: Fix
Commit-ID: 95715a3f0e4f0abc4749c6a4fdf2c08c3ff18450
Gitweb: https://git.kernel.org/tip/95715a3f0e4f0abc4749c6a4fdf2c08c3ff18450
Author: Borislav Petkov
AuthorDate: Mon, 12 Nov 2018 13:20:36 +0100
Committer: Borislav Petkov
CommitDate: Tue, 13 Nov 2018 15:16:50 +0100
x86/traps:
Commit-ID: 95715a3f0e4f0abc4749c6a4fdf2c08c3ff18450
Gitweb: https://git.kernel.org/tip/95715a3f0e4f0abc4749c6a4fdf2c08c3ff18450
Author: Borislav Petkov
AuthorDate: Mon, 12 Nov 2018 13:20:36 +0100
Committer: Borislav Petkov
CommitDate: Tue, 13 Nov 2018 15:16:50 +0100
x86/traps:
On Tue, 2018-11-06 at 15:57 +0100, Neil Armstrong wrote:
> This patchset is an attempt to handle the Amlogic Meson GX Video clock
> in the Common Clock Framework in order to move the video pipeline and
> HDMI controller clock management out of the Meson DRM Driver.
>
> In order :
> - Add support
On Tue, 2018-11-06 at 15:57 +0100, Neil Armstrong wrote:
> This patchset is an attempt to handle the Amlogic Meson GX Video clock
> in the Common Clock Framework in order to move the video pipeline and
> HDMI controller clock management out of the Meson DRM Driver.
>
> In order :
> - Add support
Compliment of the day to you Dear Friend.
Dear Friend.
I am Mrs. Amina Kadi. am sending this brief letter to solicit your
partnership to transfer $5.5 million US Dollars. I shall send you
more information and procedures when I receive positive response from
you.
Mrs. Amina Kadi
Compliment of the day to you Dear Friend.
Dear Friend.
I am Mrs. Amina Kadi. am sending this brief letter to solicit your
partnership to transfer $5.5 million US Dollars. I shall send you
more information and procedures when I receive positive response from
you.
Mrs. Amina Kadi
follow the linux coding style, rename the variable
shortGIrate to short_gi_rate.
Signed-off-by: Kevin Dou
---
drivers/staging/rtl8188eu/core/rtw_ap.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/rtl8188eu/core/rtw_ap.c
follow the linux coding style, rename the variable
shortGIrate to short_gi_rate.
Signed-off-by: Kevin Dou
---
drivers/staging/rtl8188eu/core/rtw_ap.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/rtl8188eu/core/rtw_ap.c
From: Bartosz Golaszewski
Stop using the at24_platform_data setup callback in favor of nvmem
notifiers.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/board-mityomapl138.c | 18 +++---
1 file changed, 15 insertions(+), 3 deletions(-)
diff --git
From: Bartosz Golaszewski
We want to work towards phasing out the at24_platform_data structure.
There are few users and its contents can be represented using generic
device properties. Using device properties only will allow us to
significantly simplify the at24 configuration code.
Remove the
From: Bartosz Golaszewski
Stop using the at24_platform_data setup callback in favor of nvmem
notifiers.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/board-mityomapl138.c | 18 +++---
1 file changed, 15 insertions(+), 3 deletions(-)
diff --git
From: Bartosz Golaszewski
We want to work towards phasing out the at24_platform_data structure.
There are few users and its contents can be represented using generic
device properties. Using device properties only will allow us to
significantly simplify the at24 configuration code.
Remove the
Hi Dinh,
On Mon, 2018-11-05 at 14:05 -0600, Dinh Nguyen wrote:
> From: Dinh Nguyen
>
> Create a separate reset driver that uses the reset operations in
> reset-simple. The reset driver for the SoCFPGA platform needs to
> register early in order to be able bring online timers that needed
> early
Hi Dinh,
On Mon, 2018-11-05 at 14:05 -0600, Dinh Nguyen wrote:
> From: Dinh Nguyen
>
> Create a separate reset driver that uses the reset operations in
> reset-simple. The reset driver for the SoCFPGA platform needs to
> register early in order to be able bring online timers that needed
> early
Hi,
thank you for the response.
On Fri, 2018-10-19 at 16:05 +0300, Andy Shevchenko wrote:
> On Wed, Oct 10, 2018 at 8:23 PM Lubomir Rintel
> wrote:
> > Also, the header is x86 specific, while there are non-x86 OLPC
> > machines.
>
> Same concern. as per patch 2.
Which concern? If it's that it
Hi,
thank you for the response.
On Fri, 2018-10-19 at 16:05 +0300, Andy Shevchenko wrote:
> On Wed, Oct 10, 2018 at 8:23 PM Lubomir Rintel
> wrote:
> > Also, the header is x86 specific, while there are non-x86 OLPC
> > machines.
>
> Same concern. as per patch 2.
Which concern? If it's that it
On Tue, Nov 13, 2018 at 12:27:45PM +0100, Vincent Whitchurch wrote:
> Thumb-2 functions have the lowest bit set in the symbol value in the
> symtab. When kallsyms are generated for the vmlinux, the kallsyms are
> generated from the output of nm, and nm clears the lowest bit.
>
> $
On Tue, Nov 13, 2018 at 12:27:45PM +0100, Vincent Whitchurch wrote:
> Thumb-2 functions have the lowest bit set in the symbol value in the
> symtab. When kallsyms are generated for the vmlinux, the kallsyms are
> generated from the output of nm, and nm clears the lowest bit.
>
> $
Hi Yogesh,
On 13.11.18 09:22, Yogesh Narayan Gaur wrote:
[...]
>> +
>> +static void fsl_qspi_read_ahb(struct fsl_qspi *q, const struct
>> +spi_mem_op *op) {
>> +/*
>> + * We want to avoid needing to invalidate the cache by issueing
>> + * a reset to the AHB and Serial Flash domain, as
Hi Yogesh,
On 13.11.18 09:22, Yogesh Narayan Gaur wrote:
[...]
>> +
>> +static void fsl_qspi_read_ahb(struct fsl_qspi *q, const struct
>> +spi_mem_op *op) {
>> +/*
>> + * We want to avoid needing to invalidate the cache by issueing
>> + * a reset to the AHB and Serial Flash domain, as
801 - 900 of 1256 matches
Mail list logo
