1. 16 1月, 2015 25 次提交
  2. 09 1月, 2015 1 次提交
  3. 27 12月, 2014 1 次提交
  4. 24 12月, 2014 1 次提交
  5. 23 12月, 2014 2 次提交
  6. 22 12月, 2014 2 次提交
  7. 20 12月, 2014 4 次提交
  8. 19 12月, 2014 4 次提交
    • R
      tty: 8250_omap: Replace CONFIG_PM_RUNTIME with CONFIG_PM · 71504e51
      Rafael J. Wysocki 提交于
      The 8250_omap serial driver is a new user of CONFIG_PM_RUNTIME.
      
      However, after commit b2b49ccb (PM: Kconfig: Set PM_RUNTIME if
      PM_SLEEP is selected) PM_RUNTIME is always set if PM is set, so
      #ifdef blocks depending on CONFIG_PM_RUNTIME may now be changed to
      depend on CONFIG_PM.
      
      Replace CONFIG_PM_RUNTIME with CONFIG_PM in 8250_omap.c.
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      Acked-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      71504e51
    • R
      spi: Replace CONFIG_PM_RUNTIME with CONFIG_PM · 47164fdb
      Rafael J. Wysocki 提交于
      A couple of new CONFIG_PM_RUNTIME users have been added recently
      in the SPI subsystem.
      
      However, after commit b2b49ccb (PM: Kconfig: Set PM_RUNTIME if
      PM_SLEEP is selected) PM_RUNTIME is always set if PM is set, so
      #ifdef blocks depending on CONFIG_PM_RUNTIME may now be changed to
      depend on CONFIG_PM.
      
      Replace CONFIG_PM_RUNTIME with CONFIG_PM everywhere under
      drivers/spi/ (again).
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      Acked-by: NMark Brown <broonie@kernel.org>
      47164fdb
    • T
      tick/powerclamp: Remove tick_nohz_idle abuse · a5fd9733
      Thomas Gleixner 提交于
      commit 4dbd2771 "tick: export nohz tick idle symbols for module
      use" was merged via the thermal tree without an explicit ack from the
      relevant maintainers.
      
      The exports are abused by the intel powerclamp driver which implements
      a fake idle state from a sched FIFO task. This causes all kinds of
      wreckage in the NOHZ core code which rightfully assumes that
      tick_nohz_idle_enter/exit() are only called from the idle task itself.
      
      Recent changes in the NOHZ core lead to a failure of the powerclamp
      driver and now people try to hack completely broken and backwards
      workarounds into the NOHZ core code. This is completely unacceptable
      and just papers over the real problem. There are way more subtle
      issues lurking around the corner.
      
      The real solution is to fix the powerclamp driver by rewriting it with
      a sane concept, but that's beyond the scope of this.
      
      So the only solution for now is to remove the calls into the core NOHZ
      code from the powerclamp trainwreck along with the exports. 
      
      Fixes: d6d71ee4 "PM: Introduce Intel PowerClamp Driver"
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Cc: Preeti U Murthy <preeti@linux.vnet.ibm.com>
      Cc: Viresh Kumar <viresh.kumar@linaro.org>
      Cc: Frederic Weisbecker <fweisbec@gmail.com>
      Cc: Fengguang Wu <fengguang.wu@intel.com>
      Cc: Frederic Weisbecker <frederic@kernel.org>
      Cc: Pan Jacob jun <jacob.jun.pan@intel.com>
      Cc: LKP <lkp@01.org>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Cc: Zhang Rui <rui.zhang@intel.com>
      Cc: stable@vger.kernel.org
      Link: http://lkml.kernel.org/r/alpine.DEB.2.11.1412181110110.17382@nanosSigned-off-by: NThomas Gleixner <tglx@linutronix.de>
      a5fd9733
    • N
      target: Allow AllRegistrants to re-RESERVE existing reservation · ae450e24
      Nicholas Bellinger 提交于
      This patch changes core_scsi3_pro_release() logic to allow an
      existing AllRegistrants type reservation to be re-reserved by
      any registered I_T nexus.
      
      This addresses a issue where AllRegistrants type RESERVE was
      receiving RESERVATION_CONFLICT status if dev_pr_res_holder did
      not match the same I_T nexus, instead of just returning GOOD
      status following spc4r34 Section 5.9.9:
      
      "If the device server receives a PERSISTENT RESERVE OUT command
       with RESERVE service action where the TYPE field and the SCOPE
       field contain the same values as the existing type and scope
       from a persistent reservation holder, it shall not make any
       change to the existing persistent reservation and shall complete
       the command with GOOD status."
      Reported-by: NIlias Tsitsimpis <i.tsitsimpis@gmail.com>
      Cc: Ilias Tsitsimpis <i.tsitsimpis@gmail.com>
      Cc: Lee Duncan <lduncan@suse.com>
      Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
      Signed-off-by: NNicholas Bellinger <nab@linux-iscsi.org>
      ae450e24