3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Nikolay Borisov
commit 18d03e8c25f173f4107a40d0b8c24defb6ed69f3 upstream.
When a thin pool is being destroyed delayed work items are
cancelled using cancel_delayed_work(),
In the case of Renesas R-Car hardware we know that there are generations of
SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the
relationship between IP blocks might be. For example, I believe that
r8a7790 is older than r8a7791 but that doesn't imply that the latter is a
descendant
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Nikolay Borisov
commit 18d03e8c25f173f4107a40d0b8c24defb6ed69f3 upstream.
When a thin pool is being destroyed delayed work items are
cancelled using cancel_delayed_work(), which doesn't
In the case of Renesas R-Car hardware we know that there are generations of
SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the
relationship between IP blocks might be. For example, I believe that
r8a7790 is older than r8a7791 but that doesn't imply that the latter is a
descendant
In the case of Renesas R-Car hardware we know that there are generations of
SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the
relationship between IP blocks might be. For example, I believe that
r8a7790 is older than r8a7791 but that doesn't imply that the latter is a
descendant
Add fallback compatibility strings for rcar phy drivers.
In the case of Renesas R-Car hardware we know that there are generations of
SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the
relationship between IP blocks might be. For example, I believe that
r8a7790 is older than
In the case of Renesas R-Car hardware we know that there are generations of
SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the
relationship between IP blocks might be. For example, I believe that
r8a7790 is older than r8a7791 but that doesn't imply that the latter is a
descendant
Add fallback compatibility strings for rcar phy drivers.
In the case of Renesas R-Car hardware we know that there are generations of
SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the
relationship between IP blocks might be. For example, I believe that
r8a7790 is older than
From: Matthias Brugger
Tronsmart is a China based company building consumer electronic
devices.
Signed-off-by: Matthias Brugger
Acked-by: Rob Herring
Signed-off-by: Andreas Färber
---
v1 -> v2:
* Replaced with
Signed-off-by: Andreas Färber
---
v1 -> v2:
* Adopted "arm,cortex-a53-pmu" compatible string (Sudeep)
* Adopted "arm,gic-400" compatible string (André, Sudeep)
* Adopted "arm,psci-0.2" compatible string and dropped functions (Sudeep)
* Squashed GIC reg extension patch,
From: Matthias Brugger
Tronsmart is a China based company building consumer electronic
devices.
Signed-off-by: Matthias Brugger
Acked-by: Rob Herring
Signed-off-by: Andreas Färber
---
v1 -> v2:
* Replaced with older identical patch (Matthias)
Signed-off-by: Andreas Färber
---
v1 -> v2:
* Adopted "arm,cortex-a53-pmu" compatible string (Sudeep)
* Adopted "arm,gic-400" compatible string (André, Sudeep)
* Adopted "arm,psci-0.2" compatible string and dropped functions (Sudeep)
* Squashed GIC reg extension patch, enlarged one (André)
Add Device Trees for Tronsmart Vega S95 Pro, Meta and Telos TV boxes.
Signed-off-by: Andreas Färber
---
v1 -> v2:
* Dropped aliases (moved to Meson gxbb .dtsi)
* Override only status of uart node (moved to Meson gxbb .dtsi)
arch/arm64/boot/dts/amlogic/Makefile
Use "tronsmart,vega-s95" as well as
"tronsmart,vega-s95-pro",
"tronsmart,vega-s95-meta" and
"tronsmart,vega-s95-telos" compatible strings.
Signed-off-by: Andreas Färber
---
v1 -> v2: unchanged
Documentation/devicetree/bindings/arm/amlogic.txt | 3 +++
1 file
Add Device Trees for Tronsmart Vega S95 Pro, Meta and Telos TV boxes.
Signed-off-by: Andreas Färber
---
v1 -> v2:
* Dropped aliases (moved to Meson gxbb .dtsi)
* Override only status of uart node (moved to Meson gxbb .dtsi)
arch/arm64/boot/dts/amlogic/Makefile | 4 ++
Use "tronsmart,vega-s95" as well as
"tronsmart,vega-s95-pro",
"tronsmart,vega-s95-meta" and
"tronsmart,vega-s95-telos" compatible strings.
Signed-off-by: Andreas Färber
---
v1 -> v2: unchanged
Documentation/devicetree/bindings/arm/amlogic.txt | 3 +++
1 file changed, 3
Use "amlogic,meson-gxbb" compatible string.
Signed-off-by: Andreas Färber
---
v1 -> v2: unchanged
Documentation/devicetree/bindings/arm/amlogic.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/amlogic.txt
Use "amlogic,meson-gxbb" compatible string.
Signed-off-by: Andreas Färber
---
v1 -> v2: unchanged
Documentation/devicetree/bindings/arm/amlogic.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/amlogic.txt
Hello,
This series adds initial support for the Amlogic S905 based
Tronsmart Vega S95 Pro, Meta and Telos TV boxes.
v2:
* Pick up previously acked "tronsmart" patch instead (Matthias)
* Drop ARM_GIC selection (Sudeep)
* Change some compatible strings (Sudeep, André)
* Squash some node
Hello,
This series adds initial support for the Amlogic S905 based
Tronsmart Vega S95 Pro, Meta and Telos TV boxes.
v2:
* Pick up previously acked "tronsmart" patch instead (Matthias)
* Drop ARM_GIC selection (Sudeep)
* Change some compatible strings (Sudeep, André)
* Squash some node
Provide the ARCH_MESON Kconfig symbol to allow enabling existing serial
and i2c drivers.
Signed-off-by: Andreas Färber
---
v1 -> v2:
* Dropped ARM_GIC selection (Sudeep)
arch/arm64/Kconfig.platforms | 5 +
1 file changed, 5 insertions(+)
diff --git
Provide the ARCH_MESON Kconfig symbol to allow enabling existing serial
and i2c drivers.
Signed-off-by: Andreas Färber
---
v1 -> v2:
* Dropped ARM_GIC selection (Sudeep)
arch/arm64/Kconfig.platforms | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/Kconfig.platforms
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Andrey Ryabinin
commit 0ad95472bf169a3501991f8f33f5147f792a8116 upstream.
Commit cb7323fffa85 ("lockd: create and use per-net NSM
RPC clients on MON/UNMON requests")
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Roman Volkov
commit f9eccf24615672896dc13251410c3f2f33a14f95 upstream.
The vt8500 clocksource driver declares itself as capable to handle the
minimum delay of 4 cycles by
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Roman Volkov
commit 0f090bf14e51e7eefb71d9d1c545807f8b627986 upstream.
Since WM8650 has the same 'WMT' SDHC controller as WM8505, and the driver
is already in the kernel,
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Andrey Ryabinin
commit 0ad95472bf169a3501991f8f33f5147f792a8116 upstream.
Commit cb7323fffa85 ("lockd: create and use per-net NSM
RPC clients on MON/UNMON requests") introduced per-net
NSM
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Roman Volkov
commit f9eccf24615672896dc13251410c3f2f33a14f95 upstream.
The vt8500 clocksource driver declares itself as capable to handle the
minimum delay of 4 cycles by passing the value
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Roman Volkov
commit 0f090bf14e51e7eefb71d9d1c545807f8b627986 upstream.
Since WM8650 has the same 'WMT' SDHC controller as WM8505, and the driver
is already in the kernel, this node enables
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Gerhard Uttenthaler
commit 90cfde46586d2286488d8ed636929e936c0c9ab2 upstream.
This patch fixes the problem that more CAN messages could be sent to the
interface
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Gerhard Uttenthaler
commit 90cfde46586d2286488d8ed636929e936c0c9ab2 upstream.
This patch fixes the problem that more CAN messages could be sent to the
interface as could be send on the CAN
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Ken Lin
commit 6627ae19385283b89356a199d7f03c75ba35fb29 upstream.
Add USB ID for cp2104/5 devices on GE B650v3 and B850v3 boards.
Signed-off-by: Ken Lin
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Ken Lin
commit 6627ae19385283b89356a199d7f03c75ba35fb29 upstream.
Add USB ID for cp2104/5 devices on GE B650v3 and B850v3 boards.
Signed-off-by: Ken Lin
Signed-off-by: Akshay Bhat
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Valentin Rothberg
commit 90adf98d9530054b8e665ba5a928de4307231d84 upstream.
Since commit 1c6c69525b40 ("genirq: Reject bogus threaded irq requests")
threaded IRQs
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: sumit.sax...@avagotech.com
commit 323c4a02c631d00851d8edc4213c4d184ef83647 upstream.
This is an issue on SMAP enabled CPUs and 32 bit apps running on 64 bit
OS. Do
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 1f35d04a02a652f14566f875aef3a6f2af4cb77b upstream.
The iomap[] array has PCIM_IOMAP_MAX (6) elements and not
DEVICE_COUNT_RESOURCE (16). This
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Valentin Rothberg
commit 90adf98d9530054b8e665ba5a928de4307231d84 upstream.
Since commit 1c6c69525b40 ("genirq: Reject bogus threaded irq requests")
threaded IRQs without a primary handler
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: sumit.sax...@avagotech.com
commit 323c4a02c631d00851d8edc4213c4d184ef83647 upstream.
This is an issue on SMAP enabled CPUs and 32 bit apps running on 64 bit
OS. Do not access user memory from
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 1f35d04a02a652f14566f875aef3a6f2af4cb77b upstream.
The iomap[] array has PCIM_IOMAP_MAX (6) elements and not
DEVICE_COUNT_RESOURCE (16). This bug was found using a
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Egbert Eich
commit 28fb4cb7fa6f63dc2fbdb5f2564dcbead8e3eee0 upstream.
Due to a missing initialization there was no way to map fbdev memory.
Thus for example using the Xserver
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Egbert Eich
commit 28fb4cb7fa6f63dc2fbdb5f2564dcbead8e3eee0 upstream.
Due to a missing initialization there was no way to map fbdev memory.
Thus for example using the Xserver with the fbdev
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Luca Porzio
commit d3df0465db00cf4ed9f90d0bfc3b827d32b9c796 upstream.
Anytime a write operation is performed with Reliable Write flag enabled,
the eMMC device is enforced
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Luca Porzio
commit d3df0465db00cf4ed9f90d0bfc3b827d32b9c796 upstream.
Anytime a write operation is performed with Reliable Write flag enabled,
the eMMC device is enforced to bypass the cache
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: sumit.sax...@avagotech.com
commit 357ae967ad66e357f78b5cfb5ab6ca07fb4a7758 upstream.
Do not use PAGE_SIZE marco to calculate max_sectors per I/O
request. Driver
On Wed, Mar 2, 2016 at 9:37 AM, Darren Hart wrote:
> read_once will use a *volatile assignment instead of calling barrier()
> directly for a word size argument.
>
> With weak statements like "apparently" (above) and "could be" (from the
> original
> post: This patch
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: sumit.sax...@avagotech.com
commit 357ae967ad66e357f78b5cfb5ab6ca07fb4a7758 upstream.
Do not use PAGE_SIZE marco to calculate max_sectors per I/O
request. Driver code assumes PAGE_SIZE will be
On Wed, Mar 2, 2016 at 9:37 AM, Darren Hart wrote:
> read_once will use a *volatile assignment instead of calling barrier()
> directly for a word size argument.
>
> With weak statements like "apparently" (above) and "could be" (from the
> original
> post: This patch replaces this bare barrier()
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Hariprasad S
commit 67f1aee6f45059fd6b0f5b0ecb2c97ad0451f6b3 upstream.
The cxgb3_*_send() functions return NET_XMIT_ values, which are
positive integers values. So
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 02e2a5bfebe99edcf9d694575a75032d53fe1b73 upstream.
If md->signature == MAC_DRIVER_MAGIC and md->block_size == 1023, a single
512 byte sector would be
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Vineet Gupta
commit 2e22502c080f27afeab5e6f11e618fb7bc7aea53 upstream.
Fixes STAR 9000953410: "perf callgraph profiling causing RCU stalls"
| perf record -g -c 15000 -e
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Hariprasad S
commit 67f1aee6f45059fd6b0f5b0ecb2c97ad0451f6b3 upstream.
The cxgb3_*_send() functions return NET_XMIT_ values, which are
positive integers values. So don't treat positive return
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 02e2a5bfebe99edcf9d694575a75032d53fe1b73 upstream.
If md->signature == MAC_DRIVER_MAGIC and md->block_size == 1023, a single
512 byte sector would be read (secsize / 512).
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Vineet Gupta
commit 2e22502c080f27afeab5e6f11e618fb7bc7aea53 upstream.
Fixes STAR 9000953410: "perf callgraph profiling causing RCU stalls"
| perf record -g -c 15000 -e cycles
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt (Red Hat)
commit b81f472a208d3e2b4392faa6d17037a89442f4ce upstream.
Do not update the read stamp after swapping out the reader page from the
write buffer.
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Joe Thornber
commit ed8b45a3679eb49069b094c0711b30833f27c734 upstream.
If dm_btree_del()'s call to push_frame() fails, e.g. due to
btree_node_validator finding invalid
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt (Red Hat)
commit b81f472a208d3e2b4392faa6d17037a89442f4ce upstream.
Do not update the read stamp after swapping out the reader page from the
write buffer. If the reader page is
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Joe Thornber
commit ed8b45a3679eb49069b094c0711b30833f27c734 upstream.
If dm_btree_del()'s call to push_frame() fails, e.g. due to
btree_node_validator finding invalid metadata, the
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit d98f1cd0a3b70ea91f1dfda3ac36c3b2e1a4d5e2 upstream.
When I connect an Intel SSD to SATA SIL controller (PCI ID 1095:3114), any
TRIM command results
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit c2489e07c0a71a56fb2c84bc0ee66cddfca7d068 upstream.
The following test program from Dmitry can cause softlockups or RCU
stalls as it copies 1GB from tmpfs into
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit d98f1cd0a3b70ea91f1dfda3ac36c3b2e1a4d5e2 upstream.
When I connect an Intel SSD to SATA SIL controller (PCI ID 1095:3114), any
TRIM command results in I/O errors being
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit c2489e07c0a71a56fb2c84bc0ee66cddfca7d068 upstream.
The following test program from Dmitry can cause softlockups or RCU
stalls as it copies 1GB from tmpfs into eventfd and we
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit b7bb110008607a915298bf0f47d25886ecb94477 upstream.
Some users of rfkill, like NFC and cfg80211, use a dynamic name when
allocating rfkill, in
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Suman Anna
commit c13f99b7e945dad5273a8b7ee230f4d1f22d3354 upstream.
The virtio core uses a static ida named virtio_index_ida for
assigning index numbers to virtio devices
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit b7bb110008607a915298bf0f47d25886ecb94477 upstream.
Some users of rfkill, like NFC and cfg80211, use a dynamic name when
allocating rfkill, in those cases dev_name().
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Suman Anna
commit c13f99b7e945dad5273a8b7ee230f4d1f22d3354 upstream.
The virtio core uses a static ida named virtio_index_ida for
assigning index numbers to virtio devices during
From: Rafael J. Wysocki
Use the observation that cpufreq_update_util() is only called
by the scheduler with rq->lock held, so the callers of
cpufreq_set_update_util_data() can use synchronize_sched()
instead of synchronize_rcu() to wait for cpufreq_update_util()
to
Hi,
My previous intro message still applies somewhat, so here's a link:
http://marc.info/?l=linux-pm=145609673008122=2
The executive summary of the motivation is that I wanted to do two things:
use the utilization data from the scheduler (it's passed to the governor
as aguments of update
From: Rafael J. Wysocki
Use the observation that cpufreq_update_util() is only called
by the scheduler with rq->lock held, so the callers of
cpufreq_set_update_util_data() can use synchronize_sched()
instead of synchronize_rcu() to wait for cpufreq_update_util()
to complete. Moreover, if they
Hi,
My previous intro message still applies somewhat, so here's a link:
http://marc.info/?l=linux-pm=145609673008122=2
The executive summary of the motivation is that I wanted to do two things:
use the utilization data from the scheduler (it's passed to the governor
as aguments of update
On Tue, Mar 01, 2016 at 02:38:46PM +0100, Michal Hocko wrote:
> > I'd expect a build in 224M
> > RAM plus 2G of swap to take so long, that I'd be very grateful to be
> > OOM killed, even if there is technically enough space. Unless
> > perhaps it's some superfast swap that you have?
>
> the swap
On Tue, Mar 01, 2016 at 02:38:46PM +0100, Michal Hocko wrote:
> > I'd expect a build in 224M
> > RAM plus 2G of swap to take so long, that I'd be very grateful to be
> > OOM killed, even if there is technically enough space. Unless
> > perhaps it's some superfast swap that you have?
>
> the swap
On Tue, Mar 01, 2016 at 02:58:39PM +0100, Borislav Petkov wrote:
> On Mon, Feb 29, 2016 at 12:30:47PM +0100, Thomas Gleixner wrote:
> > On Tue, 1 Mar 2016, Huang Rui wrote:
> > > On Fri, Feb 26, 2016 at 11:18:28AM +0100, Thomas Gleixner wrote:
> > > > > +static int __init amd_power_pmu_init(void)
On Fri, Feb 26, 2016 at 3:44 PM, Alan Tull wrote:
> This patch add of overlay notifications.
>
> When DT overlays are being added, some drivers/subsystems
> need to see device tree overlays before the changes go into
> the live tree.
>
> This is distinct from reconfig
From: Rafael J. Wysocki
Modify the ACPI cpufreq driver to provide a method for switching
CPU frequencies from interrupt context and update the cpufreq core
to support that method if available.
Introduce a new cpufreq driver callback, ->fast_switch, to be
invoked for
On Wednesday 02 March 2016 06:28 AM, Krzysztof Kozlowski wrote:
On 29.02.2016 21:58, Laxman Dewangan wrote:
+ .alarm_pending_status_reg = MAX77620_RTC_ALARM_PENDING_STATUS_REG,
Just skip the alarm_pending_status_reg (so it will be 0x0) and check for
non-zero value later?
It might be a
On Tue, Mar 01, 2016 at 02:58:39PM +0100, Borislav Petkov wrote:
> On Mon, Feb 29, 2016 at 12:30:47PM +0100, Thomas Gleixner wrote:
> > On Tue, 1 Mar 2016, Huang Rui wrote:
> > > On Fri, Feb 26, 2016 at 11:18:28AM +0100, Thomas Gleixner wrote:
> > > > > +static int __init amd_power_pmu_init(void)
On Fri, Feb 26, 2016 at 3:44 PM, Alan Tull wrote:
> This patch add of overlay notifications.
>
> When DT overlays are being added, some drivers/subsystems
> need to see device tree overlays before the changes go into
> the live tree.
>
> This is distinct from reconfig notifiers that are
>
From: Rafael J. Wysocki
Modify the ACPI cpufreq driver to provide a method for switching
CPU frequencies from interrupt context and update the cpufreq core
to support that method if available.
Introduce a new cpufreq driver callback, ->fast_switch, to be
invoked for frequency switching from
On Wednesday 02 March 2016 06:28 AM, Krzysztof Kozlowski wrote:
On 29.02.2016 21:58, Laxman Dewangan wrote:
+ .alarm_pending_status_reg = MAX77620_RTC_ALARM_PENDING_STATUS_REG,
Just skip the alarm_pending_status_reg (so it will be 0x0) and check for
non-zero value later?
It might be a
From: Rafael J. Wysocki
Move abstract code related to struct gov_tunables to a separate (new)
file so it can be shared with (future) goverernors that won't share
more code with "ondemand" and "conservative".
No intentional functional changes.
Signed-off-by: Rafael
From: Rafael J. Wysocki
Add a new cpufreq scaling governor, called "schedutil", that uses
scheduler-provided CPU utilization information as input for making
its decisions.
Doing that is possible after commit fe7034338ba0 (cpufreq: Add
mechanism for registering
Hi Josh,
On Tue, 1 Mar 2016 15:54:51 -0600 Josh Poimboeuf wrote:
>
> Changing it to use the host compiler would probably be an easy fix, but
> that would expose a harder bug related to endianness.
Just by luck, my PowerPC host is little endian :-)
> How about the below
From: Rafael J. Wysocki
Move abstract code related to struct gov_tunables to a separate (new)
file so it can be shared with (future) goverernors that won't share
more code with "ondemand" and "conservative".
No intentional functional changes.
Signed-off-by: Rafael J. Wysocki
---
From: Rafael J. Wysocki
Add a new cpufreq scaling governor, called "schedutil", that uses
scheduler-provided CPU utilization information as input for making
its decisions.
Doing that is possible after commit fe7034338ba0 (cpufreq: Add
mechanism for registering utilization update callbacks) that
Hi Josh,
On Tue, 1 Mar 2016 15:54:51 -0600 Josh Poimboeuf wrote:
>
> Changing it to use the host compiler would probably be an easy fix, but
> that would expose a harder bug related to endianness.
Just by luck, my PowerPC host is little endian :-)
> How about the below workaround patch to
From: Rafael J. Wysocki
Setting a new CPU frequency and reading the current request value
in the ACPI cpufreq driver involves each at least two switch
instructions (there's more if the policy is shared). One of
them is present in drv_read/write() that prepares a
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: James Hogan
commit 002374f371bd02df864cce1fe85d90dc5b292837 upstream.
ASID restoration on guest resume should determine the guest execution
mode based on the guest
From: Rafael J. Wysocki
Setting a new CPU frequency and reading the current request value
in the ACPI cpufreq driver involves each at least two switch
instructions (there's more if the policy is shared). One of
them is present in drv_read/write() that prepares a command
structure and the other
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: James Hogan
commit 002374f371bd02df864cce1fe85d90dc5b292837 upstream.
ASID restoration on guest resume should determine the guest execution
mode based on the guest Status register rather than
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Kirill A. Shutemov
commit 9f5bd30818c42c6c36a51f93b4df75a2ea2bd85e upstream.
There are few defects in vga_get() related to signal hadning:
- we shouldn't check for
From: Rafael J. Wysocki
In addition to fields representing governor tunables, struct dbs_data
contains some fields needed for the management of objects of that
type. As it turns out, that part of struct dbs_data may be shared
with (future) governors that won't use
From: Rafael J. Wysocki
In addition to fields representing governor tunables, struct dbs_data
contains some fields needed for the management of objects of that
type. As it turns out, that part of struct dbs_data may be shared
with (future) governors that won't use the common code used by
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Kirill A. Shutemov
commit 9f5bd30818c42c6c36a51f93b4df75a2ea2bd85e upstream.
There are few defects in vga_get() related to signal hadning:
- we shouldn't check for pending signals for
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: James Bottomley
commit 3417c1b5cb1fdc10261dbed42b05cc93166a78fd upstream.
Simple enclosure implementations (mostly USB) are allowed to return only
page
Hi Stephen,
On Tue, Mar 01, 2016 at 11:00:21AM -0800, Stephen Boyd wrote:
> This flag is a no-op now. Remove usage of the flag.
>
> Cc: Andi Shyti
> Cc: Krzysztof Kozlowski
> Signed-off-by: Stephen Boyd
Acked-by: Andi
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: James Bottomley
commit 3417c1b5cb1fdc10261dbed42b05cc93166a78fd upstream.
Simple enclosure implementations (mostly USB) are allowed to return only
page 8 to every diagnostic query. That
Hi Stephen,
On Tue, Mar 01, 2016 at 11:00:21AM -0800, Stephen Boyd wrote:
> This flag is a no-op now. Remove usage of the flag.
>
> Cc: Andi Shyti
> Cc: Krzysztof Kozlowski
> Signed-off-by: Stephen Boyd
Acked-by: Andi Shyti
Thanks,
Andi
> ---
> drivers/clk/clk-s2mps11.c | 3 ---
> 1 file
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: James Bottomley
commit 5e1033561da1152c57b97ee84371dba2b3d64c25 upstream.
KASAN found that our additional element processing scripts drop off
the end of
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: James Bottomley
commit 5e1033561da1152c57b97ee84371dba2b3d64c25 upstream.
KASAN found that our additional element processing scripts drop off
the end of the VPD page into unallocated space.
Make use of ARCH_RENESAS in place of ARCH_SHMOBILE.
This is part of an ongoing process to migrate from ARCH_SHMOBILE to
ARCH_RENESAS the motivation for which being that RENESAS seems to be a more
appropriate name than SHMOBILE for the majority of Renesas ARM based SoCs.
Signed-off-by: Simon
Make use of ARCH_RENESAS in place of ARCH_SHMOBILE.
This is part of an ongoing process to migrate from ARCH_SHMOBILE to
ARCH_RENESAS the motivation for which being that RENESAS seems to be a more
appropriate name than SHMOBILE for the majority of Renesas ARM based SoCs.
Signed-off-by: Simon
201 - 300 of 2848 matches
Mail list logo