On Fri, Sep 29, 2017 at 03:48:38PM +1000, Stephen Rothwell wrote:
> News: I will not be doing linux-next releases from Setp 30 to Oct 30
> (inclusive).
I'll try to pick this up in my usual reduced service best effort manner
from Monday (only just noticed and I can't do tomorrow due to other
On Fri, Sep 29, 2017 at 03:48:38PM +1000, Stephen Rothwell wrote:
> News: I will not be doing linux-next releases from Setp 30 to Oct 30
> (inclusive).
I'll try to pick this up in my usual reduced service best effort manner
from Monday (only just noticed and I can't do tomorrow due to other
Hi Paolo,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 42b76d0e6b1fe0fcb90e0ff6b4d053d50597b031
commit: c0a1666bcb2a33e84187a15eabdcd54056be9a97 KVM: VMX: use cmpxchg64
date: 7 days ago
config:
Hi Paolo,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 42b76d0e6b1fe0fcb90e0ff6b4d053d50597b031
commit: c0a1666bcb2a33e84187a15eabdcd54056be9a97 KVM: VMX: use cmpxchg64
date: 7 days ago
config:
On Tue, Oct 03, 2017 at 07:27:01PM +, Thomas Gleixner wrote:
> On Tue, 3 Oct 2017, Thomas Gleixner wrote:
> > On Tue, 3 Oct 2017, Thomas Gleixner wrote:
> > > On Tue, 3 Oct 2017, Michael Ellerman wrote:
> > > > Hmm, I tried that patch, it makes the warning go away. But then I
> > > > triggered
On Tue, Oct 03, 2017 at 07:27:01PM +, Thomas Gleixner wrote:
> On Tue, 3 Oct 2017, Thomas Gleixner wrote:
> > On Tue, 3 Oct 2017, Thomas Gleixner wrote:
> > > On Tue, 3 Oct 2017, Michael Ellerman wrote:
> > > > Hmm, I tried that patch, it makes the warning go away. But then I
> > > > triggered
On Thu, 5 Oct 2017, Julia Cartwright wrote:
> On Thu, Oct 05, 2017 at 11:55:39AM -0400, Steven Rostedt wrote:
> > On Thu, 5 Oct 2017 10:37:59 -0500
> > Julia Cartwright wrote:
> >
> > > On Thu, Oct 05, 2017 at 05:27:30PM +0200, Thomas Gleixner wrote:
> > > > On Thu, 5 Oct 2017,
On Thu, 5 Oct 2017, Julia Cartwright wrote:
> On Thu, Oct 05, 2017 at 11:55:39AM -0400, Steven Rostedt wrote:
> > On Thu, 5 Oct 2017 10:37:59 -0500
> > Julia Cartwright wrote:
> >
> > > On Thu, Oct 05, 2017 at 05:27:30PM +0200, Thomas Gleixner wrote:
> > > > On Thu, 5 Oct 2017, Julia Cartwright
On Tue, Oct 03, 2017 at 02:58:52PM -0400, Theodore Ts'o wrote:
> The argument for making it be configurable is that if it does break
> things in way we can't foresee, it's a lot easier to back it out. And
> like what we've done with relatime, if the distro's all run with it as
> the default for a
On Tue, Oct 03, 2017 at 02:58:52PM -0400, Theodore Ts'o wrote:
> The argument for making it be configurable is that if it does break
> things in way we can't foresee, it's a lot easier to back it out. And
> like what we've done with relatime, if the distro's all run with it as
> the default for a
On Thu, 2017-10-05 at 15:12 +, David Laight wrote:
> From: Joe Perches
> > Sent: 05 October 2017 13:19
> > On Thu, 2017-10-05 at 14:05 +0200, Arnd Bergmann wrote:
> > > gcc produces a harmless warning about a recently introduced
> > > signed integer overflow:
> > >
> > >
On Thu, 2017-10-05 at 15:12 +, David Laight wrote:
> From: Joe Perches
> > Sent: 05 October 2017 13:19
> > On Thu, 2017-10-05 at 14:05 +0200, Arnd Bergmann wrote:
> > > gcc produces a harmless warning about a recently introduced
> > > signed integer overflow:
> > >
> > >
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 42b76d0e6b1fe0fcb90e0ff6b4d053d50597b031
commit: 8cb5d7482810b7eb1bb05bf4f71bc93ce35e5896 lib/lz4: make arrays static
const, reduces object code size
date: 2 days ago
config: cris-dev88_defconfig
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 42b76d0e6b1fe0fcb90e0ff6b4d053d50597b031
commit: 8cb5d7482810b7eb1bb05bf4f71bc93ce35e5896 lib/lz4: make arrays static
const, reduces object code size
date: 2 days ago
config: cris-dev88_defconfig
From: Markus Elfring
Date: Thu, 5 Oct 2017 18:02:05 +0200
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
From: Markus Elfring
Date: Thu, 5 Oct 2017 18:02:05 +0200
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
arch/powerpc/perf/hv-24x7.c | 1 -
1 file changed, 1 deletion(-)
diff
Hi Benjamin,
On 10/04/2017 11:27 AM, Benjamin Gaignard wrote:
Add Timers and it sub-nodes into DT for stm32f746 family.
Signed-off-by: Benjamin Gaignard
---
arch/arm/boot/dts/stm32f746.dtsi | 270 +++
1 file changed, 270
Hi Benjamin,
On 10/04/2017 11:27 AM, Benjamin Gaignard wrote:
Add Timers and it sub-nodes into DT for stm32f746 family.
Signed-off-by: Benjamin Gaignard
---
arch/arm/boot/dts/stm32f746.dtsi | 270 +++
1 file changed, 270 insertions(+)
diff --git
On Thu, Oct 05, 2017 at 11:55:39AM -0400, Steven Rostedt wrote:
> On Thu, 5 Oct 2017 10:37:59 -0500
> Julia Cartwright wrote:
>
> > On Thu, Oct 05, 2017 at 05:27:30PM +0200, Thomas Gleixner wrote:
> > > On Thu, 5 Oct 2017, Julia Cartwright wrote:
> > > > On Tue, Oct 03, 2017 at
On Thu, Oct 05, 2017 at 11:55:39AM -0400, Steven Rostedt wrote:
> On Thu, 5 Oct 2017 10:37:59 -0500
> Julia Cartwright wrote:
>
> > On Thu, Oct 05, 2017 at 05:27:30PM +0200, Thomas Gleixner wrote:
> > > On Thu, 5 Oct 2017, Julia Cartwright wrote:
> > > > On Tue, Oct 03, 2017 at 12:49:19PM
This patch adds device information to the DMI table of the cros_ec_lpc
driver for Google Glimmer devices. Since Google BIOS does not enumerate
devices in the LPC bus, the cros_ec_lpc driver checks for system
compatibility and registers the cros_ec device itself.
Signed-off-by: Thierry Escande
This patch adds device information to the DMI table of the cros_ec_lpc
driver for Google Glimmer devices. Since Google BIOS does not enumerate
devices in the LPC bus, the cros_ec_lpc driver checks for system
compatibility and registers the cros_ec device itself.
Signed-off-by: Thierry Escande
From: Gwendal Grignou
Add driver to support older EC firmware that only support deprecated
ec command. Rely on ACPI memory map register to access sensor
information.
Present same interface as the regular cros_ec sensor stack:
- one iio device per accelerometer
- use HTML5
From: Gwendal Grignou
Add driver to support older EC firmware that only support deprecated
ec command. Rely on ACPI memory map register to access sensor
information.
Present same interface as the regular cros_ec sensor stack:
- one iio device per accelerometer
- use HTML5 axis definition
- use
- On Oct 5, 2017, at 8:24 AM, Peter Zijlstra pet...@infradead.org wrote:
> On Thu, Oct 05, 2017 at 02:12:50PM +0200, Peter Zijlstra wrote:
>> On Wed, Oct 04, 2017 at 02:37:53PM -0700, Paul E. McKenney wrote:
>> > diff --git a/arch/powerpc/kernel/membarrier.c
>> >
Hi,
This series enables a driver for a legacy accelerometer driver used on
Chromebook devices with older EC firmware.
In addition to the cros_ec_accel_legacy driver, this series contains a
fix that registers the cros_ec_lpc driver on Chromebook devices that
does not have the GOOG0004 ACPI entry.
- On Oct 5, 2017, at 8:24 AM, Peter Zijlstra pet...@infradead.org wrote:
> On Thu, Oct 05, 2017 at 02:12:50PM +0200, Peter Zijlstra wrote:
>> On Wed, Oct 04, 2017 at 02:37:53PM -0700, Paul E. McKenney wrote:
>> > diff --git a/arch/powerpc/kernel/membarrier.c
>> >
Hi,
This series enables a driver for a legacy accelerometer driver used on
Chromebook devices with older EC firmware.
In addition to the cros_ec_accel_legacy driver, this series contains a
fix that registers the cros_ec_lpc driver on Chromebook devices that
does not have the GOOG0004 ACPI entry.
With this patch, the cros_ec_ctl driver will register the legacy
accelerometer driver (named cros_ec_accel_legacy) if it fails to
register sensors through the usual path cros_ec_sensors_register().
This legacy device is present on Chromebook devices with older EC
firmware only supporting
From: Enric Balletbo i Serra
Commit 12278dc7c572 ("platform/chrome: cros_ec_lpc: Add support for
GOOG004 ACPI device") added support when the firmware reports the ACPI
device, there are some firmwares though that doesn't report this device
but have it. In such cases
With this patch, the cros_ec_ctl driver will register the legacy
accelerometer driver (named cros_ec_accel_legacy) if it fails to
register sensors through the usual path cros_ec_sensors_register().
This legacy device is present on Chromebook devices with older EC
firmware only supporting
From: Enric Balletbo i Serra
Commit 12278dc7c572 ("platform/chrome: cros_ec_lpc: Add support for
GOOG004 ACPI device") added support when the firmware reports the ACPI
device, there are some firmwares though that doesn't report this device
but have it. In such cases we need to instantiate the
Hi Vikas
On 09/29/2017 12:51 AM, Vikas Manocha wrote:
stm32 uart driver is using two compatible strings "st,stm32-usart"
& "st,stm32-uart". One can be removed safely to save some space & time.
Vikas Manocha (3):
Arm: dts: stm32: remove extra compatible string for uart
Arm: dts: stm32:
Hi Vikas
On 09/29/2017 12:51 AM, Vikas Manocha wrote:
stm32 uart driver is using two compatible strings "st,stm32-usart"
& "st,stm32-uart". One can be removed safely to save some space & time.
Vikas Manocha (3):
Arm: dts: stm32: remove extra compatible string for uart
Arm: dts: stm32:
- On Oct 5, 2017, at 8:12 AM, Peter Zijlstra pet...@infradead.org wrote:
> On Wed, Oct 04, 2017 at 02:37:53PM -0700, Paul E. McKenney wrote:
>> diff --git a/arch/powerpc/kernel/membarrier.c
>> b/arch/powerpc/kernel/membarrier.c
>> new file mode 100644
>> index ..b0d79a5f5981
>>
- On Oct 5, 2017, at 8:12 AM, Peter Zijlstra pet...@infradead.org wrote:
> On Wed, Oct 04, 2017 at 02:37:53PM -0700, Paul E. McKenney wrote:
>> diff --git a/arch/powerpc/kernel/membarrier.c
>> b/arch/powerpc/kernel/membarrier.c
>> new file mode 100644
>> index ..b0d79a5f5981
>>
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> Some boards have had node names with underscores. Remove them in favour of
> hyphens in order to reduce the DTC warnings.
>
> Signed-off-by: Maxime Ripard
> ---
>
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> Some boards have had node names with underscores. Remove them in favour of
> hyphens in order to reduce the DTC warnings.
>
> Signed-off-by: Maxime Ripard
> ---
> arch/arm/boot/dts/sun9i-a80-cubieboard4.dts | 8
>
On Thu, Oct 05, 2017 at 05:23:20PM +0200, Thomas Gleixner wrote:
> On Thu, 5 Oct 2017, Daniel Vetter wrote:
>
> > 4.14-rc1 gained the fancy new cross-release support in lockdep, which
> > seems to have uncovered a few more rules about what is allowed and
> > isn't.
> >
> > This one here seems to
On Thu, Oct 05, 2017 at 05:23:20PM +0200, Thomas Gleixner wrote:
> On Thu, 5 Oct 2017, Daniel Vetter wrote:
>
> > 4.14-rc1 gained the fancy new cross-release support in lockdep, which
> > seems to have uncovered a few more rules about what is allowed and
> > isn't.
> >
> > This one here seems to
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> Some node names in the A80 DTSI still have underscores in them. Remove them
> in favour of hyphens to remove DTC warnings.
>
> Signed-off-by: Maxime Ripard
> ---
>
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> Some node names in the A80 DTSI still have underscores in them. Remove them
> in favour of hyphens to remove DTC warnings.
>
> Signed-off-by: Maxime Ripard
> ---
> arch/arm/boot/dts/sun9i-a80.dtsi | 10 +-
> 1 file changed, 5
On Thursday 05 October 2017 17:44:45 Greg KH wrote:
> On Thu, Oct 05, 2017 at 02:22:37PM +, mario.limoncie...@dell.com wrote:
> > > -Original Message-
> > > From: Alan Cox [mailto:gno...@lxorguk.ukuu.org.uk]
> > > Sent: Thursday, October 5, 2017 8:59 AM
> > > To: Limonciello, Mario
On Thursday 05 October 2017 17:44:45 Greg KH wrote:
> On Thu, Oct 05, 2017 at 02:22:37PM +, mario.limoncie...@dell.com wrote:
> > > -Original Message-
> > > From: Alan Cox [mailto:gno...@lxorguk.ukuu.org.uk]
> > > Sent: Thursday, October 5, 2017 8:59 AM
> > > To: Limonciello, Mario
>
On Thu, 5 Oct 2017 10:37:59 -0500
Julia Cartwright wrote:
> On Thu, Oct 05, 2017 at 05:27:30PM +0200, Thomas Gleixner wrote:
> > On Thu, 5 Oct 2017, Julia Cartwright wrote:
> > > On Tue, Oct 03, 2017 at 12:49:19PM -0300, Arnaldo Carvalho de Melo wrote:
> > >
> > > > -
On Thu, 5 Oct 2017 10:37:59 -0500
Julia Cartwright wrote:
> On Thu, Oct 05, 2017 at 05:27:30PM +0200, Thomas Gleixner wrote:
> > On Thu, 5 Oct 2017, Julia Cartwright wrote:
> > > On Tue, Oct 03, 2017 at 12:49:19PM -0300, Arnaldo Carvalho de Melo wrote:
> > >
> > > > -
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> Our pinctrl node names were containing unit-adresses without a reg
> property, resulting in a warning. Change the names for our new convention.
>
> Signed-off-by: Maxime Ripard
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> Our pinctrl node names were containing unit-adresses without a reg
> property, resulting in a warning. Change the names for our new convention.
>
> Signed-off-by: Maxime Ripard
Acked-by: Chen-Yu Tsai
On 2017-10-04 18:07:59 [+0200], Mike Galbraith wrote:
> Seems combo-patch induced some ltp posix conformance test grumbling.
>
> +clock_settime_8_1 ... ... FAILED
> +clock_settime_4_2 ... ... FAILED
> +clock_settime_speculative_4_3 ... ... FAILED
> +timer_settime_5_2 ... ... FAILED
>
On 2017-10-04 18:07:59 [+0200], Mike Galbraith wrote:
> Seems combo-patch induced some ltp posix conformance test grumbling.
>
> +clock_settime_8_1 ... ... FAILED
> +clock_settime_4_2 ... ... FAILED
> +clock_settime_speculative_4_3 ... ... FAILED
> +timer_settime_5_2 ... ... FAILED
>
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> The board has an external pull-up on the card-detect signal, so there's no
> need to add another one.
>
> This also removes a DTC warning.
>
> Signed-off-by: Maxime Ripard
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> The board has an external pull-up on the card-detect signal, so there's no
> need to add another one.
>
> This also removes a DTC warning.
>
> Signed-off-by: Maxime Ripard
Acked-by: Chen-Yu Tsai
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> The board has an external pull-up on the card-detect signal, so there's no
> need to add another one.
>
> This also removes a DTC warning.
>
> Signed-off-by: Maxime Ripard
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> The board has an external pull-up on the card-detect signal, so there's no
> need to add another one.
>
> This also removes a DTC warning.
>
> Signed-off-by: Maxime Ripard
Acked-by: Chen-Yu Tsai
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> The A80 boards still define some GPIO pinctrl nodes that are not really
> useful, and redundant with the muxing already happening on gpio_request.
>
> Let's remove those nodes. This will also remove DTC
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> The A80 boards still define some GPIO pinctrl nodes that are not really
> useful, and redundant with the muxing already happening on gpio_request.
>
> Let's remove those nodes. This will also remove DTC warnings.
>
> Signed-off-by: Maxime
- On Oct 5, 2017, at 8:22 AM, Avi Kivity a...@scylladb.com wrote:
> On 10/05/2017 07:23 AM, Nicholas Piggin wrote:
>> On Wed, 4 Oct 2017 14:37:53 -0700
>> "Paul E. McKenney" wrote:
>>
>>> From: Mathieu Desnoyers
>>>
>>> Provide a
- On Oct 5, 2017, at 8:22 AM, Avi Kivity a...@scylladb.com wrote:
> On 10/05/2017 07:23 AM, Nicholas Piggin wrote:
>> On Wed, 4 Oct 2017 14:37:53 -0700
>> "Paul E. McKenney" wrote:
>>
>>> From: Mathieu Desnoyers
>>>
>>> Provide a new command allowing processes to register their intent to
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> One of the usage of the LRADC is to implement buttons. The bindings define
> that we should have one subnode per button, with their associated voltage
> as a property.
>
> However, there was no reg property
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> One of the usage of the LRADC is to implement buttons. The bindings define
> that we should have one subnode per button, with their associated voltage
> as a property.
>
> However, there was no reg property but we still used the voltage
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> Using skeleton.dtsi will create a memory node that will generate a warning
> in DTC. However, that node will be created by the bootloader, so we can
> just remove it entirely in order to remove that warning.
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> Using skeleton.dtsi will create a memory node that will generate a warning
> in DTC. However, that node will be created by the bootloader, so we can
> just remove it entirely in order to remove that warning.
>
> Signed-off-by: Maxime Ripard
Hello, Michal.
On Thu, Oct 05, 2017 at 03:14:19PM +0200, Michal Hocko wrote:
> Yes and that is why I think a boot time knob would be the most simple
> way. It will also open doors for more oom policies in future which I
> believe come sooner or later.
While boot params are fine for development
- On Oct 5, 2017, at 12:23 AM, Nicholas Piggin npig...@gmail.com wrote:
> On Wed, 4 Oct 2017 14:37:53 -0700
> "Paul E. McKenney" wrote:
>
>> From: Mathieu Desnoyers
>>
>> Provide a new command allowing processes to register
- On Oct 5, 2017, at 12:23 AM, Nicholas Piggin npig...@gmail.com wrote:
> On Wed, 4 Oct 2017 14:37:53 -0700
> "Paul E. McKenney" wrote:
>
>> From: Mathieu Desnoyers
>>
>> Provide a new command allowing processes to register their intent to use
>> the private expedited command.
>>
>>
Hello, Michal.
On Thu, Oct 05, 2017 at 03:14:19PM +0200, Michal Hocko wrote:
> Yes and that is why I think a boot time knob would be the most simple
> way. It will also open doors for more oom policies in future which I
> believe come sooner or later.
While boot params are fine for development
On Thursday 05 October 2017 17:42:14 Greg KH wrote:
> > > > --- /dev/null
> > > > +++ b/include/uapi/linux/wmi.h
> > > > @@ -0,0 +1,10 @@
> > > > +#ifndef _UAPI_LINUX_WMI_H
> > > > +#define _UAPI_LINUX_WMI_H
> > > > +
> > > > +#define WMI_IOC 'W'
> > > > +#define WMI_IO(instance)
On Thursday 05 October 2017 17:42:14 Greg KH wrote:
> > > > --- /dev/null
> > > > +++ b/include/uapi/linux/wmi.h
> > > > @@ -0,0 +1,10 @@
> > > > +#ifndef _UAPI_LINUX_WMI_H
> > > > +#define _UAPI_LINUX_WMI_H
> > > > +
> > > > +#define WMI_IOC 'W'
> > > > +#define WMI_IO(instance)
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> Some gpio-keys definitions in our DTs were having buttons defined with a
> unit-address and that would generate a DTC warning.
>
> Change the buttons node names to remove the warnings.
>
> Signed-off-by:
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> Some gpio-keys definitions in our DTs were having buttons defined with a
> unit-address and that would generate a DTC warning.
>
> Change the buttons node names to remove the warnings.
>
> Signed-off-by: Maxime Ripard
> ---
>
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> Some GPIO pinctrl nodes cannot be easily removed, because they would also
> change the pin configuration, for example to add a pull resistor or change
> the current delivered by the pin.
>
> Those nodes still
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> Some GPIO pinctrl nodes cannot be easily removed, because they would also
> change the pin configuration, for example to add a pull resistor or change
> the current delivered by the pin.
>
> Those nodes still have underscores and
On Thu, 5 Oct 2017 16:50:27 +0200
Vitaly Kuznetsov wrote:
> Changes since v2:
> - Use DEFINE_EVENT in PATCH1/2 to avoid compile warnings [Stephen Hemminger]
> - Add PATCH17 tracing channel events [Stephen Hemminger]
>
> Messages between guest and host are used in Hyper-V
On Thu, 5 Oct 2017 16:50:27 +0200
Vitaly Kuznetsov wrote:
> Changes since v2:
> - Use DEFINE_EVENT in PATCH1/2 to avoid compile warnings [Stephen Hemminger]
> - Add PATCH17 tracing channel events [Stephen Hemminger]
>
> Messages between guest and host are used in Hyper-V as control flow. To
>
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> The gpio pinctrl nodes are redundant and as such useless most of the times.
> Since they will also generate warnings in DTC, we can simply remove most of
> them.
>
> Signed-off-by: Maxime Ripard
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> The gpio pinctrl nodes are redundant and as such useless most of the times.
> Since they will also generate warnings in DTC, we can simply remove most of
> them.
>
> Signed-off-by: Maxime Ripard
Acked-by: Chen-Yu Tsai
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> The thermal-zone subnodes we defined for the A10 have underscores in them
> that will generate DTC warnings. Change those underscores for hyphens.
>
> Signed-off-by: Maxime Ripard
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> The thermal-zone subnodes we defined for the A10 have underscores in them
> that will generate DTC warnings. Change those underscores for hyphens.
>
> Signed-off-by: Maxime Ripard
Acked-by: Chen-Yu Tsai
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> Our main node for all the in-SoC controllers used to have a unit name. The
> unit-name, in addition to being actually false, would not match any reg
> property, which generates a warning.
>
> Remove it in
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> Our main node for all the in-SoC controllers used to have a unit name. The
> unit-name, in addition to being actually false, would not match any reg
> property, which generates a warning.
>
> Remove it in order to remove those warnings.
>
>
On Thu, Oct 05, 2017 at 02:22:37PM +, mario.limoncie...@dell.com wrote:
> > -Original Message-
> > From: Alan Cox [mailto:gno...@lxorguk.ukuu.org.uk]
> > Sent: Thursday, October 5, 2017 8:59 AM
> > To: Limonciello, Mario
> > Cc: dvh...@infradead.org; Andy
On Thu, Oct 05, 2017 at 02:22:37PM +, mario.limoncie...@dell.com wrote:
> > -Original Message-
> > From: Alan Cox [mailto:gno...@lxorguk.ukuu.org.uk]
> > Sent: Thursday, October 5, 2017 8:59 AM
> > To: Limonciello, Mario
> > Cc: dvh...@infradead.org; Andy Shevchenko ;
> > LKML ;
On 05/10/17 16:26, James Hogan wrote:
> On Thu, Oct 05, 2017 at 03:48:53PM +0100, Ed Blake wrote:
>>
>> I'm not sure how this is supposed to work, but the issue seems to be
>> that without this patch the parent irq isn't being masked. This is
>> causing the parent handler (MIPS GIC in this case)
On 05/10/17 16:26, James Hogan wrote:
> On Thu, Oct 05, 2017 at 03:48:53PM +0100, Ed Blake wrote:
>>
>> I'm not sure how this is supposed to work, but the issue seems to be
>> that without this patch the parent irq isn't being masked. This is
>> causing the parent handler (MIPS GIC in this case)
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> Using skeleton.dtsi will create a memory node that will generate a warning
> in DTC. However, that node will be created by the bootloader, so we can
> just remove it entirely in order to remove that warning.
On Thu, Oct 5, 2017 at 6:49 PM, Maxime Ripard
wrote:
> Using skeleton.dtsi will create a memory node that will generate a warning
> in DTC. However, that node will be created by the bootloader, so we can
> just remove it entirely in order to remove that warning.
>
> Signed-off-by: Maxime Ripard
UNSECURED BUSINESS/PERSONAL LOAN BY LOAN CAPITAL FINANCE
- NO COLLATERAL
- MINIMUM DOCUMENTATION
- BUSINESS LOAN UP TO FIVE(5) MILLION US DOLLARS
CONTACT US TODAY VIA EMAIL: financeloa...@hotmail.com
UNSECURED BUSINESS/PERSONAL LOAN BY LOAN CAPITAL FINANCE
- NO COLLATERAL
- MINIMUM DOCUMENTATION
- BUSINESS LOAN UP TO FIVE(5) MILLION US DOLLARS
CONTACT US TODAY VIA EMAIL: financeloa...@hotmail.com
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
rcu/next
head: 31f76cdc284fc45751d88b5ed754630a5f8a8914
commit: 3f4013e60f5eaf15913143831cfa8b8a2e2fbcb5 [33/34] Squash with
7202bfecfbec ("rcu: Pretend ->boost_mtx acquired legitimately")
config:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
rcu/next
head: 31f76cdc284fc45751d88b5ed754630a5f8a8914
commit: 3f4013e60f5eaf15913143831cfa8b8a2e2fbcb5 [33/34] Squash with
7202bfecfbec ("rcu: Pretend ->boost_mtx acquired legitimately")
config:
On Thu, Oct 05, 2017 at 02:35:43PM +, mario.limoncie...@dell.com wrote:
> >
> > > + strcpy(buf, "wmi/");
> > > + strcpy(buf + 4, wdriver->driver.name);
> > > + wblock->misc_dev.minor = MISC_DYNAMIC_MINOR;
> > > + wblock->misc_dev.name = buf;
> > > +
On Thu, Oct 05, 2017 at 02:35:43PM +, mario.limoncie...@dell.com wrote:
> >
> > > + strcpy(buf, "wmi/");
> > > + strcpy(buf + 4, wdriver->driver.name);
> > > + wblock->misc_dev.minor = MISC_DYNAMIC_MINOR;
> > > + wblock->misc_dev.name = buf;
> > > +
From: Markus Elfring
Date: Thu, 5 Oct 2017 17:18:33 +0200
Replace the specification of data structures by pointer dereferences
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style
From: Markus Elfring
Date: Thu, 5 Oct 2017 17:18:33 +0200
Replace the specification of data structures by pointer dereferences
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
This issue was
On 09/18/2017 02:20 PM, Waiman Long wrote:
>
> A rogue application can potentially create a large number of negative
> dentries in the system consuming most of the memory available even if
> memory controller is enabled to limit memory usage. This can impact
> performance of other applications
On 09/18/2017 02:20 PM, Waiman Long wrote:
>
> A rogue application can potentially create a large number of negative
> dentries in the system consuming most of the memory available even if
> memory controller is enabled to limit memory usage. This can impact
> performance of other applications
From: Markus Elfring
Date: Thu, 5 Oct 2017 17:10:11 +0200
Omit extra messages for a memory allocation failure in these functions.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
From: Markus Elfring
Date: Thu, 5 Oct 2017 17:10:11 +0200
Omit extra messages for a memory allocation failure in these functions.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
arch/powerpc/oprofile/cell/spu_task_sync.c | 8
From: Markus Elfring
Date: Thu, 5 Oct 2017 17:32:10 +0200
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation in three functions
Improve a size
From: Markus Elfring
Date: Thu, 5 Oct 2017 17:32:10 +0200
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation in three functions
Improve a size determination in two functions
901 - 1000 of 1942 matches
Mail list logo