1. 15 6月, 2008 1 次提交
  2. 05 6月, 2008 1 次提交
    • A
      airo warning fix · b212f337
      Andrew Morton 提交于
      WARNING: space prohibited between function name and open parenthesis '('
      #22: FILE: drivers/net/wireless/airo.c:2907:
      +	while ((IN4500 (ai, COMMAND) & COMMAND_BUSY) && (delay < 10000)) {
      
      total: 0 errors, 1 warnings, 8 lines checked
      
      ./patches/wireless-airo-waitbusy-wont-delay.patch has style problems, please review.  If any of these errors
      are false positives report them to the maintainer, see
      CHECKPATCH in MAINTAINERS.
      
      Please run checkpatch prior to sending patches
      
      Cc: Dan Williams <dcbw@redhat.com>
      Cc: Roel Kluin <roel.kluin@gmail.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      b212f337
  3. 17 5月, 2008 2 次提交
  4. 15 5月, 2008 1 次提交
  5. 29 4月, 2008 3 次提交
  6. 29 1月, 2008 19 次提交
  7. 11 10月, 2007 6 次提交
  8. 18 7月, 2007 1 次提交
    • R
      Freezer: make kernel threads nonfreezable by default · 83144186
      Rafael J. Wysocki 提交于
      Currently, the freezer treats all tasks as freezable, except for the kernel
      threads that explicitly set the PF_NOFREEZE flag for themselves.  This
      approach is problematic, since it requires every kernel thread to either
      set PF_NOFREEZE explicitly, or call try_to_freeze(), even if it doesn't
      care for the freezing of tasks at all.
      
      It seems better to only require the kernel threads that want to or need to
      be frozen to use some freezer-related code and to remove any
      freezer-related code from the other (nonfreezable) kernel threads, which is
      done in this patch.
      
      The patch causes all kernel threads to be nonfreezable by default (ie.  to
      have PF_NOFREEZE set by default) and introduces the set_freezable()
      function that should be called by the freezable kernel threads in order to
      unset PF_NOFREEZE.  It also makes all of the currently freezable kernel
      threads call set_freezable(), so it shouldn't cause any (intentional)
      change of behaviour to appear.  Additionally, it updates documentation to
      describe the freezing of tasks more accurately.
      
      [akpm@linux-foundation.org: build fixes]
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Acked-by: NNigel Cunningham <nigel@nigel.suspend2.net>
      Cc: Pavel Machek <pavel@ucw.cz>
      Cc: Oleg Nesterov <oleg@tv-sign.ru>
      Cc: Gautham R Shenoy <ego@in.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      83144186
  9. 11 7月, 2007 5 次提交
  10. 09 5月, 2007 1 次提交