1. 21 1月, 2014 17 次提交
  2. 20 1月, 2014 1 次提交
  3. 19 1月, 2014 1 次提交
  4. 18 1月, 2014 1 次提交
  5. 17 1月, 2014 1 次提交
    • M
      e1000e: Fix compilation warning when !CONFIG_PM_SLEEP · 38a529b5
      Mika Westerberg 提交于
      Commit 7509963c (e1000e: Fix a compile flag mis-match for
      suspend/resume) moved suspend and resume hooks to be available when
      CONFIG_PM is set. However, it can be set even if CONFIG_PM_SLEEP is not set
      causing following warnings to be emitted:
      
      drivers/net/ethernet/intel/e1000e/netdev.c:6178:12: warning:
        	‘e1000_suspend’ defined but not used [-Wunused-function]
      
      drivers/net/ethernet/intel/e1000e/netdev.c:6185:12: warning:
      	‘e1000_resume’ defined but not used [-Wunused-function]
      
      To fix this make the hooks to be available only when CONFIG_PM_SLEEP is set
      and remove CONFIG_PM wrapping from driver ops because this is already
      handled by SET_SYSTEM_SLEEP_PM_OPS() and SET_RUNTIME_PM_OPS().
      Signed-off-by: NMika Westerberg <mika.westerberg@linux.intel.com>
      Cc: Dave Ertman <davidx.m.ertman@intel.com>
      Cc: Aaron Brown <aaron.f.brown@intel.com>
      Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      38a529b5
  6. 16 1月, 2014 4 次提交
  7. 15 1月, 2014 12 次提交
  8. 14 1月, 2014 3 次提交
    • E
      s390/qdio: bridgeport support - CHSC part · 1c59a861
      Eugene Crosser 提交于
      Introduce function for the "Perform network-subchannel operation"
      CHSC command with operation code "bridgeport information",
      and bit definitions for "characteristics" pertaning to this command.
      Signed-off-by: NEugene Crosser <eugene.crosser@ru.ibm.com>
      Reviewed-by: NSebastian Ott <sebott@linux.vnet.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      1c59a861
    • B
      net: usbnet: fix SG initialisation · fdc3452c
      Bjørn Mork 提交于
      Commit 60e453a9 ("USBNET: fix handling padding packet")
      added an extra SG entry in case padding is necessary, but
      failed to update the initialisation of the list. This can
      cause list traversal to fall off the end of the list,
      resulting in an oops.
      
      Fixes: 60e453a9 ("USBNET: fix handling padding packet")
      Reported-by: NThomas Kear <thomas@kear.co.nz>
      Cc: Ming Lei <ming.lei@canonical.com>
      Signed-off-by: NBjørn Mork <bjorn@mork.no>
      Tested-by: NMing Lei <ming.lei@canonical.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      fdc3452c
    • N
      md: fix problem when adding device to read-only array with bitmap. · 8313b8e5
      NeilBrown 提交于
      If an array is started degraded, and then the missing device
      is found it can be re-added and a minimal bitmap-based recovery
      will bring it fully up-to-date.
      
      If the array is read-only a recovery would not be allowed.
      But also if the array is read-only and the missing device was
      present very recently, then there could be no need for any
      recovery at all, so we simply include the device in the read-only
      array without any recovery.
      
      However... if the missing device was removed a little longer ago
      it could be missing some updates, but if a bitmap is present it will
      be conditionally accepted pending a bitmap-based update.  We don't
      currently detect this case properly and will include that old
      device into the read-only array with no recovery even though it really
      needs a recovery.
      
      This patch keeps track of whether a bitmap-based-recovery is really
      needed or not in the new Bitmap_sync rdev flag.  If that is set,
      then the device will not be added to a read-only array.
      
      Cc: Andrei Warkentin <andreiw@vmware.com>
      Fixes: d70ed2e4
      Cc: stable@vger.kernel.org (3.2+)
      Signed-off-by: NNeilBrown <neilb@suse.de>
      8313b8e5