1. 09 11月, 2013 1 次提交
    • A
      mtip32xx: Add SRSI support · 8f8b8995
      Asai Thambi S P 提交于
      This patch add support for SRSI(Surprise Removal Surprise Insertion).
      
      Approach:
      ---------
      Surprise Removal:
      -----------------
      On surprise removal of the device, gendisk, request queue, device index, sysfs
      entries, etc are retained as long as device is in use - mounted filesystem,
      device opened by an application, etc. The service thread breaks out of the main
      while loop, waits for pci remove to exit, and then waits for device to become
      free. When there no holders of the device, service thread cleans up the block
      and device related stuff and returns.
      
      Surprise Insertion:
      -------------------
      No change, this scenario follows the normal pci probe() function flow.
      Signed-off-by: NAsai Thambi S P <asamymuthupa@micron.com>
      Signed-off-by: NJens Axboe <axboe@kernel.dk>
      8f8b8995
  2. 04 7月, 2013 1 次提交
  3. 15 5月, 2013 2 次提交
  4. 30 4月, 2013 1 次提交
  5. 14 4月, 2013 2 次提交
  6. 04 4月, 2013 4 次提交
  7. 22 3月, 2013 1 次提交
  8. 12 1月, 2013 2 次提交
    • F
      drivers/block/mtip32xx/mtip32xx.c:1726:5: sparse: symbol 'mtip_send_trim' was... · 478c030e
      Fengguang Wu 提交于
      drivers/block/mtip32xx/mtip32xx.c:1726:5: sparse: symbol 'mtip_send_trim' was not declared. Should it be static?
      
      Hi Asai,
      
      FYI, there are new sparse warnings show up in
      
      tree:   git://git.kernel.dk/linux-block.git for-3.9/drivers
      head:   3d6a8743
      commit: 15283469 [2/3] mtip32xx: add trim support
      
      >> drivers/block/mtip32xx/mtip32xx.c:1726:5: sparse: symbol 'mtip_send_trim' was not declared. Should it be static?
         drivers/block/mtip32xx/mtip32xx.c:3348:17: sparse: cast to restricted __le32
         drivers/block/mtip32xx/mtip32xx.c:4125:1: sparse: symbol 'mtip_workq_sdbf0' was not declared. Should it be static?
         drivers/block/mtip32xx/mtip32xx.c:4126:1: sparse: symbol 'mtip_workq_sdbf1' was not declared. Should it be static?
         drivers/block/mtip32xx/mtip32xx.c:4127:1: sparse: symbol 'mtip_workq_sdbf2' was not declared. Should it be static?
         drivers/block/mtip32xx/mtip32xx.c:4128:1: sparse: symbol 'mtip_workq_sdbf3' was not declared. Should it be static?
         drivers/block/mtip32xx/mtip32xx.c:4129:1: sparse: symbol 'mtip_workq_sdbf4' was not declared. Should it be static?
         drivers/block/mtip32xx/mtip32xx.c:4130:1: sparse: symbol 'mtip_workq_sdbf5' was not declared. Should it be static?
         drivers/block/mtip32xx/mtip32xx.c:4131:1: sparse: symbol 'mtip_workq_sdbf6' was not declared. Should it be static?
         drivers/block/mtip32xx/mtip32xx.c:4132:1: sparse: symbol 'mtip_workq_sdbf7' was not declared. Should it be static?
         drivers/block/mtip32xx/mtip32xx.c: In function 'mtip_hw_read_flags':
         drivers/block/mtip32xx/mtip32xx.c:2804:1: warning: the frame size of 1036 bytes is larger than 1024 bytes [-Wframe-larger-than=]
         drivers/block/mtip32xx/mtip32xx.c: In function 'mtip_hw_read_registers':
         drivers/block/mtip32xx/mtip32xx.c:2781:1: warning: the frame size of 1044 bytes is larger than 1024 bytes [-Wframe-larger-than=]
      Signed-off-by: NJens Axboe <axboe@kernel.dk>
      478c030e
    • F
      drivers/block/mtip32xx/mtip32xx.c:4029:1: sparse: symbol 'mtip_workq_sdbf0'... · 25bac122
      Fengguang Wu 提交于
      drivers/block/mtip32xx/mtip32xx.c:4029:1: sparse: symbol 'mtip_workq_sdbf0' was not declared. Should it be static?
      
      Hi Asai,
      
      FYI, there are new sparse warnings show up in
      
      tree:   git://git.kernel.dk/linux-block.git for-3.9/drivers
      head:   3d6a8743
      commit: 16c906e5 [1/3] mtip32xx: Add workqueue and NUMA support
      
      drivers/block/mtip32xx/mtip32xx.c:3267:17: sparse: cast to restricted __le32
      >> drivers/block/mtip32xx/mtip32xx.c:4029:1: sparse: symbol 'mtip_workq_sdbf0' was not declared. Should it be static?
      >> drivers/block/mtip32xx/mtip32xx.c:4030:1: sparse: symbol 'mtip_workq_sdbf1' was not declared. Should it be static?
      >> drivers/block/mtip32xx/mtip32xx.c:4031:1: sparse: symbol 'mtip_workq_sdbf2' was not declared. Should it be static?
      >> drivers/block/mtip32xx/mtip32xx.c:4032:1: sparse: symbol 'mtip_workq_sdbf3' was not declared. Should it be static?
      >> drivers/block/mtip32xx/mtip32xx.c:4033:1: sparse: symbol 'mtip_workq_sdbf4' was not declared. Should it be static?
      >> drivers/block/mtip32xx/mtip32xx.c:4034:1: sparse: symbol 'mtip_workq_sdbf5' was not declared. Should it be static?
      >> drivers/block/mtip32xx/mtip32xx.c:4035:1: sparse: symbol 'mtip_workq_sdbf6' was not declared. Should it be static?
      >> drivers/block/mtip32xx/mtip32xx.c:4036:1: sparse: symbol 'mtip_workq_sdbf7' was not declared. Should it be static?
         drivers/block/mtip32xx/mtip32xx.c: In function 'mtip_hw_read_flags':
         drivers/block/mtip32xx/mtip32xx.c:2723:1: warning: the frame size of 1036 bytes is larger than 1024 bytes [-Wframe-larger-than=]
         drivers/block/mtip32xx/mtip32xx.c: In function 'mtip_hw_read_registers':
         drivers/block/mtip32xx/mtip32xx.c:2700:1: warning: the frame size of 1044 bytes is larger than 1024 bytes [-Wframe-larger-than=]
      
      Please consider folding the below diff :-)
      Signed-off-by: NJens Axboe <axboe@kernel.dk>
      25bac122
  9. 11 1月, 2013 4 次提交
  10. 23 11月, 2012 4 次提交
  11. 30 10月, 2012 1 次提交
  12. 13 9月, 2012 7 次提交
  13. 05 6月, 2012 2 次提交
  14. 31 5月, 2012 8 次提交