1. 11 10月, 2006 1 次提交
  2. 20 9月, 2006 1 次提交
  3. 12 7月, 2006 2 次提交
    • C
      [S390] path grouping and path verifications fixes. · 7e560814
      Cornelia Huck 提交于
      1. Multipath devices for which SetPGID is not supported are not handled well.
         Use NOP ccws for path verification (sans path grouping) when SetPGID is not
         supported.
      2. Check for PGIDs already set with SensePGID on _all_ paths (not just the
         first one) and try to find a common one. Moan if no common PGID can be
         found (and use NOP verification). If no PGIDs have been set, use the css
         global PGID (as before). (Rationale: SetPGID will get a command reject if
         the PGID it tries to set does not match the already set PGID.)
      3. Immediately before reboot, issue RESET CHANNEL PATH (rcp) on all chpids. This
         will remove the old PGIDs. rcp will generate solicited CRWs which can be
         savely ignored by the machine check handler (all other actions create
         unsolicited CRWs).
      Signed-off-by: NCornelia Huck <cornelia.huck@de.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      7e560814
    • C
      [S390] subchannel register/unregister mutex. · 6ab4879a
      Cornelia Huck 提交于
      Add a reg_mutex to prevent unregistering a subchannel before it has been
      registered. Since 2.6.17, we've seen oopses in kslowcrw when a device is
      found to be not operational during sense id when doing initial device
      recognition; it is not clear yet why that particular problem was not (yet)
      observed with earlier kernels...
      Signed-off-by: NCornelia Huck <cornelia.huck@de.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      6ab4879a
  4. 29 6月, 2006 1 次提交
  5. 24 3月, 2006 2 次提交
  6. 15 3月, 2006 1 次提交
  7. 02 2月, 2006 1 次提交
  8. 15 1月, 2006 1 次提交
  9. 14 1月, 2006 1 次提交
  10. 07 1月, 2006 6 次提交
  11. 26 6月, 2005 1 次提交
  12. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4