1. 17 10月, 2007 1 次提交
    • S
      firewire: fw-ohci: enforce read order for selfID generation · ee71c2f9
      Stefan Richter 提交于
      It seems unlikely, but access to self_id_cpu[0] could at least in theory
      be deferred until after the loop over self_id_cpu[1..n] or even after
      the subsequent reg_read.  Enforce the desired order by a read barrier.
      
      Also prevent the reg_read from being reordered relative to the for loop.
      This isn't necessary if the loop's conditional printk counts as an
      implicit barrier, but better make it explicit.
      
      (self_id_cpu[] is a coherent DMA buffer.)
      Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
      ee71c2f9
  2. 08 9月, 2007 1 次提交
  3. 03 8月, 2007 1 次提交
  4. 19 7月, 2007 2 次提交
  5. 10 7月, 2007 1 次提交
  6. 29 6月, 2007 1 次提交
  7. 16 6月, 2007 1 次提交
  8. 01 6月, 2007 1 次提交
  9. 28 5月, 2007 1 次提交
  10. 16 5月, 2007 1 次提交
  11. 11 5月, 2007 5 次提交
  12. 12 4月, 2007 2 次提交
  13. 29 3月, 2007 2 次提交
  14. 16 3月, 2007 2 次提交
  15. 10 3月, 2007 18 次提交