4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Glauber
commit c782a8c43e94ba6c09e9de2d69b5e3a5840ce61c upstream.
After issuing a request an endless loop was used to read the
completion state from memory which is asynchronously updated
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Glauber
commit c782a8c43e94ba6c09e9de2d69b5e3a5840ce61c upstream.
After issuing a request an endless loop was used to read the
completion state from memory which is asynchronously updated
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Bonzini
commit ce14e868a54edeb2e30cb7a7b104a2fc4b9d76ca upstream.
Int the next patch the emulator's .read_std and .write_std callbacks will
grow another argument, which is not needed in
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Bonzini
commit ce14e868a54edeb2e30cb7a7b104a2fc4b9d76ca upstream.
Int the next patch the emulator's .read_std and .write_std callbacks will
grow another argument, which is not needed in
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Bin Liu
commit 9dbc8a0328efa485a6f5b68b867f9f523a3fbeff upstream.
Fixes: 8043bb1ae03cb ("crypto: omap-sham - convert driver logic to use sgs for
data xmit")
The memory pages freed in
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Bin Liu
commit 9dbc8a0328efa485a6f5b68b867f9f523a3fbeff upstream.
Fixes: 8043bb1ae03cb ("crypto: omap-sham - convert driver logic to use sgs for
data xmit")
The memory pages freed in
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Kappner
commit 8c4e97ddfe73a0958bb0abf7e6a3bc4cc3e04936 upstream.
The ALWAYS_SYNC flag is currently honored by the usb-storage driver but not UAS
and is required to work around
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Kappner
commit 8c4e97ddfe73a0958bb0abf7e6a3bc4cc3e04936 upstream.
The ALWAYS_SYNC flag is currently honored by the usb-storage driver but not UAS
and is required to work around
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Walleij
commit 7d18f0a14aa6a0d6bad39111c1fb655f07f71d59 upstream.
Sometimes a GPIO is fetched with NULL as parent device, and
that is just fine. So under these circumstances, avoid
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Walleij
commit 7d18f0a14aa6a0d6bad39111c1fb655f07f71d59 upstream.
Sometimes a GPIO is fetched with NULL as parent device, and
that is just fine. So under these circumstances, avoid
On 14/06/18 15:18, Quentin Perret wrote:
> On Thursday 14 Jun 2018 at 16:11:18 (+0200), Juri Lelli wrote:
> > On 14/06/18 14:58, Quentin Perret wrote:
> >
> > [...]
> >
> > > Hmm not sure if this can help but I think that rebuild_sched_domains()
> > > does _not_ take the hotplug lock before
On 14/06/18 14:58, Quentin Perret wrote:
[...]
> Hmm not sure if this can help but I think that rebuild_sched_domains()
> does _not_ take the hotplug lock before calling partition_sched_domains()
> when CONFIG_CPUSETS=n. But it does take it for CONFIG_CPUSETS=y.
Did you mean cpuset_mutex?
On 14/06/18 15:18, Quentin Perret wrote:
> On Thursday 14 Jun 2018 at 16:11:18 (+0200), Juri Lelli wrote:
> > On 14/06/18 14:58, Quentin Perret wrote:
> >
> > [...]
> >
> > > Hmm not sure if this can help but I think that rebuild_sched_domains()
> > > does _not_ take the hotplug lock before
On 14/06/18 14:58, Quentin Perret wrote:
[...]
> Hmm not sure if this can help but I think that rebuild_sched_domains()
> does _not_ take the hotplug lock before calling partition_sched_domains()
> when CONFIG_CPUSETS=n. But it does take it for CONFIG_CPUSETS=y.
Did you mean cpuset_mutex?
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Walleij
commit 7d18f0a14aa6a0d6bad39111c1fb655f07f71d59 upstream.
Sometimes a GPIO is fetched with NULL as parent device, and
that is just fine. So under these circumstances, avoid using
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Walleij
commit 7d18f0a14aa6a0d6bad39111c1fb655f07f71d59 upstream.
Sometimes a GPIO is fetched with NULL as parent device, and
that is just fine. So under these circumstances, avoid using
From: Guenter Roeck
Fix build error on nds32 due to the merge of commit e3d5980568f ("lib:
Rename compiler intrinsic selects to GENERIC_LIB_*") during the 4.18
merge window which renames Kconfig symbols. This had raced with commit
aeaa7af744fa ("nds32: lib: To use generic lib instead of libgcc
From: Guenter Roeck
Fix build error on nds32 due to the merge of commit e3d5980568f ("lib:
Rename compiler intrinsic selects to GENERIC_LIB_*") during the 4.18
merge window which renames Kconfig symbols. This had raced with commit
aeaa7af744fa ("nds32: lib: To use generic lib instead of libgcc
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Martin Wilck
commit 42819eb7a0957cc340ad4ed8bba736bab5ebc464 upstream.
The merged version of my patch "nvmet: don't report 0-bytes in serial
number" fails to remove two lines which should have
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Martin Wilck
commit 42819eb7a0957cc340ad4ed8bba736bab5ebc464 upstream.
The merged version of my patch "nvmet: don't report 0-bytes in serial
number" fails to remove two lines which should have
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Bonzini
commit 79367a65743975e5cac8d24d08eccc7fdae832b0 upstream.
Wrap the common invocation of ctxt->ops->read_std and ctxt->ops->write_std, so
as to have a smaller patch when the
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Bonzini
commit 79367a65743975e5cac8d24d08eccc7fdae832b0 upstream.
Wrap the common invocation of ctxt->ops->read_std and ctxt->ops->write_std, so
as to have a smaller patch when the
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit ca6938a1cd8a1c5e861a99b67f84ac166fc2b9e7 upstream.
Since commit:
58122bf1d856 ("x86/fpu: Default eagerfpu=on on all CPUs")
... in Linux 4.6, eager FPU mode has been
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit ca6938a1cd8a1c5e861a99b67f84ac166fc2b9e7 upstream.
Since commit:
58122bf1d856 ("x86/fpu: Default eagerfpu=on on all CPUs")
... in Linux 4.6, eager FPU mode has been
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Bonzini
commit ce14e868a54edeb2e30cb7a7b104a2fc4b9d76ca upstream.
Int the next patch the emulator's .read_std and .write_std callbacks will
grow another argument, which is not needed in
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Bonzini
commit ce14e868a54edeb2e30cb7a7b104a2fc4b9d76ca upstream.
Int the next patch the emulator's .read_std and .write_std callbacks will
grow another argument, which is not needed in
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Laura Abbott
commit 45ad559a29629cb1c64ee636563c69b71524f077 upstream.
Syzbot reported yet another warning with Ion:
WARNING: CPU: 0 PID: 1467 at drivers/staging/android/ion/ion.c:122
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Laura Abbott
commit 45ad559a29629cb1c64ee636563c69b71524f077 upstream.
Syzbot reported yet another warning with Ion:
WARNING: CPU: 0 PID: 1467 at drivers/staging/android/ion/ion.c:122
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Kappner
commit 8c4e97ddfe73a0958bb0abf7e6a3bc4cc3e04936 upstream.
The ALWAYS_SYNC flag is currently honored by the usb-storage driver but not UAS
and is required to work around
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Kappner
commit 8c4e97ddfe73a0958bb0abf7e6a3bc4cc3e04936 upstream.
The ALWAYS_SYNC flag is currently honored by the usb-storage driver but not UAS
and is required to work around
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Kappner
commit ca7d9515d0e6825351ce106066cea1f60e40b1c8 upstream.
The "G-Drive" (sold by G-Technology) external USB 3.0 drive
hangs on write access under UAS and usb-storage:
[
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Kappner
commit ca7d9515d0e6825351ce106066cea1f60e40b1c8 upstream.
The "G-Drive" (sold by G-Technology) external USB 3.0 drive
hangs on write access under UAS and usb-storage:
[
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mahesh Bandewar
commit b5bf0f5b16b9c316c34df9f31d4be8729eb86845 upstream.
bond_miimon_commit() marks the link UP after attempting to get the speed
and duplex settings for the link. There is a
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mahesh Bandewar
commit b5bf0f5b16b9c316c34df9f31d4be8729eb86845 upstream.
bond_miimon_commit() marks the link UP after attempting to get the speed
and duplex settings for the link. There is a
On Tue, Jun 12, 2018 at 5:28 AM, Zhouyang Jia wrote:
> When i2c_new_dummy fails, the lack of error-handling code may
> cause unexpected results.
>
> This patch adds error-handling code after calling i2c_new_dummy.
>
> Signed-off-by: Zhouyang Jia
Patch applied for non-critical fixes.
Yours,
On Tue, Jun 12, 2018 at 5:28 AM, Zhouyang Jia wrote:
> When i2c_new_dummy fails, the lack of error-handling code may
> cause unexpected results.
>
> This patch adds error-handling code after calling i2c_new_dummy.
>
> Signed-off-by: Zhouyang Jia
Patch applied for non-critical fixes.
Yours,
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Tony Lindgren
commit 13dc04d0e5fdc25c8f713ad23fdce51cf2bf96ba upstream.
I noticed that unused UARTs won't necessarily idle properly always
unless at least one byte tx transfer is done first.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Geert Uytterhoeven
commit d63c16f8e1ab761775275adcf54f4bef7c330295 upstream.
Printk format "%pCr" will be removed soon, as clk_get_rate() must not be
called in atomic context.
Replace it by
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Tony Lindgren
commit 13dc04d0e5fdc25c8f713ad23fdce51cf2bf96ba upstream.
I noticed that unused UARTs won't necessarily idle properly always
unless at least one byte tx transfer is done first.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Geert Uytterhoeven
commit d63c16f8e1ab761775275adcf54f4bef7c330295 upstream.
Printk format "%pCr" will be removed soon, as clk_get_rate() must not be
called in atomic context.
Replace it by
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Wienke
commit e6e7e9cd8eed0e18217c899843bffbe8c7dae564 upstream.
Add ELAN0612 to the list of supported touchpads; this ID is used in Lenovo
v330 14IKB devices.
Bugzilla:
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Wienke
commit e6e7e9cd8eed0e18217c899843bffbe8c7dae564 upstream.
Add ELAN0612 to the list of supported touchpads; this ID is used in Lenovo
v330 14IKB devices.
Bugzilla:
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Bonzini
commit 3c9fa24ca7c9c47605672916491f79e8ccacb9e6 upstream.
The functions that were used in the emulation of fxrstor, fxsave, sgdt and
sidt were originally meant for task
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Bonzini
commit 3c9fa24ca7c9c47605672916491f79e8ccacb9e6 upstream.
The functions that were used in the emulation of fxrstor, fxsave, sgdt and
sidt were originally meant for task
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ethan Lee
commit 5ca4d1ae9bad0f59bd6f851c39b19f5366953666 upstream.
GPD Win 2 Website: http://www.gpd.hk/gpdwin2.asp
Tested on a unit from the first production run sent to Indiegogo backers
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Andreas Born
commit ad729bc9acfb7c47112964b4877ef5404578ed13 upstream.
The patch c4adfc822bf5 ("bonding: make speed, duplex setting consistent
with link state") puts the link state to down if
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ethan Lee
commit 5ca4d1ae9bad0f59bd6f851c39b19f5366953666 upstream.
GPD Win 2 Website: http://www.gpd.hk/gpdwin2.asp
Tested on a unit from the first production run sent to Indiegogo backers
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Andreas Born
commit ad729bc9acfb7c47112964b4877ef5404578ed13 upstream.
The patch c4adfc822bf5 ("bonding: make speed, duplex setting consistent
with link state") puts the link state to down if
On Thu, Jun 14, 2018 at 10:01:08AM +0300, Leon Romanovsky wrote:
> On Wed, Jun 13, 2018 at 11:21:54PM -0700, Cong Wang wrote:
> > On Wed, Jun 13, 2018 at 10:34 PM, Leon Romanovsky wrote:
> > >
> > > Hi Cong,
> > >
> > > If the compiler optimizes the first line (mutex_lock) as you wrote,
> > > it
On Thu, Jun 14, 2018 at 10:01:08AM +0300, Leon Romanovsky wrote:
> On Wed, Jun 13, 2018 at 11:21:54PM -0700, Cong Wang wrote:
> > On Wed, Jun 13, 2018 at 10:34 PM, Leon Romanovsky wrote:
> > >
> > > Hi Cong,
> > >
> > > If the compiler optimizes the first line (mutex_lock) as you wrote,
> > > it
On Thu, Jun 14, 2018 at 10:55 AM, wrote:
> From: Sean Wang
>
> The function, external interrupt controller, is made as an optional to
> mt7622 pinctrl. But if we don't want pio behaves as an external interrupt
> controller, it would lead to hw->eint not be created properly and then
> will
On Thu, Jun 14, 2018 at 10:55 AM, wrote:
> From: Sean Wang
>
> The function, external interrupt controller, is made as an optional to
> mt7622 pinctrl. But if we don't want pio behaves as an external interrupt
> controller, it would lead to hw->eint not be created properly and then
> will
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Keith Busch
commit 161b8be2bd6abad250d4b3f674bdd5480f15beeb upstream.
A spurious interrupt before the nvme driver has initialized the completion
queue may inadvertently cause the driver to
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Keith Busch
commit 161b8be2bd6abad250d4b3f674bdd5480f15beeb upstream.
A spurious interrupt before the nvme driver has initialized the completion
queue may inadvertently cause the driver to
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 02f39b2379fb81557ae864ec8f85421c0250c954 upstream.
The crypto code was checking both use_eager_fpu() and
defined(X86_FEATURE_EAGER_FPU). The latter was nonsensical, so
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 02f39b2379fb81557ae864ec8f85421c0250c954 upstream.
The crypto code was checking both use_eager_fpu() and
defined(X86_FEATURE_EAGER_FPU). The latter was nonsensical, so
On Wed, Jun 13, 2018 at 1:06 AM, Stephen Boyd wrote:
> Update the binding for two more PMICs supported by the same driver.
> While we're here, remove the duplicate pmi8994 lines because that
> support got merged twice.
>
> Cc: Rajendra Nayak
> Cc: Vivek Gautam
> Cc:
> Signed-off-by: Stephen
On Wed, Jun 13, 2018 at 1:06 AM, Stephen Boyd wrote:
> Update the binding for two more PMICs supported by the same driver.
> While we're here, remove the duplicate pmi8994 lines because that
> support got merged twice.
>
> Cc: Rajendra Nayak
> Cc: Vivek Gautam
> Cc:
> Signed-off-by: Stephen
On 6/13/2018 3:54 AM, Andy Shevchenko wrote:
>> + /* Calling Interface SMI
>
> I suppose the style of the comments like
> /*
> * Calling ...
> ...
Yes... goof on my part. Thanks.
>> +*
>> +* Provide physical address of command buffer field
On 6/13/2018 3:54 AM, Andy Shevchenko wrote:
>> + /* Calling Interface SMI
>
> I suppose the style of the comments like
> /*
> * Calling ...
> ...
Yes... goof on my part. Thanks.
>> +*
>> +* Provide physical address of command buffer field
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
The x86 copy of cpufeatures.h is now out of sync, so fix that.
Signed-off-by: Greg Kroah-Hartman
---
tools/arch/x86/include/asm/cpufeatures.h |2 +-
1 file changed, 1
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
The x86 copy of cpufeatures.h is now out of sync, so fix that.
Signed-off-by: Greg Kroah-Hartman
---
tools/arch/x86/include/asm/cpufeatures.h |2 +-
1 file changed, 1
On Thu, Jun 14, 2018 at 4:43 AM, Amit Kucheria wrote:
> SDM845 uses the TSENS v2 IP block
>
> Signed-off-by: Amit Kucheria
> ---
> Documentation/devicetree/bindings/thermal/qcom-tsens.txt | 1 +
> arch/arm64/boot/dts/qcom/msm8996.dtsi| 2 +-
> drivers/thermal/qcom/tsens-v2.c
On Thu, Jun 14, 2018 at 4:43 AM, Amit Kucheria wrote:
> SDM845 uses the TSENS v2 IP block
>
> Signed-off-by: Amit Kucheria
> ---
> Documentation/devicetree/bindings/thermal/qcom-tsens.txt | 1 +
> arch/arm64/boot/dts/qcom/msm8996.dtsi| 2 +-
> drivers/thermal/qcom/tsens-v2.c
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Borislav Petkov
commit 362f924b64ba0f4be2ee0cb697690c33d40be721 upstream.
Those are stupid and code should use static_cpu_has_safe() or
boot_cpu_has() instead. Kill the least used and unused
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Borislav Petkov
commit 362f924b64ba0f4be2ee0cb697690c33d40be721 upstream.
Those are stupid and code should use static_cpu_has_safe() or
boot_cpu_has() instead. Kill the least used and unused
On Thu, Jun 14, 2018 at 7:27 AM, Masahiro Yamada
wrote:
> If a GPIO chip is a part of a hierarchy IRQ domain, there is no
> way to specify the trigger type when gpio(d)_to_irq() allocates an
> interrupt on-the-fly.
>
> Currently, uniphier_gpio_to_irq() sets IRQ_TYPE_NONE, but it causes
> an
On Thu, Jun 14, 2018 at 7:27 AM, Masahiro Yamada
wrote:
> If a GPIO chip is a part of a hierarchy IRQ domain, there is no
> way to specify the trigger type when gpio(d)_to_irq() allocates an
> interrupt on-the-fly.
>
> Currently, uniphier_gpio_to_irq() sets IRQ_TYPE_NONE, but it causes
> an
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Juergen Gross
commit ed29210cd6a67425026e78aa298fa434e11a74e3 upstream.
It is used nowhere.
Signed-off-by: Juergen Gross
Link:
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Juergen Gross
commit ed29210cd6a67425026e78aa298fa434e11a74e3 upstream.
It is used nowhere.
Signed-off-by: Juergen Gross
Link:
This is the start of the stable review cycle for the 4.4.138 release.
There are 24 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sat Jun 16 13:27:15 UTC 2018.
Anything
Also I think the email list is rejecting your replies because they're
in html?
regards,
dan carpenter
Also I think the email list is rejecting your replies because they're
in html?
regards,
dan carpenter
This is the start of the stable review cycle for the 4.4.138 release.
There are 24 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sat Jun 16 13:27:15 UTC 2018.
Anything
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 02f39b2379fb81557ae864ec8f85421c0250c954 upstream.
The crypto code was checking both use_eager_fpu() and
defined(X86_FEATURE_EAGER_FPU). The latter was nonsensical, so
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 02f39b2379fb81557ae864ec8f85421c0250c954 upstream.
The crypto code was checking both use_eager_fpu() and
defined(X86_FEATURE_EAGER_FPU). The latter was nonsensical, so
On 06/13/2018 06:00 PM, Benjamin Herrenschmidt wrote:
On Wed, 2018-06-13 at 09:57 -0500, Eddie James wrote:
On 06/12/2018 12:19 AM, Benjamin Herrenschmidt wrote:
This was too hard to split ... this adds a number of features
to the SCOM user interface:
- Support for indirect SCOMs
-
On Thursday 14 Jun 2018 at 16:11:18 (+0200), Juri Lelli wrote:
> On 14/06/18 14:58, Quentin Perret wrote:
>
> [...]
>
> > Hmm not sure if this can help but I think that rebuild_sched_domains()
> > does _not_ take the hotplug lock before calling partition_sched_domains()
> > when
On Thursday 14 Jun 2018 at 16:11:18 (+0200), Juri Lelli wrote:
> On 14/06/18 14:58, Quentin Perret wrote:
>
> [...]
>
> > Hmm not sure if this can help but I think that rebuild_sched_domains()
> > does _not_ take the hotplug lock before calling partition_sched_domains()
> > when
On 06/13/2018 06:00 PM, Benjamin Herrenschmidt wrote:
On Wed, 2018-06-13 at 09:57 -0500, Eddie James wrote:
On 06/12/2018 12:19 AM, Benjamin Herrenschmidt wrote:
This was too hard to split ... this adds a number of features
to the SCOM user interface:
- Support for indirect SCOMs
-
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Bonzini
commit 79367a65743975e5cac8d24d08eccc7fdae832b0 upstream.
Wrap the common invocation of ctxt->ops->read_std and ctxt->ops->write_std, so
as to have a smaller patch when the
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Walleij
commit 7d18f0a14aa6a0d6bad39111c1fb655f07f71d59 upstream.
Sometimes a GPIO is fetched with NULL as parent device, and
that is just fine. So under these circumstances, avoid using
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Bonzini
commit 79367a65743975e5cac8d24d08eccc7fdae832b0 upstream.
Wrap the common invocation of ctxt->ops->read_std and ctxt->ops->write_std, so
as to have a smaller patch when the
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Walleij
commit 7d18f0a14aa6a0d6bad39111c1fb655f07f71d59 upstream.
Sometimes a GPIO is fetched with NULL as parent device, and
that is just fine. So under these circumstances, avoid using
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Marek Szyprowski
commit aa2f80e752c75e593b3820f42c416ed9458fa73e upstream.
The best granularity of residue that DMA engine can report is in the BURST
units, so the serial driver must use
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Marek Szyprowski
commit aa2f80e752c75e593b3820f42c416ed9458fa73e upstream.
The best granularity of residue that DMA engine can report is in the BURST
units, so the serial driver must use
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Bonzini
commit 3c9fa24ca7c9c47605672916491f79e8ccacb9e6 upstream.
The functions that were used in the emulation of fxrstor, fxsave, sgdt and
sidt were originally meant for task
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Bonzini
commit 3c9fa24ca7c9c47605672916491f79e8ccacb9e6 upstream.
The functions that were used in the emulation of fxrstor, fxsave, sgdt and
sidt were originally meant for task
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Wienke
commit e6e7e9cd8eed0e18217c899843bffbe8c7dae564 upstream.
Add ELAN0612 to the list of supported touchpads; this ID is used in Lenovo
v330 14IKB devices.
Bugzilla:
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Wienke
commit e6e7e9cd8eed0e18217c899843bffbe8c7dae564 upstream.
Add ELAN0612 to the list of supported touchpads; this ID is used in Lenovo
v330 14IKB devices.
Bugzilla:
On 06/14/2018 03:53 PM, Paul Clarke wrote:
> On 06/14/2018 06:48 AM, Thomas Richter wrote:
>> PMU alias definitions in sysfs files may have spaces, newlines
>> and number with leading zeroes. Same alias definitions may
>> also appear in JSON files without spaces, etc.
>>
>> Scan alias definitions
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 58122bf1d856a4ea9581d62a07c557d997d46a19 upstream.
We have eager and lazy FPU modes, introduced in:
304bceda6a18 ("x86, fpu: use non-lazy fpu restore for processors
On 06/14/2018 03:53 PM, Paul Clarke wrote:
> On 06/14/2018 06:48 AM, Thomas Richter wrote:
>> PMU alias definitions in sysfs files may have spaces, newlines
>> and number with leading zeroes. Same alias definitions may
>> also appear in JSON files without spaces, etc.
>>
>> Scan alias definitions
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 58122bf1d856a4ea9581d62a07c557d997d46a19 upstream.
We have eager and lazy FPU modes, introduced in:
304bceda6a18 ("x86, fpu: use non-lazy fpu restore for processors
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit f363938c70a04e6bc99023a5e0c44ef7879b903f upstream.
After fixing FPU option parsing, we now parse the 'no387' boot option
too early: no387 clears X86_FEATURE_FPU before
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit f363938c70a04e6bc99023a5e0c44ef7879b903f upstream.
After fixing FPU option parsing, we now parse the 'no387' boot option
too early: no387 clears X86_FEATURE_FPU before
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Borislav Petkov
commit 6e6867093de35141f0a76b66ac13f9f2e2c8e77a upstream.
i486 derived cores like Intel Quark support only the very old,
legacy x87 FPU (FSAVE/FRSTOR, CPUID bit FXSR is not
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Borislav Petkov
commit 6e6867093de35141f0a76b66ac13f9f2e2c8e77a upstream.
i486 derived cores like Intel Quark support only the very old,
legacy x87 FPU (FSAVE/FRSTOR, CPUID bit FXSR is not
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit 0cc3b0ec23ce4c69e1e890ed2b8d2fa932b14aad upstream.
We have a MAX_LFS_FILESIZE macro that is meant to be filled in by
filesystems (and other IO targets) that know they are
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit 0cc3b0ec23ce4c69e1e890ed2b8d2fa932b14aad upstream.
We have a MAX_LFS_FILESIZE macro that is meant to be filled in by
filesystems (and other IO targets) that know they are
601 - 700 of 1344 matches
Mail list logo
