4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Lyle
commit 9276717b9e297a62d1151a43d1cd286213f68eb7 upstream.
Most importantly, solve a crash where %llu was used to format signed
numbers. This would cause a buffer
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Joe Carnuccio
commit 6e98095f8fb6d98da34c4e6c34e69e7c638d79c0 upstream.
Fix incorrect second argument for wait_event_timeout()
Fixes: c4a9b538ab2a ("qla2xxx: Allow
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Tang Junhui
commit a8394090a9129b40f9d90dcb7f4a49d60c727ca6 upstream.
__update_write_rate() uses a Proportion-Differentiation Controller
algorithm to control writeback
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Lyle
commit 9276717b9e297a62d1151a43d1cd286213f68eb7 upstream.
Most importantly, solve a crash where %llu was used to format signed
numbers. This would cause a buffer overflow when
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Joe Carnuccio
commit 6e98095f8fb6d98da34c4e6c34e69e7c638d79c0 upstream.
Fix incorrect second argument for wait_event_timeout()
Fixes: c4a9b538ab2a ("qla2xxx: Allow vref count to timeout on
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Tang Junhui
commit a8394090a9129b40f9d90dcb7f4a49d60c727ca6 upstream.
__update_write_rate() uses a Proportion-Differentiation Controller
algorithm to control writeback rate. A dirty target
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit 50e76632339d4655859523a39249dd95ee5e93e7 upstream.
Cpusets vs. suspend-resume is _completely_ broken. And it got noticed
because it now resulted in
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit 50e76632339d4655859523a39249dd95ee5e93e7 upstream.
Cpusets vs. suspend-resume is _completely_ broken. And it got noticed
because it now resulted in non-cpuset usage
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Luca Coelho
commit 01a9c948a09348950515bf2abb6113ed83e696d8 upstream.
The OTP in some SKUs have erroneously allowed 40MHz and 80MHz channels
in the 5.2GHz band. The
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Luca Coelho
commit 01a9c948a09348950515bf2abb6113ed83e696d8 upstream.
The OTP in some SKUs have erroneously allowed 40MHz and 80MHz channels
in the 5.2GHz band. The firmware has been
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 53168215909281a09d3afc6fb51a9d4f81f74d39 upstream.
With TXQs, the AP_VLAN interfaces are resolved to their owner AP
interface when enqueuing the
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Beni Lev
commit 9de981f507474f326e42117858dc9a9321331ae5 upstream.
In struct ieee80211_tx_info, control.vif pointer and rate_driver_data[0]
falls on the same place,
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 53168215909281a09d3afc6fb51a9d4f81f74d39 upstream.
With TXQs, the AP_VLAN interfaces are resolved to their owner AP
interface when enqueuing the frame, which makes sense
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Beni Lev
commit 9de981f507474f326e42117858dc9a9321331ae5 upstream.
In struct ieee80211_tx_info, control.vif pointer and rate_driver_data[0]
falls on the same place, depending on the union
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Hernandez
commit b7edfa235effb4b4a9816c2345620b11609c123e upstream.
Following error will be logged in to message file while trying to
configure target
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Avraham Stern
commit 6e46d8ce894374fc135c96a8d1057c6af1fef237 upstream.
When HW ROC is supported it is possible that after the HW notified
that the ROC has started,
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Hernandez
commit b7edfa235effb4b4a9816c2345620b11609c123e upstream.
Following error will be logged in to message file while trying to
configure target with multiqueue.
"Cmd 0x1f
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Avraham Stern
commit 6e46d8ce894374fc135c96a8d1057c6af1fef237 upstream.
When HW ROC is supported it is possible that after the HW notified
that the ROC has started, the ROC was cancelled and
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Quinn Tran
commit b2e8ae3f0e342a3308b4573790bd42528e51885a upstream.
The Get Port Speed switch command needs the fabric port name of the
remote device. Current code
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Quinn Tran
commit b2e8ae3f0e342a3308b4573790bd42528e51885a upstream.
The Get Port Speed switch command needs the fabric port name of the
remote device. Current code uses the registered WWPN.
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Anup Patel
commit 6d2061b981af165d3e45462e0804b5a1f2f4c7bc upstream.
The mask used in CMPL_START_ADDR_VALUE() should be 27bits instead of
26bits. This incorrect mask
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Zev Weiss
commit 60361e12d01676e23a8de89a5ef4a349ae97f616 upstream.
stack_tracer_disable()/stack_tracer_enable() had been using the wrong
name for the config symbol to
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit e6f77540c067b48dee10f1e33678415bfcc89017 upstream.
The value of "size" comes from the user. When we add "start + size" it
could lead to an
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Zev Weiss
commit 60361e12d01676e23a8de89a5ef4a349ae97f616 upstream.
stack_tracer_disable()/stack_tracer_enable() had been using the wrong
name for the config symbol to enable their
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit e6f77540c067b48dee10f1e33678415bfcc89017 upstream.
The value of "size" comes from the user. When we add "start + size" it
could lead to an integer overflow bug.
It
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Anup Patel
commit 6d2061b981af165d3e45462e0804b5a1f2f4c7bc upstream.
The mask used in CMPL_START_ADDR_VALUE() should be 27bits instead of
26bits. This incorrect mask was causing completion
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit bde59c475e0883e4c4294bcd9b9c7e08ae18c828 upstream.
When an RX BA session is started by the driver, and it has to tell
mac80211 about it, the
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit bde59c475e0883e4c4294bcd9b9c7e08ae18c828 upstream.
When an RX BA session is started by the driver, and it has to tell
mac80211 about it, the corresponding bit in
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit 9cb067ef8a10bb13112e4d1c0ea996ec96527422 upstream.
The result of cpumask_any_and() is invalid when result greater or equal
nr_cpu_ids. The current
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit 9cb067ef8a10bb13112e4d1c0ea996ec96527422 upstream.
The result of cpumask_any_and() is invalid when result greater or equal
nr_cpu_ids. The current check is checking for
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: John Keeping
commit 596a7a1d0989c621c3ae49be73a1d1f9de22eb5a upstream.
On allocating the interrupts routed via a wire-to-MSI bridge, the allocator
iterates over the MSI
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: John Keeping
commit 596a7a1d0989c621c3ae49be73a1d1f9de22eb5a upstream.
On allocating the interrupts routed via a wire-to-MSI bridge, the allocator
iterates over the MSI descriptors to build
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit 12ac1d0f6c3e95732d144ffa65c8b20fbd9aa462 upstream.
for_each_active_irq() iterates the sparse irq allocation bitmap. The caller
must hold
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Hannes Reinecke
commit 4759df905a474d245752c9dc94288e779b8734dd upstream.
Factor out sg_fill_request_table() for better readability.
[mkp: typos, applied by hand]
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Sawan Chandak
commit fcc5b5cd726c0779cd689362aea82cc9d5a61346 upstream.
If FA-WWPN feature disabled on the switch side and enabled for the
adapter, then driver would
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit 12ac1d0f6c3e95732d144ffa65c8b20fbd9aa462 upstream.
for_each_active_irq() iterates the sparse irq allocation bitmap. The caller
must hold sparse_irq_lock. Several code
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Hannes Reinecke
commit 4759df905a474d245752c9dc94288e779b8734dd upstream.
Factor out sg_fill_request_table() for better readability.
[mkp: typos, applied by hand]
Signed-off-by: Hannes
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Sawan Chandak
commit fcc5b5cd726c0779cd689362aea82cc9d5a61346 upstream.
If FA-WWPN feature disabled on the switch side and enabled for the
adapter, then driver would update the port name with
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Tony Asleson
commit 77fa100f27475d08a569b9d51c17722130f089e7 upstream.
If you encounter any errors in bch_cached_dev_attach it will return
a negative error code. The
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Tang Junhui
commit 69daf03adef5f7bc13e0ac86b4b8007df1767aab upstream.
Since bypassed IOs use no bucket, so do not subtract sectors_to_gc to
trigger gc thread.
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Tony Asleson
commit 77fa100f27475d08a569b9d51c17722130f089e7 upstream.
If you encounter any errors in bch_cached_dev_attach it will return
a negative error code. The variable 'v' which
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Tang Junhui
commit 69daf03adef5f7bc13e0ac86b4b8007df1767aab upstream.
Since bypassed IOs use no bucket, so do not subtract sectors_to_gc to
trigger gc thread.
Signed-off-by: tang.junhui
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Chanwoo Choi
commit 9e14de1077e9c34f141cf98bdba60cdd5193d962 upstream.
When the devfreq_add_device fails to register deivce, the memory
leak of devfreq instance happen.
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit 4b758df21ee7081ab41448d21d60367efaa625b3 upstream.
If blkdev_get_by_path() in register_bcache() fails, we try to lookup the
block device using lookup_bdev() to
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Tang Junhui
commit 9baf30972b5568d8b5bc8b3c46a6ec5b58100463 upstream.
gc and write-back get raced (see the email "bcache get stucked" I sended
before):
gc thread
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit fc27fe7e8deef2f37cba3f2be2d52b6ca5eb9d57 upstream.
ALSA sequencer core has a mechanism to load the enumerated devices
automatically, and it's performed in
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Chanwoo Choi
commit 9e14de1077e9c34f141cf98bdba60cdd5193d962 upstream.
When the devfreq_add_device fails to register deivce, the memory
leak of devfreq instance happen. So, this patch fix the
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit 4b758df21ee7081ab41448d21d60367efaa625b3 upstream.
If blkdev_get_by_path() in register_bcache() fails, we try to lookup the
block device using lookup_bdev() to detect which
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Tang Junhui
commit 9baf30972b5568d8b5bc8b3c46a6ec5b58100463 upstream.
gc and write-back get raced (see the email "bcache get stucked" I sended
before):
gc thread
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit fc27fe7e8deef2f37cba3f2be2d52b6ca5eb9d57 upstream.
ALSA sequencer core has a mechanism to load the enumerated devices
automatically, and it's performed in an off-load
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Jose Abreu
commit 1ee55a8f7f6b7ca4c0c59e0b4b4e3584a085c2d3 upstream.
I recently came upon a scenario where I would get a double fault
machine check exception
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt (VMware)
commit 3d9622c12c8873911f4cc0ccdabd0362c2fca06b upstream.
trace_printk() uses 4 buffers, one for each context (normal, softirq, irq
and NMI), such
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Martin Schwidefsky
commit b3e5dc45fd1ec2aa1de6b80008f9295eb17e0659 upstream.
The local TLB flushing code keeps an additional mask in the mm.context,
the
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Sean Young
commit a607f51e5a4c421e2097077db88105402099c528 upstream.
This reverts commit 5be2b76a9ca4ea5fd3e221114d62eeb0d78267ca.
Only when the lirc device is freed, should
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Jose Abreu
commit 1ee55a8f7f6b7ca4c0c59e0b4b4e3584a085c2d3 upstream.
I recently came upon a scenario where I would get a double fault
machine check exception tiriggered by a kernel module.
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt (VMware)
commit 3d9622c12c8873911f4cc0ccdabd0362c2fca06b upstream.
trace_printk() uses 4 buffers, one for each context (normal, softirq, irq
and NMI), such that it does not
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Martin Schwidefsky
commit b3e5dc45fd1ec2aa1de6b80008f9295eb17e0659 upstream.
The local TLB flushing code keeps an additional mask in the mm.context,
the cpu_attach_mask. At the time a global
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Sean Young
commit a607f51e5a4c421e2097077db88105402099c528 upstream.
This reverts commit 5be2b76a9ca4ea5fd3e221114d62eeb0d78267ca.
Only when the lirc device is freed, should we drop our
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Shivasharan S
commit eb3fe263a48b0d27b229c213929c4cb3b1b39a0f upstream.
After a kill adapter, since the cmd_status is not set, the IOCTLs will
be hung
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Long Li
commit 0208eeaa650c5c866a3242201678a19e6dc4a14e upstream.
When storvsc is sending I/O to Hyper-v, it may allocate a bigger buffer
descriptor for large data
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Aleksandar Markovic
commit 7cf64ce4d37f1b4f44365fcf77f565d523819dcd upstream.
Fix the cases of . when any of two multiplicands is
+0 or -0,
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Douglas Leung
commit 2cfa58259f4b65b33ebe8f167019a1f89c6c3289 upstream.
Implement fused multiply-add with correct accuracy.
Fused multiply-add operation has better
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Benjamin Block
commit a099b7b1fc1f0418ab8d79ecf98153e1e134656e upstream.
Up until now zfcp would just ignore the FCP_RESID_OVER flag in the FCP
response IU. When
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Shivasharan S
commit eb3fe263a48b0d27b229c213929c4cb3b1b39a0f upstream.
After a kill adapter, since the cmd_status is not set, the IOCTLs will
be hung in driver resulting in application hang.
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Long Li
commit 0208eeaa650c5c866a3242201678a19e6dc4a14e upstream.
When storvsc is sending I/O to Hyper-v, it may allocate a bigger buffer
descriptor for large data payload that can't fit into
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Aleksandar Markovic
commit 7cf64ce4d37f1b4f44365fcf77f565d523819dcd upstream.
Fix the cases of . when any of two multiplicands is
+0 or -0, and the third input is also +0 or -0. Depending on
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Douglas Leung
commit 2cfa58259f4b65b33ebe8f167019a1f89c6c3289 upstream.
Implement fused multiply-add with correct accuracy.
Fused multiply-add operation has better accuracy than respective
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Benjamin Block
commit a099b7b1fc1f0418ab8d79ecf98153e1e134656e upstream.
Up until now zfcp would just ignore the FCP_RESID_OVER flag in the FCP
response IU. When this flag is set, it is
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Shivasharan S
commit e636a7a430f41efb0ff2727960ce61ef9f8f6769 upstream.
Setting resetwaittime to 0 during a FW fault will result in driver not
calling
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Gary R Hook
commit e652399edba99a5497f0d80f240c9075d3b43493 upstream.
Version 5 CCPs have some new requirements for XTS-AES: the type field
must be specified, and the key
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Steffen Maier
commit 9fe5d2b2fd30aa8c7827ec62cbbe6d30df4fe3e3 upstream.
Without this fix we get SCSI trace records on task management functions
which cannot be
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Shivasharan S
commit ed2983f458bed9dc827ec60c8486253b1669bb52 upstream.
Driver allocated 256 byte MFI frames bytes but while sending MFI frame
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Shivasharan S
commit e636a7a430f41efb0ff2727960ce61ef9f8f6769 upstream.
Setting resetwaittime to 0 during a FW fault will result in driver not
calling the OCR.
Signed-off-by: Kashyap Desai
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Gary R Hook
commit e652399edba99a5497f0d80f240c9075d3b43493 upstream.
Version 5 CCPs have some new requirements for XTS-AES: the type field
must be specified, and the key requires 512 bits,
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Steffen Maier
commit 9fe5d2b2fd30aa8c7827ec62cbbe6d30df4fe3e3 upstream.
Without this fix we get SCSI trace records on task management functions
which cannot be correlated to HBA trace records
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Shivasharan S
commit ed2983f458bed9dc827ec60c8486253b1669bb52 upstream.
Driver allocated 256 byte MFI frames bytes but while sending MFI frame
(embedded inside chain frame of MPT frame) to
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: John Allen
commit afb5519fdb346201728040cab4e08ce53e7ff4fd upstream.
Check if an LMB is assigned before attempting to call dlpar_acquire_drc
in order to avoid any
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit e8a27f836f165c26f867ece7f31eb5c811692319 upstream.
bitmap_resize() does not work for file-backed bitmaps.
The buffer_heads are allocated and initialized when
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Bart Van Assche
commit 4ddd56b003f251091a67c15ae3fe4a5c5c5e390a upstream.
Calling blk_start_queue() from interrupt context with the queue
lock held and without
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Bart Van Assche
commit 7277cc67b3916eed47558c64f9c9c0de00a35cda upstream.
Since put_disk() triggers a disk_release() call and since that
last function calls
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: John Allen
commit afb5519fdb346201728040cab4e08ce53e7ff4fd upstream.
Check if an LMB is assigned before attempting to call dlpar_acquire_drc
in order to avoid any unnecessary rtas calls. This
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit e8a27f836f165c26f867ece7f31eb5c811692319 upstream.
bitmap_resize() does not work for file-backed bitmaps.
The buffer_heads are allocated and initialized when
the bitmap is
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Bart Van Assche
commit 4ddd56b003f251091a67c15ae3fe4a5c5c5e390a upstream.
Calling blk_start_queue() from interrupt context with the queue
lock held and without disabling IRQs, as the skd
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Bart Van Assche
commit 7277cc67b3916eed47558c64f9c9c0de00a35cda upstream.
Since put_disk() triggers a disk_release() call and since that
last function calls blk_put_queue() if disk->queue !=
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: zhangyi (F)
commit b0a5a9589decd07db755d6a8d9c0910d96ff7992 upstream.
Current ext4 quota should always "usage enabled" if the
quota feautre is enabled. But in
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Ethan Barnes
commit 0c96b27305faf06c068b45e07d28336c80dac286 upstream.
If cpuhp_store_callbacks() is called for CPUHP_AP_ONLINE_DYN or
CPUHP_BP_PREPARE_DYN, which are
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: zhangyi (F)
commit b0a5a9589decd07db755d6a8d9c0910d96ff7992 upstream.
Current ext4 quota should always "usage enabled" if the
quota feautre is enabled. But in ext4_orphan_cleanup(), it
turn
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Ethan Barnes
commit 0c96b27305faf06c068b45e07d28336c80dac286 upstream.
If cpuhp_store_callbacks() is called for CPUHP_AP_ONLINE_DYN or
CPUHP_BP_PREPARE_DYN, which are the indicators for
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Sebastian Reichel
commit 91a024e80336528d12b67b5a2e636b9e4467d3ec upstream.
The original patch from Tony uses standby mode bit inverted, which is
not
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Sebastian Reichel
commit 91a024e80336528d12b67b5a2e636b9e4467d3ec upstream.
The original patch from Tony uses standby mode bit inverted, which is
not correct. This fixes all instances in the
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Majd Dibbiny
commit 4c25b7a39005c9243a492b577c3e940eeac36a25 upstream.
When we have a miss in one order of the mkey cache, we try to get
an mkey from a higher order.
We
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Majd Dibbiny
commit 4c25b7a39005c9243a492b577c3e940eeac36a25 upstream.
When we have a miss in one order of the mkey cache, we try to get
an mkey from a higher order.
We still need to check
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Cameron Gutman
commit 122d6a347329818419b032c5a1776e6b3866d9b9 upstream.
We should only see devices with interrupt endpoints. Ignore any other
endpoints that we find,
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Cameron Gutman
commit 122d6a347329818419b032c5a1776e6b3866d9b9 upstream.
We should only see devices with interrupt endpoints. Ignore any other
endpoints that we find, so we don't send try to
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Krzysztof Kozlowski
commit af0b0baa89953aed07034725023371b2fa50a1e6 upstream.
When setting the pin function for external interrupts, the driver used
wrong IO memory address
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Aleksandar Markovic
commit 3444c4eb534c20e44f0d6670b34263efaf8b531f upstream.
Fix the value returned by . fd,fs,ft, if both inputs
are
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Aleksandar Markovic
commit e78bf0dc4789bdea1453595ae89e8db65918e22e upstream.
Fix the value returned by . fd,fs,ft, if both
inputs are
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Krzysztof Kozlowski
commit af0b0baa89953aed07034725023371b2fa50a1e6 upstream.
When setting the pin function for external interrupts, the driver used
wrong IO memory address base. The pin
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Aleksandar Markovic
commit 3444c4eb534c20e44f0d6670b34263efaf8b531f upstream.
Fix the value returned by . fd,fs,ft, if both inputs
are infinite. The previous implementation returned always
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Aleksandar Markovic
commit e78bf0dc4789bdea1453595ae89e8db65918e22e upstream.
Fix the value returned by . fd,fs,ft, if both
inputs are quiet NaNs. The . specifications
state that the returned
701 - 800 of 1308 matches
Mail list logo