Skip to content

Tags

Tags give the ability to mark specific points in history as being important
  • drm-intel-next-2014-11-21
    - infoframe tracking (for fastboot) from Jesse
    - start of the dri1/ums support removal
    - vlv forcewake timeout fixes (Imre)
    - bunch of patches to polish the rps code (Imre) and improve it on bdw (Tom
      O'Rourke)
    - on-demand pinning for execlist contexts
    - vlv/chv backlight improvements (Ville)
    - gen8+ render ctx w/a work from various people
    - skl edp programming (Satheeshakrishna et al.)
    - psr docbook (Rodrigo)
    - piles of little fixes and improvements all over, as usual
  • devicetree-fixes-for-3.18
    DeviceTree fixes for 3.18:
    - 2 fixes for OF selftest code
    - Fix for PowerPC address parsing to disable work-around except on old
      PowerMACs
    - Fix a crash when earlycon is enabled, but no device is found
    - DT documentation fixes and missing vendor prefixes
    
    All but the doc updates are also for stable.
    
  • v3.12.33
    0bbf78fb · Linux 3.12.33 ·
    This is the 3.12.33 stable release
    
  • mac80211-next-for-john-2014-11-20
    It has been a while since my last pull request, so we accumulated
    another relatively large set of changes:
     * TDLS off-channel support set from Arik/Liad, with some support
       patches I did
     * custom regulatory fixes from Arik
     * minstrel VHT fix (and a small optimisation) from Felix
     * add back radiotap vendor namespace support (myself)
     * random MAC address scanning for cfg80211/mac80211/hwsim (myself)
     * CSA improvements (Luca)
     * WoWLAN Net Detect (wake on network found) support (Luca)
     * and lots of other smaller changes from many people
    
  • sound-3.18-rc6
    sound fixes for 3.18-rc6
    
    This batch ended up as a relatively high volume due to pending
    ASoC fixes.  But most of fixes there are trivial and/or device-
    specific fixes and quirks, so safe to apply.  The only (ASoC)
    core fixes are the DPCM race fix and the machine-driver matching
    fix for componentization.
    
  • sunxi-core-for-3.19
    Allwinner Core Additions for 3.19
    
    This has mostly been about introducing A80 support
    
  • sunxi-dt-for-3.19
    Allwinner Device Tree Changes for 3.19
    
    A lot of things happened during that merge window, but mostly:
      - Preliminary Support for the A80
      - New Boards Support
        + Mele M3
        + Banana Pi
        + Optimus
        + OLinuXino Lime2
      - Device Tree Relicensing to GPLv2/X11 dual license
    
  • sunxi-fixes-for-3.18
    Allwinner fixes for 3.18
    
    A fix for the A31 dma controller that requires the AHB clock to be parented to
    PLL6 in order to operate.
    
  • mac80211-for-john-2014-11-18
    Here's another last minute fix, for minstrel HT crashing
    depending on the value of some uninitialised stack.
    
  • v3.19-meson-soc
    ARM: meson: SOC related changes
  • v3.19-meson-dts
    ARM: meson: DTS related changes
  • asoc-v3.18-rc5
    ASoC: Fixes for v3.18
    
    As well as the usual driver fixes there's a few other things here:
    
    One is a fix for a race in DPCM which is unfortuantely a rather large
    diffstat, this is the result of growing usage of the mainline code and
    hence more detailed testing so I'm relatively happy.
    
    The other is a fix for non-DT machine driver matching following some of
    the componentization work which is much more focused.
    
    Both have had a while to cook in -next.
    
  • drm-intel-fixes-2014-11-19
  • v3.18-rc5
    fc14f9c1 · Linux 3.18-rc5 ·
    Linux 3.18-rc5
    
  • iio-fixes-for-3.18c
    Third set of IIO fixes for the 3.18 cycle.
    
    Most of these are fairly standard little fixes, a bmc150 and bmg160 patch
    is to make an ABI change to indicated a specific axis in an event rather
    than the generic option in the original drivers.  As both of these drivers
    are new in this cycle it would be ideal to push this minor change through
    even though it isn't strictly a fix.  A couple of other 'fixes' change
    defaults for some settings on these new drivers to more intuitive calues.
    Looks like some useful feedback has been coming in for this driver
    since it was applied.
    
    * IIO_EVENT_CODE_EXTRACT_DIR bit mask was wrong and has been for a while
      0xCF clearly doesn't give a contiguous bitmask.
    * kxcjk-1013 range setting was failing to mask out the previous value
      in the register and hence was 'enable only'.
    * men_z188 device id table wasn't null terminated.
    * bmg160 and bmc150 both failed to correctly handling an error in mode
      setting.
    * bmg160 and bmc150 both had a bug in setting the event direction in the
      event spec (leads to an attribute name being incorrect)
    * bmg160 defaulted to an open drain output for the interrupt - as a default
      this obviously only works with some interrupt chips - hence change the
      default to push-pull (note this is a new driver so we aren't going to
      cause any regressions with this change).
    * bmc150 had an unintuitive default for the rate of change (motion detector)
      so change it to 0 (new driver so change of default won't cause any
      regressions).
    
  • v3.17.3
    7623e244 · Linux 3.17.3 ·
    This is the 3.17.3 stable release
    
  • v3.14.24
    9c3da881 · Linux 3.14.24 ·
    This is the 3.14.24 stable release
    
  • v3.10.60
    be701888 · Linux 3.10.60 ·
    This is the 3.10.60 stable release
    
  • pm+acpi-3.18-rc5
    ACPI and power management fixes for 3.18-rc5
    
     - Fix a crash in the suspend-to-idle code path introduced by a
       recent commit that forgot to check a pointer against NULL before
       dereferencing it (Dmitry Eremin-Solenikov).
    
     - Fix a boot crash on Exynos5 introduced by a recent commit making
       that platform use generic Device Tree bindings for power domains
       which exposed a weakness in the generic power domains framework
       leading to that crash (Ulf Hansson).
    
     - Fix a crash during system resume on systems where cpufreq depends
       on Operation Performance Points (OPP) for functionality, but
       CONFIG_OPP is not set.  This leads the cpufreq driver registration
       to fail, but the resume code attempts to restore the pre-suspend
       cpufreq configuration (which does not exist) nevertheless and
       crashes.  From Geert Uytterhoeven.
    
     - Add a new ACPI blacklist entry for Dell Vostro 3546 that has
       problems if it is reported as Windows 8 compatible to the BIOS
       (Adam Lee).
    
     - Fix swapped arguments in an error message in the cpufreq-dt
       driver (Abhilash Kesavan).
    
     - Fix up the prototypes of new callbacks in struct generic_pm_domain
       to make them more useful.  Users of those callbacks will be added
       in 3.19 and it's better for them to be based on the correct struct
       definition in mainline from the start.  From Ulf Hansson and
       Kevin Hilman.
    
    /
    
  • drm-intel-next-2014-11-07-fixups