Skip to content

Tags

Tags give the ability to mark specific points in history as being important
  • mfd-gpio-v3.17
    Immutable branch between MFD and GPIO for v3.17.
    
  • pm+acpi-3.16-rc2
    ACPI and power management updates for 3.16-rc2
    
     - Fix for an ia64 regression introduced during the 3.11 cycle by a
       commit that modified the hardware initialization ordering and made
       device discovery fail on some systems.
    
     - Fix for a build problem on systems where the cpufreq-cpu0 driver
       is built-in and the cpu-thermal driver is modular from Arnd Bergmann.
    
     - Fix for a recently introduced computational mistake in the
       intel_pstate driver that leads to excessive rounding errors from
       Doug Smythies.
    
     - Fix for a failure code path in cpufreq_update_policy() that fails
       to unlock the locks acquired previously from Aaron Plattner.
    
     - Fix for the cpuidle mvebu driver to use shorter state names which
       will prevent the sysfs interface from returning mangled strings.
       From Gregory Clement.
    
     - ACPI LPSS driver fix to make sure that the I2C controllers
       included in BayTrail SoCs are not held in the reset state while
       they are being probed from Mika Westerberg.
    
     - New kernel command line arguments making it possible to build
       kernel images with hibernation and kASLR included at the same
       time and to select which of them will be used via the command
       line (they are still functionally mutually exclusive, though).
       From Kees Cook.
    
     - ACPI battery driver quirk for Acer Aspire V5-573G that fails
       to send battery status change notifications timely from
       Alexander Mezin.
    
     - Two ACPI core cleanups from Christoph Jaeger and Fabian Frederick.
    
    /
    
  • topic/core-stuff-2014-06-30
  • v2.6.32.63
    02560982 · Linux 2.6.32.63 ·
    This is the 2.6.32.63 stable release
    
  • iio-for-3.17a
    First round of new drivers, cleanups and functionality for the 3.17 cycle.
    
    New drivers
    * t5403 barometric pressure sensor
    * kxcjk1013 accelerometer (with a locking followup fix).
    * ak09911 digital compass
    
    Documentation
    * ABI docs for proximity added (interface has been there a long time but
      somehow snuck through without being documented)
    * Move iio-trig-sysfs documentation out of staging (got left behind when
      the driver moved some time ago).
    
    Cleanups
     * drop the timestamp argument from iio_trigger_poll(_chained) as
       nothing has been done with it for some time.
     * ad799x kerneldoc for ad799x_chip brought up to date.
     * replace a number of reimplementations of the GENMASK macro and
       use the BIT macro to cleanup a few locations.
     * bring the iio_event_monitor example program up to date with new
       device types.
     * fix some incorrect function prototypes in iio_utils.h example code.
     * INDIO_RING_TRIGGERED to INDIO_BUFFER_TRIGGERED fix in docs. This
       got left behind after we renamed it a long time back.
     * fix error handling in the generic_buffer example program.
     * small tidy ups in the iio-trig-periodic-rtc driver.
     * Allow reseting iio-trig-periodic-rtc frequency to 0 (default) after
       it has changed.
     * Trivial tidy ups in coding style in iio_simply_dummy
    
  • sound-3.16-rc2
    sound fixes for 3.16-rc2
    
    The significant part here is a few security fixes for ALSA core
    control API by Lars.  Besides that, there are a few fixes for ASoC
    sigmadsp (again by Lars) for building properly, and small fixes for
    ASoC rsnd, MMP, PXA and FSL, in addition to a fix for bogus WARNING in
    i915/HD-audio binding.
    
  • dt-fixes-for-3.16
    - Fix microblaze compiling due to conflicting merge window changes
    - A fix in of_attach_node due to of_find_node_by_path changes
    - Prevent format strings in DT kobject names
    
  • mfd-extcon-regulator-v3.17
    Immutable branch between MFD, Extcon and Regulator due for v3.17
    
  • regulator-v3.16-rc1
    regulator: Fixes for v3.16
    
    A few small fixes:
    
     - Fixes for bugs in Palmas and as3722 exposed by recent changes in the
       core - the drivers weren't allowing the current configuration to be
       read sometimes.
     - Provide a stub for regulator_can_change_voltage() for !REGULATOR.
     - Make sure ltc3589 only looks at its child nodes in the device tree
       rather than searching the whole tree.
    
  • asoc-v3.16-rc1
    ASoC: Fixes for v3.16
    
    Quite a few build coverage fixes in here among the usual small driver
    fixes includling the sigmadsp change from Lars - moving the driver to
    separate modules per bus (which is basically just code motion) avoids
    issues with some combinations of buses being enabled.
    
  • v3.4.94
    95f3bb9b · Linux 3.4.94 ·
    This is the 3.4.94 stable release
    
  • v3.15.1
    41b67d8f · Linux 3.15.1 ·
    This is the 3.15.1 stable release
    
  • v3.10.44
    73eabc6d · Linux 3.10.44 ·
    This is the 3.10.44 stable release
    
  • v3.14.8
    0c5b3b80 · Linux 3.14.8 ·
    This is the 3.14.8 stable release
    
  • v3.16-rc1
    7171511e · Linux 3.16-rc1 ·
    Linux 3.16-rc1
    
  • iio-fixes-for-3.16a
    First set of IIO fixes for the 3.16 cycle.
    
    A mixed bag of fixes, many of which feel just to late for 3.15.
    
    * hid sensors - some devices need a feature report request in order to
      change power state.  This isn't part of the spec, but has been observed
      on several devices and does no harm to others.
    * mpl3115 has had two errors in the buffer description fixed. The presure is
      signed, not unsigned and the temperature has 12 bits rather than 16.
      These could lead to incorrect interpretation of the data in userspace.
    * tsl2x7x - the high byte of the proximity thresholds should be written along
      with the low byte (which was). This could lead to interesting results
      with large thresholds.
    * twl4030 - a flag to specify processed values were required was not set
      when initializing a reading.  As such values returned were in an unknown
      state. Fixed by simply initializing it appropriately.
    * IIO_SIMPLE_DUMMY_BUFFER did not select IIO_BUFFER leading to randconfig
      build errors.
    * ak8975 was applying an unwanted le16_to_cpu conversion as the i2c framework
      already performs one.  As such for big endian systems, the bytes would be
      in the wrong order in the magnetic field measurements reported.
    * mxs-lradc - the controllable voltage dividers were not enabled / disabled for
      later channels than the first one during conversion.
    * at91_adc error handling returned -ENOMEM in a u8. Return value of
      at91_adc_get_trigger_value_by_name changed to int thus allowing -ENOMEM and
      also original values to be returned.
    * mcb - mcb_request_mem returns and ERR_PTR but the caller was checking for
      NULL to detect an error.
    
  • gpio-v3.16-2
    A first GPIO fix for the v3.16 series, this was serious since
    it blocks the OMAP boot.
    
  • sound-fix-3.16-rc1
    sound fixes for 3.16-rc1
    
    Most of changes are small and easy cleanup or fixes.
    
    - a few HD-audio Realtek codec fixes and quirks
    - Intel HDMI audio fixes for Broadwell and Haswell / ValleyView
    - FireWire sound stack cleanups
    - a couple of sequencer core fixes
    - compress ABI fix for 64bit
    - Conversion to modern ktime*() API
    
  • drm-intel-fixes-2014-06-17
  • pm+acpi-3.16-rc1-2
    d715a226 · Merge branch 'pm-sleep' ·
    More ACPI and power management updates for 3.16-rc1
    
     - I didn't remember correctly that the Hans de Goede's ACPI video
       patches actually didn't flip the video.use_native_backlight
       default, although we had discussed that and decided to do that.
       Since I said we would do that in the previous PM+ACPI pull
       request, make that change for real now.
    
     - ACPI bus check notifications for PCI host bridges don't cause
       the bus below the host bridge to be checked for changes as they
       should because of a mistake in the ACPI-based PCI hotplug (ACPIPHP)
       subsystem that forgets to add hotplug contexts to PCI host bridge
       ACPI device objects.  Create hotplug contexts for PCI host bridges
       too as appropriate.
    
     - Revert recent cpufreq commit related to the big.LITTLE cpufreq
       driver that breaks arm64 builds.
    
     - Fix for a regression in the ppc-corenet cpufreq driver introduced
       during the 3.15 cycle and causing the driver to use the remainder
       from do_div instead of the quotient.  From Ed Swarthout.
    
     - Resets triggered by panic activate a BUG_ON() in vmalloc.c on
       systems where the ACPI reset register is located in memory address
       space.  Fix from Randy Wright.
    
     - Fix for a problem with cpufreq governors that decisions made by
       them may be suboptimal due to the fact that deferrable timers are
       used by them for CPU load sampling.  From Srivatsa S Bhat.
    
     - Fix for a problem with the Tegra cpufreq driver where the CPU
       frequency is temporarily switched to a "stable" level that
       is different from both the initial and target frequencies
       during transitions which causes udelay() to expire earlier than
       it should sometimes.  From Viresh Kumar.
    
     - New trace points and rework of some existing trace points for
       system suspend/resume profiling from Todd Brandt.
    
     - Assorted cpufreq fixes and cleanups from Stratos Karafotis and
       Viresh Kumar.
    
     - Copyright notice update for suspend-and-cpuhotplug.txt from
       Srivatsa S Bhat.
    
    /