1. 10 1月, 2006 7 次提交
  2. 06 1月, 2006 4 次提交
  3. 13 12月, 2005 2 次提交
  4. 09 11月, 2005 11 次提交
  5. 07 11月, 2005 1 次提交
  6. 29 10月, 2005 1 次提交
  7. 10 9月, 2005 2 次提交
  8. 06 9月, 2005 1 次提交
  9. 05 9月, 2005 1 次提交
  10. 02 8月, 2005 1 次提交
  11. 13 7月, 2005 1 次提交
  12. 26 6月, 2005 1 次提交
    • C
      [PATCH] Cleanup patch for process freezing · 3e1d1d28
      Christoph Lameter 提交于
      1. Establish a simple API for process freezing defined in linux/include/sched.h:
      
         frozen(process)		Check for frozen process
         freezing(process)		Check if a process is being frozen
         freeze(process)		Tell a process to freeze (go to refrigerator)
         thaw_process(process)	Restart process
         frozen_process(process)	Process is frozen now
      
      2. Remove all references to PF_FREEZE and PF_FROZEN from all
         kernel sources except sched.h
      
      3. Fix numerous locations where try_to_freeze is manually done by a driver
      
      4. Remove the argument that is no longer necessary from two function calls.
      
      5. Some whitespace cleanup
      
      6. Clear potential race in refrigerator (provides an open window of PF_FREEZE
         cleared before setting PF_FROZEN, recalc_sigpending does not check
         PF_FROZEN).
      
      This patch does not address the problem of freeze_processes() violating the rule
      that a task may only modify its own flags by setting PF_FREEZE. This is not clean
      in an SMP environment. freeze(process) is therefore not SMP safe!
      Signed-off-by: NChristoph Lameter <christoph@lameter.com>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      3e1d1d28
  13. 24 6月, 2005 2 次提交
  14. 22 6月, 2005 1 次提交
    • J
      [PATCH] I2C: Kill address ranges in non-sensors i2c chip drivers · b3d5496e
      Jean Delvare 提交于
      Some months ago, you killed the address ranges mechanism from all
      sensors i2c chip drivers (both the module parameters and the in-code
      address lists). I think it was a very good move, as the ranges can
      easily be replaced by individual addresses, and this allowed for
      significant cleanups in the i2c core (let alone the impressive size
      shrink for all these drivers).
      
      Unfortunately you did not do the same for non-sensors i2c chip drivers.
      These need the address ranges even less, so we could get rid of the
      ranges here as well for another significant i2c core cleanup. Here comes
      a patch which does just that. Since the process is exactly the same as
      what you did for the other drivers set already, I did not split this one
      in parts.
      
      A documentation update is included.
      
      The change saves 308 bytes in the i2c core, and an average 1382 bytes
      for chip drivers which use I2C_CLIENT_INSMOD, 126 bytes for those which
      do not.
      
      This change is required if we want to merge the sensors and non-sensors
      i2c code (and we want to do this).
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      
      Index: gregkh-2.6/Documentation/i2c/writing-clients
      ===================================================================
      b3d5496e
  15. 01 5月, 2005 1 次提交
  16. 17 4月, 2005 2 次提交