s390 patches for 2.6.23-rc3
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest10 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/10 | cio: dont forget to set last slot to NULL in ccw_uevent().drivers/ | +4 | 0 replies | |
| 2/10 | cio: change confusing message in cmf.drivers/ | +3 | 0 replies | |
| 3/10 | qdio: fix EQBS handling on CCQ96drivers/ | +2 | 0 replies | |
| 4/10 | qdio: Refresh buffer states for IQDIO Asynchronous output queuedrivers/ | +2 | 0 replies | |
| 5/10 | vmur: fix diag14 exceptions with addresses > 2GB.arch/ arch/ arch/ +9 more | +150 | 0 replies | |
| 6/10 | vmur: fix reference counting for vmur device structuredrivers/ drivers/ | +161 | 0 replies | |
| 7/10 | disassembler: fix b2 opcodes like srst, bsg, and othersarch/ | +1 | 0 replies | |
| 8/10 | hypfs: inode corruption due to missing lockingarch/ | +25 | 0 replies | |
| 9/10 | kprobes: fix instruction length calculationarch/ | +1 | 0 replies | |
| 10/10 | Change atomic_read/set to inline functions with barrier semantics.include/ | +22 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [patch 00/10] s390 patches for 2.6.23-rc3
10 patches for s390. The new vmur driver still has some rough edges but we are getting there. Patch #10 is our solution to the atomic_t vs. volatile problem. As prediced by Linus adding a barrier to atomic_read/atomic_set has close to zero impact to the generated code and adding the barrier to atomic_read/atomic_set forces the compiler to read/write the value to/from memory. This seems to be the most convenient way to solve this problem.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.