1. 11 Oct, 2009 22 commits
  2. 09 Oct, 2009 1 commit
  3. 07 Oct, 2009 1 commit
  4. 06 Oct, 2009 2 commits
  5. 05 Oct, 2009 1 commit
  6. 02 Oct, 2009 3 commits
  7. 01 Oct, 2009 2 commits
  8. 30 Sep, 2009 1 commit
  9. 29 Sep, 2009 1 commit
  10. 28 Sep, 2009 2 commits
  11. 27 Sep, 2009 4 commits
    • Linus Torvalds's avatar
      Linux 2.6.32-rc1 · 17d857be
      Linus Torvalds authored
      17d857be
    • Linus Torvalds's avatar
      alpha: Fix duplicate <asm/thread_info.h> include · b3b75cef
      Linus Torvalds authored
      .. duplicated by merging the same fix twice, for details see commit
      0d9df251 ("Merge
      git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild-fixes")
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      b3b75cef
    • Dave Young's avatar
      tty: Fix regressions caused by commit b50989dc · f278a2f7
      Dave Young authored
      The following commit made console open fails while booting:
      
      	commit b50989dc
      	Author: Alan Cox <alan@linux.intel.com>
      	Date:   Sat Sep 19 13:13:22 2009 -0700
      
      	tty: make the kref destructor occur asynchronously
      
      Due to tty release routines run in a workqueue now, error like the
      following will be reported while booting:
      
      INIT open /dev/console Input/output error
      
      It also causes hibernation regression to appear as reported at
      http://bugzilla.kernel.org/show_bug.cgi?id=14229
      
      The reason is that now there's latency issue with closing, but when
      we open a "closing not finished" tty, -EIO will be returned.
      
      Fix it as per the following Alan's suggestion:
      
        Fun but it's actually not a bug and the fix is wrong in itself as
        the port may be closing but not yet being destructed, in which case
        it seems to do the wrong thing.  Opening a tty that is closing (and
        could be closing for long periods) is supposed to return -EIO.
      
        I suspect a better way to deal with this and keep the old console
        timing is to split tty->shutdown into two functions.
      
        tty->shutdown() - called synchronously just before we dump the tty
        onto the waitqueue for destruction
      
        tty->cleanup() - called when the destructor runs.
      
        We would then do the shutdown part which can occur in IRQ context
        fine, before queueing the rest of the release (from tty->magic = 0
        ...  the end) to occur asynchronously
      
        The USB update in -next would then need a call like
      
             if (tty->cleanup)
                     tty->cleanup(tty);
      
        at the top of the async function and the USB shutdown to be split
        between shutdown and cleanup as the USB resource cleanup and final
        tidy cannot occur synchronously as it needs to sleep.
      
        In other words the logic becomes
      
             final kref put
                     make object unfindable
      
             async
                     clean it up
      Signed-off-by: default avatarDave Young <hidave.darkstar@gmail.com>
      [ rjw: Rebased on top of 2.6.31-git, reworked the changelog. ]
      Signed-off-by: default avatar"Rafael J. Wysocki" <rjw@sisk.pl>
      [ Changed serial naming to match new rules, dropped tty_shutdown as per
        comments from Alan Stern  - Linus ]
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      f278a2f7
    • Linus Torvalds's avatar
      ACPI: kill "unused variable ‘i’" warning · 569ec4cc
      Linus Torvalds authored
      Commit 3d5b6fb4 ("ACPI: Kill overly
      verbose "power state" log messages") removed the actual use of this
      variable, but didn't remove the variable itself, resulting in build
      warnings like
      
        drivers/acpi/processor_idle.c: In function ‘acpi_processor_power_init’:
        drivers/acpi/processor_idle.c:1169: warning: unused variable ‘i’
      
      Just get rid of the now unused variable.
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      569ec4cc