1. 01 12月, 2011 1 次提交
  2. 16 3月, 2011 3 次提交
  3. 07 12月, 2009 1 次提交
  4. 11 9月, 2009 2 次提交
  5. 25 12月, 2008 3 次提交
    • S
      [S390] cio: introduce cio_commit_config · 13952ec1
      Sebastian Ott 提交于
      To change the configuration of a subchannel we alter the modifiable
      bits of the subchannel's schib field and issue a modify subchannel.
      There can be the case that not all changes were applied -or worse-
      quietly overwritten by the hardware. With the next store subchannel
      we obtain the current state of the hardware but lose our target
      configuration.
      
      With this patch we introduce a subchannel_config structure which
      contains the target subchannel configuration. Additionally the msch
      wrapper cio_modify is replaced with cio_commit_config which
      copies the desired changes to a temporary schib. msch is then
      called with the temporary schib. This schib is only written back
      to the subchannel if all changes were applied.
      Signed-off-by: NSebastian Ott <sebott@linux.vnet.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      13952ec1
    • S
      [S390] cio: introduce cio_update_schib · cdb912a4
      Sebastian Ott 提交于
      There is the chance that we get condition code 0 for a stsch but
      the resulting schib is not vaild. In the current code there are
      2 cases:
      * we do a check for validity of the schib after stsch, but at this
        time we have already stored the invaild schib in the subchannel
        structure. This may lead to problems.
      * we don't do a check for validity, which is not that good either.
      
      The patch addresses both issues by introducing the stsch wrapper
      cio_update_schib which performs stsch on a local schib. This schib
      is only written back to the subchannel if it's valid.
      
      side note: For some functions (chp_events) the return codes are
      different now (-ENXIO vs -ENODEV) but this shouldn't do harm
      since the caller doesn't check for _specific_ errors.
      Signed-off-by: NSebastian Ott <sebott@linux.vnet.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      cdb912a4
    • C
      [S390] cio: Dont fail probe for I/O subchannels. · 90ed2b69
      Cornelia Huck 提交于
      If we fail the probe for an I/O subchannel, we won't be able
      to unregister it again since there are no sch_event()
      callbacks for unbound subchannels. Just succeed the probe in
      any case and schedule unregistering the subchannel.
      Signed-off-by: NCornelia Huck <cornelia.huck@de.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      90ed2b69
  6. 11 10月, 2008 1 次提交
  7. 14 7月, 2008 6 次提交
  8. 07 5月, 2008 1 次提交
  9. 30 4月, 2008 1 次提交
  10. 17 4月, 2008 1 次提交
  11. 26 1月, 2008 3 次提交
  12. 27 4月, 2007 2 次提交
  13. 08 12月, 2006 2 次提交
  14. 12 7月, 2006 1 次提交
  15. 07 1月, 2006 1 次提交
  16. 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