Skip to content

Tags

Tags give the ability to mark specific points in history as being important
  • v3.11.5
    a145cb95 · Linux 3.11.5 ·
    This is the 3.11.5 stable release
    
  • v3.10.16
    7fc87816 · Linux 3.10.16 ·
    This is the 3.10.16 stable release
    
  • v3.4.66
    dc3a8b0c · Linux 3.4.66 ·
    This is the 3.4.66 stable release
    
  • v3.12-rc5
    61e6cfa8 · Linux 3.12-rc5 ·
    Linux 3.12-rc5
    
  • v3.0.100
    dccc509a · Linux 3.0.100 ·
    This is the 3.0.100 stable release
    
  • pm+acpi-3.12-rc5
    ACPI and power management fixes for 3.12-rc5
    
     - The WARN_ON() in acpiphp_enumerate_slots() triggers as a false
       positive in some cases, so drop it.
    
     - Add a missing pci_dev_put() to an error code path in
       acpiphp_enumerate_slots().
    
     - Replace my old e-mail address that's going to expire with a new one.
    
     - Update ACPI web links and git tree information in MAINTAINERS.
    
     - Update links to the Linux-ACPI project's page in MAINTAINERS.
    
     - Update some stale links and e-mail addresses under Documentation
       and in the ACPI Kconfig file.
    
    /
    
  • v3.12-rc4
    d0e639c9 · Linux 3.12-rc4 ·
    Linux 3.12-rc4
    
  • v3.11.4
    90fec819 · Linux 3.11.4 ·
    This is the 3.11.4 stable release
    
  • v3.10.15
    cac65253 · Linux 3.10.15 ·
    This is the 3.10.15 stable release
    
  • v3.4.65
    5602328b · Linux 3.4.65 ·
    This is the 3.4.65 stable release
    
  • v3.0.99
    5b31202a · Linux 3.0.99 ·
    This is the 3.0.99 stable release
    
  • pm+acpi-3.12-rc4
    726dcbe5 · Merge branch 'pm-fixes' ·
    ACPI and power management fixes for 3.12-rc4
    
     1) The resume part of user space driven hibernation (s2disk) is now
        broken after the change that moved the creation of memory bitmaps
        to after the freezing of tasks, because I forgot that the resume
        utility loaded the image before freezing tasks and needed the
        bitmaps for that.  The fix adds special handling for that case.
    
     2) One of recent commits changed the export of acpi_bus_get_device()
        to EXPORT_SYMBOL_GPL(), which was technically correct but broke
        existing binary modules using that function including one in
        particularly widespread use.  Change it back to EXPORT_SYMBOL().
    
     3) The intel_pstate driver sometimes fails to disable turbo if its
        no_turbo sysfs attribute is set.  Fix from Srinivas Pandruvada.
    
     4) One of recent cpufreq fixes forgot to update a check in cpufreq-cpu0
        which still (incorrectly) treats non-NULL as non-error.  Fix from
        Philipp Zabel.
    
     5) The SPEAr cpufreq driver uses a wrong variable type in one place
        preventing it from catching errors returned by one of the functions
        called by it.  Fix from Sachin Kamat.
    
    /
    
  • iommu-fixes-v3.12-rc3
    IOMMU Fixes for Linux v3.12-rc3
    
    A couple of fixes from the IOMMU side:
    
    	* Some small fixes for the new ARM-SMMU driver
    	* A register offset correction for VT-d
    	* Adding MAINTAINERS entry for drivers/iommu
    
    Overall no really big or intrusive changes.
    
  • v3.11.3
    db203880 · Linux 3.11.3 ·
    This is the 3.11.3 stable release
    
  • v3.10.14
    8c15abc9 · Linux 3.10.14 ·
    This is the 3.10.14 stable release
    
  • v3.4.64
    d4c162c5 · Linux 3.4.64 ·
    This is the 3.4.64 stable release
    
  • v3.0.98
    f45b5c1b · Linux 3.0.98 ·
    This is the 3.0.98 stable release
    
  • v3.12-rc3
    15c03dd4 · Linux 3.12-rc3 ·
    Linux 3.12-rc3
    
  • pm+acpi-3.12-rc3
    ACPI and power management fixes for 3.12-rc3
    
     1) After recent locking changes in the cpufreq core it is possible
        to trigger BUG_ON(!policy) in lock_policy_rwsem_read() if
        cpufreq_get() is called before registering a cpufreq driver.
        Fix from Viresh Kumar.
    
     2) If intel_pstate has been loaded already, it doesn't make sense
        to do anything in acpi_cpufreq_init() and moreover doing something
        in there in that case may be harmful, so make that function return
        immediately if another cpufreq driver is already present.  From
        Yinghai Lu.
    
     3) The ACPI IPMI driver sometimes attempts to acquire a mutex from
        interrupt context, which can be avoided by replacing that mutex
        with a spinlock.  From Lv Zheng.
    
     4) A NULL pointer may be dereferenced by the exynos5440 cpufreq
        driver if a memory allocation made by it fails.  Fix from
        Sachin Kamat.
    
     5) Hanjun Guo's commit fixes a typo in the kerneldoc comment
        documenting acpi_bus_unregister_driver().
    
    /
    
  • fbdev-fixes-3.12
    Small fbdev fixes for various fb drivers