Use the appropriate SPDX license identifier and drop the license text.
This patch is only cosmetic.
Signed-off-by: Antoine Tenart
---
drivers/phy/marvell/phy-berlin-usb.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/phy/marvell/phy-berlin-usb.c
Use the appropriate SPDX license identifier and drop the license text.
This patch is only cosmetic.
Signed-off-by: Antoine Tenart
---
drivers/phy/marvell/phy-berlin-usb.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/phy/marvell/phy-berlin-usb.c
On Fri, Jul 13, 2018 at 05:33:51PM +0200, Greg Kroah-Hartman wrote:
> On Fri, Jul 13, 2018 at 05:06:37PM +0200, Arnd Bergmann wrote:
> > A new user of the deprecated current_kernel_time() function has appeared
> > here. This code won't work correct during leap seconds or a concurrent
> >
On Fri, Jul 13, 2018 at 05:33:51PM +0200, Greg Kroah-Hartman wrote:
> On Fri, Jul 13, 2018 at 05:06:37PM +0200, Arnd Bergmann wrote:
> > A new user of the deprecated current_kernel_time() function has appeared
> > here. This code won't work correct during leap seconds or a concurrent
> >
On Fri, 2018-07-13 at 16:17 +0300, Aapo Vienamo wrote:
> Implement and use tegra_sdhci_get_max_clock() which returns the true
> maximum host clock rate. The issue with tegra_sdhci_get_max_clock()
> is
> that it returns the current clock rate of the host instead of the
> maximum one, which can lead
On Fri, 2018-07-13 at 16:17 +0300, Aapo Vienamo wrote:
> Implement and use tegra_sdhci_get_max_clock() which returns the true
> maximum host clock rate. The issue with tegra_sdhci_get_max_clock()
> is
> that it returns the current clock rate of the host instead of the
> maximum one, which can lead
Andy Lutomirski wrote:
> > Whilst I'm at it, do we want the option of doing the equivalent of
> > mountat()? I.e. offering the option to open all the device files used by
> > a superblock with dfd and AT_* flags in combination with the filename?
> >
>
> Isn't that more or less what I was
Andy Lutomirski wrote:
> > Whilst I'm at it, do we want the option of doing the equivalent of
> > mountat()? I.e. offering the option to open all the device files used by
> > a superblock with dfd and AT_* flags in combination with the filename?
> >
>
> Isn't that more or less what I was
Now that the component framework is integrated into the ASoC core,
remove any redundant code in this driver.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/qdsp6/q6afe-dai.c | 34 --
1 file changed, 4 insertions(+), 30 deletions(-)
diff --git
Now that the component framework is integrated into the ASoC core,
remove any redundant code in this driver.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/qdsp6/q6asm-dai.c | 35 ---
1 file changed, 4 insertions(+), 31 deletions(-)
diff --git
Now that the component framework is integrated into the ASoC core,
remove any redundant code in this driver.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/qdsp6/q6afe-dai.c | 34 --
1 file changed, 4 insertions(+), 30 deletions(-)
diff --git
Now that the component framework is integrated into the ASoC core,
remove any redundant code in this driver.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/qdsp6/q6asm-dai.c | 35 ---
1 file changed, 4 insertions(+), 31 deletions(-)
diff --git
On Fri, 13 Jul 2018 15:01:21 +0100
Jon Hunter wrote:
> On 13/07/18 14:17, Aapo Vienamo wrote:
> > Implement and use tegra_sdhci_get_max_clock() which returns the true
> > maximum host clock rate. The issue with tegra_sdhci_get_max_clock() is
>
> Don't you mean sdhci_pltfm_clk_get_max_clock
On Fri, 13 Jul 2018 15:01:21 +0100
Jon Hunter wrote:
> On 13/07/18 14:17, Aapo Vienamo wrote:
> > Implement and use tegra_sdhci_get_max_clock() which returns the true
> > maximum host clock rate. The issue with tegra_sdhci_get_max_clock() is
>
> Don't you mean sdhci_pltfm_clk_get_max_clock
Now that the component framework is integrated into the ASoC core,
remove any redundant code in this driver.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/apq8096.c | 75
1 file changed, 6 insertions(+), 69 deletions(-)
diff --git
On Thu, 2018-07-12 at 09:39 +0200, Stefan Agner wrote:
> The stack assumes that SDHC controller which support SD3.0 (SDR104)
> do
> support HS200. This is not the case for Tegra 3, which does support
> SD
> 3.0
> but only supports eMMC spec 4.41.
>
> Use SDHCI_QUIRK2_BROKEN_HS200 to indicate that
This patch aims at achieving dynamic behaviour of audio card when
the dependent components disappear and reappear.
With this patch the card is removed if any of the dependent component
is removed and card is added back if the dependent component comes back.
All this is done using component
During discussion regarding card re-binding when components unregister
and register back at https://lkml.org/lkml/2018/7/9/785 it was suggested
that component framework can be added into core to provide this feature.
With this new changes the card will re-bind once the dependent component
Now that the component framework is integrated into the ASoC core,
remove any redundant code in this driver.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/qdsp6/q6routing.c | 32 ++--
1 file changed, 6 insertions(+), 26 deletions(-)
diff --git
Now that the component framework is integrated into the ASoC core,
remove any redundant code in this driver.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/apq8096.c | 75
1 file changed, 6 insertions(+), 69 deletions(-)
diff --git
On Thu, 2018-07-12 at 09:39 +0200, Stefan Agner wrote:
> The stack assumes that SDHC controller which support SD3.0 (SDR104)
> do
> support HS200. This is not the case for Tegra 3, which does support
> SD
> 3.0
> but only supports eMMC spec 4.41.
>
> Use SDHCI_QUIRK2_BROKEN_HS200 to indicate that
This patch aims at achieving dynamic behaviour of audio card when
the dependent components disappear and reappear.
With this patch the card is removed if any of the dependent component
is removed and card is added back if the dependent component comes back.
All this is done using component
During discussion regarding card re-binding when components unregister
and register back at https://lkml.org/lkml/2018/7/9/785 it was suggested
that component framework can be added into core to provide this feature.
With this new changes the card will re-bind once the dependent component
Now that the component framework is integrated into the ASoC core,
remove any redundant code in this driver.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/qdsp6/q6routing.c | 32 ++--
1 file changed, 6 insertions(+), 26 deletions(-)
diff --git
Use new return type vm_fault_t for fault handler. For now,
this is just documenting that the function returns a
VM_FAULT value rather than an errno. Once all instances are
converted, vm_fault_t will become a distinct type.
Ref-> commit 1c8f422059ae ("mm: change return type to
vm_fault_t") was
Use new return type vm_fault_t for fault handler. For now,
this is just documenting that the function returns a
VM_FAULT value rather than an errno. Once all instances are
converted, vm_fault_t will become a distinct type.
Ref-> commit 1c8f422059ae ("mm: change return type to
vm_fault_t") was
On Fri, Jul 13, 2018 at 05:06:37PM +0200, Arnd Bergmann wrote:
> A new user of the deprecated current_kernel_time() function has appeared
> here. This code won't work correct during leap seconds or a concurrent
> settimeofday() call, and it probably doesn't do what the author intended
> even for
On Fri, Jul 13, 2018 at 05:06:37PM +0200, Arnd Bergmann wrote:
> A new user of the deprecated current_kernel_time() function has appeared
> here. This code won't work correct during leap seconds or a concurrent
> settimeofday() call, and it probably doesn't do what the author intended
> even for
Hi Agustin,
On Thu, Jul 05, 2018 at 04:23:17PM -0400, Agustin Vega-Frias wrote:
> This series is a complete re-design of V1 of the QCOM Falkor extensions [1],
> it introduces a probe table based on the HID of a device nested under the CPU
> device to allow variant detection and arm_pmu
Hi Agustin,
On Thu, Jul 05, 2018 at 04:23:17PM -0400, Agustin Vega-Frias wrote:
> This series is a complete re-design of V1 of the QCOM Falkor extensions [1],
> it introduces a probe table based on the HID of a device nested under the CPU
> device to allow variant detection and arm_pmu
Not all toolchains have the baremetal elf targets, RedHat/Fedora ones
in particular. So, probe for whether it's available and use the previous
(linux) targets if it isn't.
Reported-by: Laura Abbott
Cc: Paul Kocialkowski
Signed-off-by: Olof Johansson
---
arch/arm64/Makefile| 9 +
Not all toolchains have the baremetal elf targets, RedHat/Fedora ones
in particular. So, probe for whether it's available and use the previous
(linux) targets if it isn't.
Reported-by: Laura Abbott
Cc: Paul Kocialkowski
Signed-off-by: Olof Johansson
---
arch/arm64/Makefile| 9 +
+ Dan
On Fri, Jul 13 2018 at 07:46 -0600, Raju P L S S S N wrote:
From: "Raju P.L.S.S.S.N"
The patch fixes the bug reported by Dan Carpenter.
It removes the unnecessary err check for ‘tcs’ reported by
static checker warning:
drivers/soc/qcom/rpmh-rsc.c:111 tcs_invalidate()
warn: 'tcs' isn't
+ Dan
On Fri, Jul 13 2018 at 07:46 -0600, Raju P L S S S N wrote:
From: "Raju P.L.S.S.S.N"
The patch fixes the bug reported by Dan Carpenter.
It removes the unnecessary err check for ‘tcs’ reported by
static checker warning:
drivers/soc/qcom/rpmh-rsc.c:111 tcs_invalidate()
warn: 'tcs' isn't
Date: Fri, 13 Jul 2018 15:52:35 +0200
Add a log message to `run_init_process()`.
This log message serves two purposes.
1. If the init process is not specified on the Linux Kernel command
line, the user sees, what file was chosen.
2. The time stamps shows exactly, when the Linux kernel
Date: Fri, 13 Jul 2018 15:52:35 +0200
Add a log message to `run_init_process()`.
This log message serves two purposes.
1. If the init process is not specified on the Linux Kernel command
line, the user sees, what file was chosen.
2. The time stamps shows exactly, when the Linux kernel
Andrew, Ben, first of all let me thank you for bringing in this set of
patches.
From the discussion it looks to me like Rob is not familiar with
specifics of BMC-managed servers and tries to apply to them the rules
that have proven to be good for workstations and laptops.
As someone using
Andrew, Ben, first of all let me thank you for bringing in this set of
patches.
From the discussion it looks to me like Rob is not familiar with
specifics of BMC-managed servers and tries to apply to them the rules
that have proven to be good for workstations and laptops.
As someone using
On Fri, Jul 13, 2018 at 8:07 AM, Will Deacon wrote:
> Hi Olof,
>
> On Fri, Jul 13, 2018 at 07:59:10AM -0700, Olof Johansson wrote:
>> On Tue, Jul 10, 2018 at 10:36:16AM +0100, Will Deacon wrote:
>> > On Tue, Jul 10, 2018 at 11:30:39AM +0200, Paul Kocialkowski wrote:
>> > > On Tue, 2018-07-10 at
On Fri, Jul 13, 2018 at 8:07 AM, Will Deacon wrote:
> Hi Olof,
>
> On Fri, Jul 13, 2018 at 07:59:10AM -0700, Olof Johansson wrote:
>> On Tue, Jul 10, 2018 at 10:36:16AM +0100, Will Deacon wrote:
>> > On Tue, Jul 10, 2018 at 11:30:39AM +0200, Paul Kocialkowski wrote:
>> > > On Tue, 2018-07-10 at
The RTC in the JZ4725B works just like the one in the JZ4740.
The RTC in the JZ4760 and JZ4770 work just like the one in the JZ4780.
Signed-off-by: Paul Cercueil
---
Documentation/devicetree/bindings/rtc/ingenic,jz4740-rtc.txt | 3 +++
drivers/rtc/rtc-jz4740.c
The RTC in the JZ4725B works just like the one in the JZ4740.
The RTC in the JZ4760 and JZ4770 work just like the one in the JZ4780.
Signed-off-by: Paul Cercueil
---
Documentation/devicetree/bindings/rtc/ingenic,jz4740-rtc.txt | 3 +++
drivers/rtc/rtc-jz4740.c
Hi,
On Fri, 2018-07-13 at 08:01 -0700, Olof Johansson wrote:
> On Fri, Jul 13, 2018 at 7:59 AM, Olof Johansson wrote:
> > On Tue, Jul 10, 2018 at 10:36:16AM +0100, Will Deacon wrote:
> > > On Tue, Jul 10, 2018 at 11:30:39AM +0200, Paul Kocialkowski wrote:
> > > > On Tue, 2018-07-10 at 10:01
Hi,
On Fri, 2018-07-13 at 08:01 -0700, Olof Johansson wrote:
> On Fri, Jul 13, 2018 at 7:59 AM, Olof Johansson wrote:
> > On Tue, Jul 10, 2018 at 10:36:16AM +0100, Will Deacon wrote:
> > > On Tue, Jul 10, 2018 at 11:30:39AM +0200, Paul Kocialkowski wrote:
> > > > On Tue, 2018-07-10 at 10:01
The SCMI protocol can be used to get power estimates from firmware
corresponding to each performance state of a device. Although these power
costs are already managed by the SCMI firmware driver, they are not
exposed to any external subsystem yet.
Fix this by adding a new get_power() interface to
The SCMI protocol can be used to get power estimates from firmware
corresponding to each performance state of a device. Although these power
costs are already managed by the SCMI firmware driver, they are not
exposed to any external subsystem yet.
Fix this by adding a new get_power() interface to
A new user of the deprecated current_kernel_time() function has appeared
here. This code won't work correct during leap seconds or a concurrent
settimeofday() call, and it probably doesn't do what the author intended
even for the normal case, as it passes a timeout in nanoseconds but
reads the
A new user of the deprecated current_kernel_time() function has appeared
here. This code won't work correct during leap seconds or a concurrent
settimeofday() call, and it probably doesn't do what the author intended
even for the normal case, as it passes a timeout in nanoseconds but
reads the
Hi Olof,
On Fri, Jul 13, 2018 at 07:59:10AM -0700, Olof Johansson wrote:
> On Tue, Jul 10, 2018 at 10:36:16AM +0100, Will Deacon wrote:
> > On Tue, Jul 10, 2018 at 11:30:39AM +0200, Paul Kocialkowski wrote:
> > > On Tue, 2018-07-10 at 10:01 +0100, Will Deacon wrote:
> > > > Thanks, Laura.
> > > >
Hi Olof,
On Fri, Jul 13, 2018 at 07:59:10AM -0700, Olof Johansson wrote:
> On Tue, Jul 10, 2018 at 10:36:16AM +0100, Will Deacon wrote:
> > On Tue, Jul 10, 2018 at 11:30:39AM +0200, Paul Kocialkowski wrote:
> > > On Tue, 2018-07-10 at 10:01 +0100, Will Deacon wrote:
> > > > Thanks, Laura.
> > > >
Hi Hans,
On Fri, 2018-07-13 at 11:08 +0200, Hans de Goede wrote:
> Hi,
>
> On 13-07-18 00:27, Srinivas Pandruvada wrote:
> > Currently when min_power policy is selected, the partial low power
> > state
> > is not entered and link will try aggressively enter to only slumber
> > state.
> > Add a
Hi Hans,
On Fri, 2018-07-13 at 11:08 +0200, Hans de Goede wrote:
> Hi,
>
> On 13-07-18 00:27, Srinivas Pandruvada wrote:
> > Currently when min_power policy is selected, the partial low power
> > state
> > is not entered and link will try aggressively enter to only slumber
> > state.
> > Add a
On Fri, Jul 06, 2018 at 03:21:24PM +0200, Peter Zijlstra wrote:
> On Fri, Jul 06, 2018 at 02:16:04PM +0100, Will Deacon wrote:
> > On Thu, Jul 05, 2018 at 05:40:41PM +0100, Mark Rutland wrote:
> > > This series scripts the generation of the various atomic headers, to
> > > ensure
> > > that the
On Fri, Jul 06, 2018 at 03:21:24PM +0200, Peter Zijlstra wrote:
> On Fri, Jul 06, 2018 at 02:16:04PM +0100, Will Deacon wrote:
> > On Thu, Jul 05, 2018 at 05:40:41PM +0100, Mark Rutland wrote:
> > > This series scripts the generation of the various atomic headers, to
> > > ensure
> > > that the
> On Jul 13, 2018, at 6:27 AM, David Howells wrote:
>
> Whilst I'm at it, do we want the option of doing the equivalent of mountat()?
> I.e. offering the option to open all the device files used by a superblock
> with dfd and AT_* flags in combination with the filename?
>
Isn’t that more or
> On Jul 13, 2018, at 6:27 AM, David Howells wrote:
>
> Whilst I'm at it, do we want the option of doing the equivalent of mountat()?
> I.e. offering the option to open all the device files used by a superblock
> with dfd and AT_* flags in combination with the filename?
>
Isn’t that more or
On Fri, Jul 13, 2018 at 7:59 AM, Olof Johansson wrote:
> On Tue, Jul 10, 2018 at 10:36:16AM +0100, Will Deacon wrote:
>> On Tue, Jul 10, 2018 at 11:30:39AM +0200, Paul Kocialkowski wrote:
>> > On Tue, 2018-07-10 at 10:01 +0100, Will Deacon wrote:
>> > > Thanks, Laura.
>> > >
>> > > I'll take this
On Fri, Jul 13, 2018 at 7:59 AM, Olof Johansson wrote:
> On Tue, Jul 10, 2018 at 10:36:16AM +0100, Will Deacon wrote:
>> On Tue, Jul 10, 2018 at 11:30:39AM +0200, Paul Kocialkowski wrote:
>> > On Tue, 2018-07-10 at 10:01 +0100, Will Deacon wrote:
>> > > Thanks, Laura.
>> > >
>> > > I'll take this
On Tue, Jul 10, 2018 at 10:36:16AM +0100, Will Deacon wrote:
> On Tue, Jul 10, 2018 at 11:30:39AM +0200, Paul Kocialkowski wrote:
> > On Tue, 2018-07-10 at 10:01 +0100, Will Deacon wrote:
> > > Thanks, Laura.
> > >
> > > I'll take this as a fix, and add a comment to the Makefile to justify
> > >
On Tue, Jul 10, 2018 at 10:36:16AM +0100, Will Deacon wrote:
> On Tue, Jul 10, 2018 at 11:30:39AM +0200, Paul Kocialkowski wrote:
> > On Tue, 2018-07-10 at 10:01 +0100, Will Deacon wrote:
> > > Thanks, Laura.
> > >
> > > I'll take this as a fix, and add a comment to the Makefile to justify
> > >
2018-07-12 20:32 GMT+09:00 Dirk Gouders :
> Masahiro Yamada writes:
>
>> 2018-07-09 20:39 GMT+09:00 Dirk Gouders :
>>> Dirk Gouders writes:
>>>
Dirk Gouders writes:
> Masahiro Yamada writes:
>
>> syncconfig updates the .config only when sym_change_count > 0, i.e.
>>
2018-07-12 20:32 GMT+09:00 Dirk Gouders :
> Masahiro Yamada writes:
>
>> 2018-07-09 20:39 GMT+09:00 Dirk Gouders :
>>> Dirk Gouders writes:
>>>
Dirk Gouders writes:
> Masahiro Yamada writes:
>
>> syncconfig updates the .config only when sym_change_count > 0, i.e.
>>
On 07/12/2018 10:17 AM, Joel Fernandes wrote:
On Wed, Jul 11, 2018 at 10:43:28AM +0200, Dietmar Eggemann wrote:
On 07/11/2018 01:09 AM, Joel Fernandes wrote:
On Mon, Jul 09, 2018 at 05:47:53PM +0100, Dietmar Eggemann wrote:
A CFS (SCHED_OTHER, SCHED_BATCH or SCHED_IDLE policy) task's
On 07/12/2018 10:17 AM, Joel Fernandes wrote:
On Wed, Jul 11, 2018 at 10:43:28AM +0200, Dietmar Eggemann wrote:
On 07/11/2018 01:09 AM, Joel Fernandes wrote:
On Mon, Jul 09, 2018 at 05:47:53PM +0100, Dietmar Eggemann wrote:
A CFS (SCHED_OTHER, SCHED_BATCH or SCHED_IDLE policy) task's
Use the appropriate SPDX license identifier and drop the license text.
This patch is only cosmetic.
Signed-off-by: Antoine Tenart
---
drivers/phy/marvell/phy-mvebu-cp110-comphy.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/phy/marvell/phy-mvebu-cp110-comphy.c
Use the appropriate SPDX license identifier and drop the license text.
This patch is only cosmetic.
Signed-off-by: Antoine Tenart
---
drivers/phy/marvell/phy-mvebu-cp110-comphy.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/phy/marvell/phy-mvebu-cp110-comphy.c
On Wed, Jul 11, 2018 at 11:09 AM, Colin King wrote:
> From: Colin Ian King
>
> Variables slope and offset are being assigned but are never used hence
> they are redundant and can be removed.
>
Sounds like some half-baked calculus and perhaps would be fixed
better. Though, no one complained so
On Wed, Jul 11, 2018 at 11:09 AM, Colin King wrote:
> From: Colin Ian King
>
> Variables slope and offset are being assigned but are never used hence
> they are redundant and can be removed.
>
Sounds like some half-baked calculus and perhaps would be fixed
better. Though, no one complained so
Oleg Nesterov writes:
> That is why I tried to sugest another approach. copy_process() should always
> fail
> if signal_pending() == T, just the "real" signal should not disturb the
> forking
> thread unless the signal is fatal or multi-process.
I understand now why you are suggesting another
Oleg Nesterov writes:
> That is why I tried to sugest another approach. copy_process() should always
> fail
> if signal_pending() == T, just the "real" signal should not disturb the
> forking
> thread unless the signal is fatal or multi-process.
I understand now why you are suggesting another
The interrupt controller of the JZ4725B works the same way as the other
JZ SoCs from Ingenic; so we just add a new compatible string.
Signed-off-by: Paul Cercueil
---
Documentation/devicetree/bindings/interrupt-controller/ingenic,intc.txt | 1 +
drivers/irqchip/irq-ingenic.c
The interrupt controller of the JZ4725B works the same way as the other
JZ SoCs from Ingenic; so we just add a new compatible string.
Signed-off-by: Paul Cercueil
---
Documentation/devicetree/bindings/interrupt-controller/ingenic,intc.txt | 1 +
drivers/irqchip/irq-ingenic.c
The UART in the jz4725b works just like in the other JZ SoCs, so this
commit simply adds a new compatible string.
Signed-off-by: Paul Cercueil
---
Documentation/devicetree/bindings/serial/ingenic,uart.txt | 1 +
drivers/tty/serial/8250/8250_ingenic.c| 5 +
2 files
The UART in the jz4725b works just like in the other JZ SoCs, so this
commit simply adds a new compatible string.
Signed-off-by: Paul Cercueil
---
Documentation/devicetree/bindings/serial/ingenic,uart.txt | 1 +
drivers/tty/serial/8250/8250_ingenic.c| 5 +
2 files
Sounds good. I'll keep an eye out for your patch set and try it on my
boards as well. CC me if you can.
-- Haris
On 07/13/2018 07:01 AM, Anna-Maria Gleixner wrote:
Hi Haris,
On Thu, 28 Jun 2018, Haris Okanovic wrote:
Collect expired timers in interrupt context to avoid overhead of waking
Sounds good. I'll keep an eye out for your patch set and try it on my
boards as well. CC me if you can.
-- Haris
On 07/13/2018 07:01 AM, Anna-Maria Gleixner wrote:
Hi Haris,
On Thu, 28 Jun 2018, Haris Okanovic wrote:
Collect expired timers in interrupt context to avoid overhead of waking
On Tue, Jul 3, 2018 at 7:20 PM, Stuart Hayes wrote:
>
> If the WSMT ACPI table is present and indicates that a fixed communication
> buffer should be used, use the firmware-specified buffer instead of
> allocating a buffer in memory for communications between the dcdbas driver
> and firmare.
>
>
On Tue, Jul 3, 2018 at 7:20 PM, Stuart Hayes wrote:
>
> If the WSMT ACPI table is present and indicates that a fixed communication
> buffer should be used, use the firmware-specified buffer instead of
> allocating a buffer in memory for communications between the dcdbas driver
> and firmare.
>
>
get_seconds() has a limited range on 32-bit architectures and is
deprecated because of that. While AFS uses the same limits for
its inode timestamps on the wire protocol, let's just use the
simpler current_time() as we do for other file systems.
This will still zero out the 'tv_nsec' field of the
get_seconds() has a limited range on 32-bit architectures and is
deprecated because of that. While AFS uses the same limits for
its inode timestamps on the wire protocol, let's just use the
simpler current_time() as we do for other file systems.
This will still zero out the 'tv_nsec' field of the
On Thu 12-07-18 14:34:00, David Rientjes wrote:
[...]
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> index 0fe4087d5151..e6328cef090f 100644
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -488,9 +488,11 @@ void __oom_reap_task_mm(struct mm_struct *mm)
>* Tell all users of
On Fri, Jul 6, 2018 at 7:28 PM, wrote:
> Reviewed-by: Mario Limonciello
Pushed to my review and testing queue, thanks!
>> This driver has no maintainer.
>
> Stuart,
>
> Outside of this patch, I think it would make sense to send some follow up
> patch
> series that do the following:
>
> 1)
On Thu 12-07-18 14:34:00, David Rientjes wrote:
[...]
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> index 0fe4087d5151..e6328cef090f 100644
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -488,9 +488,11 @@ void __oom_reap_task_mm(struct mm_struct *mm)
>* Tell all users of
On Fri, Jul 6, 2018 at 7:28 PM, wrote:
> Reviewed-by: Mario Limonciello
Pushed to my review and testing queue, thanks!
>> This driver has no maintainer.
>
> Stuart,
>
> Outside of this patch, I think it would make sense to send some follow up
> patch
> series that do the following:
>
> 1)
afs uses 32-bit timestamps everywhere, but mixes signed and unsigned
usage, which is a bit inconsistent. In particular on 32-bit machines,
it currently uses unsigned timestamps (ranging from 1970 to 2106) for
locally modified files, but signed timestamps (rand 1902 to 2038) when
reading from a
afs uses 32-bit timestamps everywhere, but mixes signed and unsigned
usage, which is a bit inconsistent. In particular on 32-bit machines,
it currently uses unsigned timestamps (ranging from 1970 to 2106) for
locally modified files, but signed timestamps (rand 1902 to 2038) when
reading from a
On 07/10/2018 02:25 PM, Ray Jui wrote:
> This patch series adds DT support for Stingray smart NIC boards
>
> This patch series is based off v4.18-rc3 and is available on GIHUB:
> repo: https://github.com/Broadcom/arm64-linux.git
> branch: sr-smartnic-dt-v1
Series applied to
On 07/10/2018 02:25 PM, Ray Jui wrote:
> This patch series adds DT support for Stingray smart NIC boards
>
> This patch series is based off v4.18-rc3 and is available on GIHUB:
> repo: https://github.com/Broadcom/arm64-linux.git
> branch: sr-smartnic-dt-v1
Series applied to
On Fri, Jul 6, 2018 at 11:55 PM Ganesh Goudar wrote:
>
> Hi,
>
> Kindly pull the new firmware from the following URL.
> git://git.chelsio.net/pub/git/linux-firmware.git for-upstream
>
> Thanks
> Ganesh
>
> The following changes since commit d1147327232ec4616a66ab898df84f9700c816c1:
>
> Merge
On Fri, Jul 6, 2018 at 11:55 PM Ganesh Goudar wrote:
>
> Hi,
>
> Kindly pull the new firmware from the following URL.
> git://git.chelsio.net/pub/git/linux-firmware.git for-upstream
>
> Thanks
> Ganesh
>
> The following changes since commit d1147327232ec4616a66ab898df84f9700c816c1:
>
> Merge
On Fri, Jul 13, 2018 at 08:46:25AM -0500, Eric W. Biederman wrote:
> Pavel Emelyanov writes:
>
> > On 07/12/2018 07:33 PM, Eric W. Biederman wrote:
> >>
> >> Adrian Reber writes:
> >>
> >>> The CHECKPOINT_RESTORE configuration option was introduced in 2012 and
> >>> combined with EXPERT.
On Fri, Jul 13, 2018 at 08:46:25AM -0500, Eric W. Biederman wrote:
> Pavel Emelyanov writes:
>
> > On 07/12/2018 07:33 PM, Eric W. Biederman wrote:
> >>
> >> Adrian Reber writes:
> >>
> >>> The CHECKPOINT_RESTORE configuration option was introduced in 2012 and
> >>> combined with EXPERT.
On Wed, Jul 4, 2018 at 10:39 PM, Vadim Pasternak wrote:
>
>
>> -Original Message-
>> From: Kees Cook [mailto:keesc...@chromium.org]
>> Sent: Wednesday, July 04, 2018 8:29 PM
>> To: Darren Hart
>> Cc: Vadim Pasternak ; Andy Shevchenko
>> ; platform-driver-...@vger.kernel.org; linux-
>>
On Wed, Jul 4, 2018 at 10:39 PM, Vadim Pasternak wrote:
>
>
>> -Original Message-
>> From: Kees Cook [mailto:keesc...@chromium.org]
>> Sent: Wednesday, July 04, 2018 8:29 PM
>> To: Darren Hart
>> Cc: Vadim Pasternak ; Andy Shevchenko
>> ; platform-driver-...@vger.kernel.org; linux-
>>
const is a magic keyword here :)
Acked-by: Peter Hutterer
Signed-off-by: Benjamin Tissoires
---
no changes in v4
no changes in v3
no changes in v2
---
drivers/hid/hid-multitouch.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/hid/hid-multitouch.c
const is a magic keyword here :)
Acked-by: Peter Hutterer
Signed-off-by: Benjamin Tissoires
---
no changes in v4
no changes in v3
no changes in v2
---
drivers/hid/hid-multitouch.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/hid/hid-multitouch.c
Now that the driver can handle more than one multitouch collection in
a single HID device, ditch the last bit that contains us to use only
one mt collection.
Acked-by: Peter Hutterer
Signed-off-by: Benjamin Tissoires
---
no changes in v4
no changes in v3
no changes in v2
---
Now that the driver can handle more than one multitouch collection in
a single HID device, ditch the last bit that contains us to use only
one mt collection.
Acked-by: Peter Hutterer
Signed-off-by: Benjamin Tissoires
---
no changes in v4
no changes in v3
no changes in v2
---
The Dell Canvas 27 has a tool that can be put on the surface and acts
as a dial. The firmware processes the detection of the tool and forward
regular HID reports with X, Y, Azimuth, rotation, width/height.
The firmware also exports Contact ID, Countact Count which may hint that
several totems can
The Dell Canvas 27 has a tool that can be put on the surface and acts
as a dial. The firmware processes the detection of the tool and forward
regular HID reports with X, Y, Azimuth, rotation, width/height.
The firmware also exports Contact ID, Countact Count which may hint that
several totems can
401 - 500 of 944 matches
Mail list logo
