1. 20 10月, 2007 1 次提交
  2. 17 10月, 2007 1 次提交
  3. 19 9月, 2007 1 次提交
  4. 17 9月, 2007 1 次提交
    • H
      ACPI: thinkpad-acpi: revert new 2.6.23 CONFIG_THINKPAD_ACPI_INPUT_ENABLED option · ff80f137
      Henrique de Moraes Holschuh 提交于
      Revert new 2.6.23 CONFIG_THINKPAD_ACPI_INPUT_ENABLED Kconfig option because
      it would create a legacy we don't want to support.
      
      CONFIG_THINKPAD_ACPI_INPUT_ENABLED was added to try to fix an issue that is
      now moot with the addition of the netlink ACPI event report interface to
      the ACPI core.
      
      Now that ACPI core can send events over netlink, we can use a different
      strategy to keep backwards compatibility with older userspace, without the
      need for the CONFIG_THINKPAD_ACPI_INPUT_ENABLED games.  And it arrived
      before CONFIG_THINKPAD_ACPI_INPUT_ENABLED made it to a stable mainline
      kernel, even, which is Good.
      
      This patch is in sync with some changes to thinkpad-acpi backports, that
      will keep things sane for userspace across different combinations of kernel
      versions, thinkpad-acpi backports (or the lack thereof), and userspace
      capabilities:
      
      Unless a module parameter is used, thinkpad-acpi will now behave in such a
      way that it will work well (by default) with userspace that still uses only
      the old ACPI procfs event interface and doesn't care for thinkpad-acpi
      input devices.
      
      It will also always work well with userspace that has been updated to use
      both the thinkpad-acpi input devices, and ACPI core netlink event
      interface, regardless of any module parameter.
      
      The module parameter was added to allow thinkpad-acpi to work with
      userspace that has been partially updated to use thinkpad-acpi input
      devices, but not the new ACPI core netlink event interface.  To use this
      mode of hot key reporting, one has to specify the hotkey_report_mode=2
      module parameter.
      
      The thinkpad-acpi driver exports the value of hotkey_report_mode through
      sysfs, as well.  thinkpad-acpi backports to older kernels, that do not
      support the new ACPI core netlink interface, have code to allow userspace
      to switch hotkey_report_mode at runtime through sysfs.  This capability
      will not be provided in mainline thinkpad-acpi as it is not needed there.
      Signed-off-by: NHenrique de Moraes Holschuh <hmh@hmh.eng.br>
      Cc: Michael S. Tsirkin <mst@dev.mellanox.co.il>
      Cc: Hugh Dickins <hugh@veritas.com>
      Cc: Richard Hughes <hughsient@gmail.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      ff80f137
  5. 29 8月, 2007 1 次提交
  6. 19 8月, 2007 1 次提交
  7. 08 8月, 2007 1 次提交
  8. 22 7月, 2007 2 次提交
  9. 18 7月, 2007 1 次提交
  10. 17 7月, 2007 2 次提交
  11. 09 7月, 2007 1 次提交
  12. 05 7月, 2007 1 次提交
    • L
      Remove the blink driver · 2bcb1b7d
      Linus Torvalds 提交于
      Yeah, we could have just disabled it, but there's work on a new one that
      isn't as fundamentally broken, so there really doesn't seem to be any
      point in keeping it around.
      
      The recent timer cleanup broke the only valid use, and when I say
      "valid", I obviously mean "totally broken".  So it's not like it works,
      or really even can work in the current format that uses the unsafe
      "panic" LED blinking routines..
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      2bcb1b7d
  13. 10 5月, 2007 1 次提交
  14. 09 5月, 2007 2 次提交
  15. 25 4月, 2007 1 次提交
  16. 22 4月, 2007 1 次提交
  17. 11 4月, 2007 2 次提交
  18. 31 3月, 2007 1 次提交
  19. 26 3月, 2007 1 次提交
  20. 13 2月, 2007 3 次提交
  21. 10 2月, 2007 1 次提交
  22. 30 1月, 2007 3 次提交
  23. 25 10月, 2006 1 次提交
  24. 17 10月, 2006 1 次提交
  25. 14 10月, 2006 1 次提交
  26. 04 10月, 2006 1 次提交
  27. 08 9月, 2005 1 次提交
  28. 01 9月, 2005 1 次提交
  29. 13 7月, 2005 1 次提交
  30. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4