January 2016 Archives by subject
Starting: Fri Jan 1 02:33:36 UTC 2016
Ending: Sun Jan 31 22:45:25 UTC 2016
Messages: 219
- [lsk-v3.14-android] linaro-android-3.14 topic branch updates for 16.01
Amit Pundir
- [lsk-v3.18-android] linaro-android-3.18 topic branch updates for 16.01
Amit Pundir
- [lsk-v4.1-android] linaro-android-4.1 topic branch updates for 16.01
Amit Pundir
- [PATCH 00/17] PM / OPP: Introduce APIs to transition OPPs
Viresh Kumar
- [PATCH 01/17] PM / OPP: get/put regulators from OPP core
Stephen Boyd
- [PATCH 01/17] PM / OPP: get/put regulators from OPP core
Viresh Kumar
- [PATCH 01/17] PM / OPP: get/put regulators from OPP core
Viresh Kumar
- [PATCH 01/17] PM / OPP: get/put regulators from OPP core
Stephen Boyd
- [PATCH 02/17] PM / OPP: Add APIs to set regulator-name
Stephen Boyd
- [PATCH 02/17] PM / OPP: Add APIs to set regulator-name
Viresh Kumar
- [PATCH 03/17] PM / OPP: Disable OPPs that aren't supported by the regulator
Stephen Boyd
- [PATCH 04/17] PM / OPP: Introduce dev_pm_opp_get_max_volt_latency()
Stephen Boyd
- [PATCH 04/17] PM / OPP: Introduce dev_pm_opp_get_max_volt_latency()
Viresh Kumar
- [PATCH 04/17] PM / OPP: Introduce dev_pm_opp_get_max_volt_latency()
Stephen Boyd
- [PATCH 04/17] PM / OPP: Introduce dev_pm_opp_get_max_volt_latency()
Viresh Kumar
- [PATCH 04/17] PM / OPP: Introduce dev_pm_opp_get_max_volt_latency()
Viresh Kumar
- [PATCH 04/17] PM / OPP: Introduce dev_pm_opp_get_max_volt_latency()
Stephen Boyd
- [PATCH 04/17] PM / OPP: Introduce dev_pm_opp_get_max_volt_latency()
Viresh Kumar
- [PATCH 04/17] PM / OPP: Introduce dev_pm_opp_get_max_volt_latency()
Stephen Boyd
- [PATCH 05/17] PM / OPP: Introduce dev_pm_opp_get_max_transition_latency()
Stephen Boyd
- [PATCH 06/17] PM / OPP: Parse clock-latency and voltage-tolerance for v1 bindings
Stephen Boyd
- [PATCH 06/17] PM / OPP: Parse clock-latency and voltage-tolerance for v1 bindings
Viresh Kumar
- [PATCH 06/17] PM / OPP: Parse clock-latency and voltage-tolerance for v1 bindings
Stephen Boyd
- [PATCH 06/17] PM / OPP: Parse clock-latency and voltage-tolerance for v1 bindings
Viresh Kumar
- [PATCH 06/17] PM / OPP: Parse clock-latency and voltage-tolerance for v1 bindings
Stephen Boyd
- [PATCH 06/17] PM / OPP: Parse clock-latency and voltage-tolerance for v1 bindings
Stephen Boyd
- [PATCH 07/17] PM / OPP: Manage device clk
Stephen Boyd
- [PATCH 07/17] PM / OPP: Manage device clk
Viresh Kumar
- [PATCH 07/17] PM / OPP: Manage device clk
Stephen Boyd
- [PATCH 08/17] PM / OPP: Add dev_pm_opp_set_rate()
Stephen Boyd
- [PATCH 08/17] PM / OPP: Add dev_pm_opp_set_rate()
Viresh Kumar
- [PATCH 08/17] PM / OPP: Add dev_pm_opp_set_rate()
Stephen Boyd
- [PATCH 08/17] PM / OPP: Add dev_pm_opp_set_rate()
Viresh Kumar
- [PATCH 09/17] cpufreq: dt: Convert few pr_debug/err() calls to dev_dbg/err()
Stephen Boyd
- [PATCH 10/17] cpufreq: dt: Rename 'need_update' to 'opp_v1'
Stephen Boyd
- [PATCH 11/17] cpufreq: dt: OPP layers handles clock-latency for V1 bindings as well
Stephen Boyd
- [PATCH 12/17] cpufreq: dt: Pass regulator name to the OPP core for V1 bindings
Stephen Boyd
- [PATCH 12/17] cpufreq: dt: Pass regulator name to the OPP core for V1 bindings
Viresh Kumar
- [PATCH 12/17] cpufreq: dt: Pass regulator name to the OPP core for V1 bindings
Stephen Boyd
- [PATCH 12/17] cpufreq: dt: Pass regulator name to the OPP core for V1 bindings
Viresh Kumar
- [PATCH 12/17] cpufreq: dt: Pass regulator name to the OPP core for V1 bindings
Mark Brown
- [PATCH 13/17] cpufreq: dt: Unsupported OPPs are already disabled
Stephen Boyd
- [PATCH 14/17] cpufreq: dt: Reuse dev_pm_opp_get_max_transition_latency()
Stephen Boyd
- [PATCH 15/17] cpufreq: dt: Use dev_pm_opp_set_rate() to switch frequency
Stephen Boyd
- [PATCH 16/17] cpufreq: dt: drop references to DT node
Stephen Boyd
- [PATCH 17/17] cpufreq: dt: No need to allocate resources anymore
Stephen Boyd
- [PATCH 17/17] cpufreq: dt: No need to allocate resources anymore
Viresh Kumar
- [PATCH 17/17] cpufreq: dt: No need to allocate resources anymore
Stephen Boyd
- [PATCH 17/17] cpufreq: dt: No need to allocate resources anymore
Viresh Kumar
- [PATCH 17/17] cpufreq: dt: No need to allocate resources anymore
Stephen Boyd
- [PATCH 17/17] cpufreq: dt: No need to allocate resources anymore
Viresh Kumar
- [PATCH 4.4-rc5 v22 1/4] irqchip: gic: Optimize locking in gic_raise_softirq
Marc Zyngier
- [PATCH 4.4-rc5 v22 2/4] irqchip: gic: Make gic_raise_softirq FIQ-safe
Marc Zyngier
- [PATCH 4.4-rc5 v22 3/4] irqchip: gic: Introduce plumbing for IPI FIQ
Marc Zyngier
- [PATCH 4.4-rc5 v22 3/4] irqchip: gic: Introduce plumbing for IPI FIQ
Daniel Thompson
- [PATCH 4.4-rc5 v22 4/4] ARM: Allow IPI_CPU_BACKTRACE to exploit FIQ
Daniel Thompson
- [PATCH 4.4-rc5 v22 4/4] ARM: Allow IPI_CPU_BACKTRACE to exploit FIQ
Daniel Thompson
- [PATCH] arm64: reenable interrupt when handling ptrace breakpoint
Shi, Yang
- [PATCH] arm64: reenable interrupt when handling ptrace breakpoint
Will Deacon
- [PATCH] arm64: reenable interrupt when handling ptrace breakpoint
Shi, Yang
- [PATCH] arm64: reenable interrupt when handling ptrace breakpoint
Will Deacon
- [PATCH] arm64: reenable interrupt when handling ptrace breakpoint
Shi, Yang
- [PATCH] cpufreq: Fix NULL reference crash while accessing policy->governor_data
Viresh Kumar
- [PATCH] cpufreq: Fix NULL reference crash while accessing policy->governor_data
Juri Lelli
- [PATCH] cpufreq: Fix NULL reference crash while accessing policy->governor_data
Juri Lelli
- [PATCH] cpufreq: Fix NULL reference crash while accessing policy->governor_data
Rafael J. Wysocki
- [PATCH] cpufreq: Fix NULL reference crash while accessing policy->governor_data
Viresh Kumar
- [PATCH] cpufreq: Fix NULL reference crash while accessing policy->governor_data
Viresh Kumar
- [PATCH] cpufreq: Fix NULL reference crash while accessing policy->governor_data
Juri Lelli
- [PATCH] cpufreq: Fix NULL reference crash while accessing policy->governor_data
Juri Lelli
- [PATCH] cpufreq: Fix NULL reference crash while accessing policy->governor_data
Rafael J. Wysocki
- [PATCH] cpufreq: Fix NULL reference crash while accessing policy->governor_data
Viresh Kumar
- [PATCH] cpufreq: Fix NULL reference crash while accessing policy->governor_data
Juri Lelli
- [PATCH] cpufreq: Fix NULL reference crash while accessing policy->governor_data
Rafael J. Wysocki
- [PATCH] kgdb: disable do_fork and sys_open tests on boot when DEBUG_RODATA is enabled
Yang Shi
- [PATCH] PCI: layerscape: add ls2085a compatible
Yang Shi
- [PATCH] PCI: layerscape: add ls2085a compatible
Shi, Yang
- [PATCH] PM / OPP: Use snprintf() instead of sprintf()
Viresh Kumar
- [PATCH] PM / OPP: Use snprintf() instead of sprintf()
Geert Uytterhoeven
- [PATCH] PM / OPP: Use snprintf() instead of sprintf()
Stephen Boyd
- [PATCH] PM / OPP: Use snprintf() instead of sprintf()
Rafael J. Wysocki
- [PATCH] ppc64: select HAVE_CONTEXT_TRACKING by default
Shi, Yang
- [PATCH V2 00/16] PM / OPP: Introduce APIs to transition OPPs
Viresh Kumar
- [PATCH V2 00/16] PM / OPP: Introduce APIs to transition OPPs
Stephen Boyd
- [PATCH V2 01/16] PM / OPP: get/put regulators from OPP core
Viresh Kumar
- [PATCH V2 02/16] PM / OPP: Disable OPPs that aren't supported by the regulator
Viresh Kumar
- [PATCH V2 03/16] PM / OPP: Introduce dev_pm_opp_get_max_volt_latency()
Viresh Kumar
- [PATCH V2 04/16] PM / OPP: Introduce dev_pm_opp_get_max_transition_latency()
Viresh Kumar
- [PATCH V2 05/16] PM / OPP: Parse clock-latency and voltage-tolerance for v1 bindings
Viresh Kumar
- [PATCH V2 06/16] PM / OPP: Manage device clk
Viresh Kumar
- [PATCH V2 07/16] PM / OPP: Add dev_pm_opp_set_rate()
Viresh Kumar
- [PATCH V2 08/16] cpufreq: dt: Convert few pr_debug/err() calls to dev_dbg/err()
Viresh Kumar
- [PATCH V2 09/16] cpufreq: dt: Rename 'need_update' to 'opp_v1'
Viresh Kumar
- [PATCH V2 10/16] cpufreq: dt: OPP layers handles clock-latency for V1 bindings as well
Viresh Kumar
- [PATCH V2 11/16] cpufreq: dt: Pass regulator name to the OPP core
Viresh Kumar
- [PATCH V2 12/16] cpufreq: dt: Unsupported OPPs are already disabled
Viresh Kumar
- [PATCH V2 13/16] cpufreq: dt: Reuse dev_pm_opp_get_max_transition_latency()
Viresh Kumar
- [PATCH V2 14/16] cpufreq: dt: Use dev_pm_opp_set_rate() to switch frequency
Viresh Kumar
- [PATCH V2 15/16] cpufreq: dt: drop references to DT node
Viresh Kumar
- [PATCH V2 16/16] cpufreq: dt: No need to allocate resources anymore
Viresh Kumar
- [PATCH v2 3/3] ARM64: dts: mt8173: Add CPU OPP, clock and regulator supply properties
Arnd Bergmann
- [PATCH v2 3/3] ARM64: dts: mt8173: Add CPU OPP, clock and regulator supply properties
Viresh Kumar
- [PATCH v2] PM / OPP: Fix parsing of opp-microvolt and opp-microamp properties
Rafael J. Wysocki
- [PATCH v2] PM/OPP: Set cpu_dev->id in cpumask first
Rafael J. Wysocki
- [PATCH V3 2/2] PM / OPP: Parse 'opp-<prop>-<name>' bindings
Geert Uytterhoeven
- [PATCH V3 2/2] PM / OPP: Parse 'opp-<prop>-<name>' bindings
Viresh Kumar
- [PATCH v5 3/7] x86: mm/gup: add gup trace points
Shi, Yang
- [PATCH v5 5/7] s390: mm/gup: add gup trace points
Shi, Yang
- [PATCH v5 5/7] s390: mm/gup: add gup trace points
Heiko Carstens
- [PATCH v5 7/7] sparc64: mm/gup: add gup trace points
Shi, Yang
- [PATCH v5 7/7] sparc64: mm/gup: add gup trace points
David Miller
- [PATCH v5 7/7] sparc64: mm/gup: add gup trace points
Steven Rostedt
- [PATCH v6] clk: mediatek: Export CPU mux clocks for CPU frequency control
Daniel Kurtz
- [RFC V5] Add gup trace points support
Shi, Yang
- [RFC V5] Add gup trace points support
Steven Rostedt
- [RFC V5] Add gup trace points support
Shi, Yang
- [RFC V5] Add gup trace points support
Steven Rostedt
- master build: 0 failures 5 warnings (v4.4-10019-g9638685)
Build bot for Mark Brown
- master build: 0 failures 5 warnings (v4.4-10062-g30f0530)
Build bot for Mark Brown
- master build: 0 failures 5 warnings (v4.4-10172-ge9f57eb)
Build bot for Mark Brown
- master build: 0 failures 5 warnings (v4.4-10286-g404a474)
Build bot for Mark Brown
- master build: 0 failures 5 warnings (v4.4-10454-g3e1e21c)
Build bot for Mark Brown
- master build: 0 failures 5 warnings (v4.4-10513-g2101ae4)
Build bot for Mark Brown
- master build: 0 failures 5 warnings (v4.4-10559-g2c9b3eb)
Build bot for Mark Brown
- master build: 0 failures 5 warnings (v4.4-10691-gb82dde0)
Build bot for Mark Brown
- master build: 0 failures 5 warnings (v4.4-10714-gcc67375)
Build bot for Mark Brown
- master build: 0 failures 5 warnings (v4.4-8810-gd05d82f)
Build bot for Mark Brown
- master build: 0 failures 5 warnings (v4.4-8855-ga200dcb)
Build bot for Mark Brown
- master build: 0 failures 5 warnings (v4.4-8904-g99e38df)
Build bot for Mark Brown
- master build: 0 failures 5 warnings (v4.4-8917-g7c24d9f)
Build bot for Mark Brown
- master build: 0 failures 5 warnings (v4.4-8950-g2b4015e)
Build bot for Mark Brown
- master build: 0 failures 5 warnings (v4.4-8984-g9fa6860)
Build bot for Mark Brown
- master build: 0 failures 6 warnings (v4.4-1175-g03891f9)
Build bot for Mark Brown
- master build: 0 failures 6 warnings (v4.4-1441-g4f31d77)
Build bot for Mark Brown
- master build: 0 failures 6 warnings (v4.4-947-g2c48712)
Build bot for Mark Brown
- master build: 0 failures 6 warnings (v4.5-rc1-179-gad0b40fa)
Build bot for Mark Brown
- master build: 0 failures 7 warnings (v4.4-10721-gb3e27d5)
Build bot for Mark Brown
- master build: 0 failures 7 warnings (v4.4-10893-g048ccca)
Build bot for Mark Brown
- master build: 0 failures 7 warnings (v4.4-10894-g587198b)
Build bot for Mark Brown
- master build: 0 failures 7 warnings (v4.4-1561-g60b7eca)
Build bot for Mark Brown
- master build: 0 failures 7 warnings (v4.4-3408-g6799060)
Build bot for Mark Brown
- master build: 0 failures 7 warnings (v4.4-8606-g5807fca)
Build bot for Mark Brown
- master build: 0 failures 7 warnings (v4.5-rc1-104-gf51d4d7)
Build bot for Mark Brown
- master build: 0 failures 7 warnings (v4.5-rc1-23-g075356c)
Build bot for Mark Brown
- master build: 0 failures 7 warnings (v4.5-rc1-28-g03c21cb)
Build bot for Mark Brown
- master build: 0 failures 7 warnings (v4.5-rc1-32-g26cd836)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-30-gddf1d62)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-432-gaf34520)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-5210-g77a76b0)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-5270-gcbd88cd)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-5593-g7fdec82)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-5820-g10a0c0f)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-5966-g7d1fc01)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-8548-g9840650)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-rc7-74-g7c672dd)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-rc7-76-g9c982e8)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-rc7-81-g4294616)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-rc8-101-geac6f76)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-rc8-22-g51cb67c)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-rc8-26-gb06f3a1)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-rc8-28-g2626820)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-rc8-36-g02006f7a)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-rc8-49-g4054f64)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-rc8-5-gee9a7d2)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-rc8-83-g650e545)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-rc8-95-g44d8a7d)
Build bot for Mark Brown
- master build: 0 failures 8 warnings (v4.4-rc8-96-g751e5f5)
Build bot for Mark Brown
- master build: 0 failures 9 warnings (v4.4-6383-g4e5448a)
Build bot for Mark Brown
- master build: 0 failures 9 warnings (v4.4-6534-gece6267)
Build bot for Mark Brown
- next-20160104 build: 3 failures 15 warnings (next-20160104)
Build bot for Mark Brown
- next-20160104 build: 3 failures 15 warnings (next-20160104)
Mark Brown
- next-20160104 build: 3 failures 15 warnings (next-20160104)
Mark Brown
- next-20160104 build: 3 failures 15 warnings (next-20160104)
Arnd Bergmann
- next-20160104 build: 3 failures 15 warnings (next-20160104)
Mark Brown
- next-20160104 build: 3 failures 15 warnings (next-20160104)
Rafael J. Wysocki
- next-20160105 build: 4 failures 16 warnings (next-20160105)
Build bot for Mark Brown
- next-20160106 build: 0 failures 13 warnings (next-20160106)
Build bot for Mark Brown
- next-20160107 build: 0 failures 9 warnings (next-20160107)
Build bot for Mark Brown
- next-20160108 build: 0 failures 9 warnings (next-20160108)
Build bot for Mark Brown
- next-20160111 build: 2 failures 11 warnings (next-20160111)
Build bot for Mark Brown
- next-20160111 build: 2 failures 11 warnings (next-20160111)
Paul Gortmaker
- next-20160111 build: 2 failures 11 warnings (next-20160111)
Bayyavarapu, Maruthi
- next-20160112 build: 1 failures 6 warnings (next-20160112)
Build bot for Mark Brown
- next-20160113 build: 0 failures 6 warnings (next-20160113)
Build bot for Mark Brown
- next-20160114 build: 0 failures 6 warnings (next-20160114)
Build bot for Mark Brown
- next-20160115 build: 0 failures 6 warnings (next-20160115)
Build bot for Mark Brown
- next-20160118 build: 0 failures 7 warnings (next-20160118)
Build bot for Mark Brown
- next-20160119 build: 0 failures 6 warnings (next-20160119)
Build bot for Mark Brown
- next-20160120 build: 0 failures 5 warnings (next-20160120)
Build bot for Mark Brown
- next-20160121 build: 0 failures 5 warnings (next-20160121)
Build bot for Mark Brown
- next-20160122 build: 0 failures 6 warnings (next-20160122)
Build bot for Mark Brown
- next-20160125 build: 0 failures 7 warnings (next-20160125)
Build bot for Mark Brown
- next-20160127 build: 0 failures 9 warnings (next-20160127)
Build bot for Mark Brown
- next-20160128 build: 4 failures 9 warnings (next-20160128)
Build bot for Mark Brown
- next-20160128 build: 4 failures 9 warnings (next-20160128)
Mark Brown
- next-20160129 build: 0 failures 10 warnings (next-20160129)
Build bot for Mark Brown
- v3.10.94-rt102 build: 0 failures 83 warnings (v3.10.94-rt102)
Build bot for Mark Brown
- v3.10.95 build: 0 failures 78 warnings (v3.10.95)
Build bot for Mark Brown
- v3.10.96 build: 0 failures 77 warnings (v3.10.96)
Build bot for Mark Brown
- v3.12.52-rt70 build: 0 failures 69 warnings (v3.12.52-rt70)
Build bot for Mark Brown
- v3.12.52 build: 0 failures 66 warnings (v3.12.52)
Build bot for Mark Brown
- v3.12.53 build: 0 failures 66 warnings (v3.12.53)
Build bot for Mark Brown
- v3.14.58-rt59 build: 0 failures 66 warnings (v3.14.58-rt59)
Build bot for Mark Brown
- v3.14.59 build: 0 failures 62 warnings (v3.14.59)
Build bot for Mark Brown
- v3.14.60 build: 0 failures 62 warnings (v3.14.60)
Build bot for Mark Brown
- v3.18-rt build: 0 failures 39 warnings (v3.18.24-rt22-137-g90a3d74)
Build bot for Mark Brown
- v3.18.25-rt23 build: 0 failures 39 warnings (v3.18.25-rt23)
Build bot for Mark Brown
- v3.18.26 build: 0 failures 35 warnings (v3.18.26)
Build bot for Mark Brown
- v3.2.75-rt108 build: 2 failures 45 warnings (v3.2.75-rt108)
Build bot for Mark Brown
- v3.2.76 build: 2 failures 32 warnings (v3.2.76)
Build bot for Mark Brown
- v3.4.110 build: 2 failures 29 warnings (v3.4.110)
Build bot for Mark Brown
- v4.1.16 build: 0 failures 26 warnings (v4.1.16)
Build bot for Mark Brown
- v4.1.17 build: 0 failures 26 warnings (v4.1.17)
Build bot for Mark Brown
- v4.2.8 build: 0 failures 70 warnings (v4.2.8)
Build bot for Mark Brown
- v4.3.4 build: 0 failures 47 warnings (v4.3.4)
Build bot for Mark Brown
- v4.4-rc8 build: 0 failures 8 warnings (v4.4-rc8)
Build bot for Mark Brown
- v4.4 build: 0 failures 8 warnings (v4.4)
Build bot for Mark Brown
- v4.4 build: 0 failures 8 warnings (v4.4)
Build bot for Mark Brown
- v4.5-rc1 build: 0 failures 7 warnings (v4.5-rc1)
Build bot for Mark Brown
Last message date:
Sun Jan 31 22:45:25 UTC 2016
Archived on: Sun Jan 31 22:45:42 UTC 2016
This archive was generated by
Pipermail 0.09 (Mailman edition).