diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2016-04-15 15:44:10 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2016-04-15 15:44:10 -0700 |
commit | 2e572599139d27db3aaf540b0d34f0a4f58dfca1 (patch) | |
tree | a96c8d562d50963c923edd777b60a2dc3749462c /arch/arm/mm/proc-v7.S | |
parent | f3c9a1abbe9d4c9565fdb0755e2c7814f32d4f62 (diff) | |
parent | a7297a6a3a3322b054592e8e988981d2f5f29cc4 (diff) | |
download | talos-obmc-linux-2e572599139d27db3aaf540b0d34f0a4f58dfca1.tar.gz talos-obmc-linux-2e572599139d27db3aaf540b0d34f0a4f58dfca1.zip |
Merge branch 'for-linus' of git://git.kernel.dk/linux-block
Pull block fixes from Jens Axboe:
"A few fixes for the current series. This contains:
- Two fixes for NVMe:
One fixes a reset race that can be triggered by repeated
insert/removal of the module.
The other fixes an issue on some platforms, where we get probe
timeouts since legacy interrupts isn't working. This used not to
be a problem since we had the worker thread poll for completions,
but since that was killed off, it means those poor souls can't
successfully probe their NVMe device. Use a proper IRQ check and
probe (msi-x -> msi ->legacy), like most other drivers to work
around this. Both from Keith.
- A loop corruption issue with offset in iters, from Ming Lei.
- A fix for not having the partition stat per cpu ref count
initialized before sending out the KOBJ_ADD, which could cause user
space to access the counter prior to initialization. Also from
Ming Lei.
- A fix for using the wrong congestion state, from Kaixu Xia"
* 'for-linus' of git://git.kernel.dk/linux-block:
block: loop: fix filesystem corruption in case of aio/dio
NVMe: Always use MSI/MSI-x interrupts
NVMe: Fix reset/remove race
writeback: fix the wrong congested state variable definition
block: partition: initialize percpuref before sending out KOBJ_ADD
Diffstat (limited to 'arch/arm/mm/proc-v7.S')
0 files changed, 0 insertions, 0 deletions