Hello Paul,
On Wed, Jul 22, 2015 at 3:13 AM, Paul Gortmaker
paul.gortma...@windriver.com wrote:
[Re: [PATCH 2/3] mfd: Remove MFD_CROS_EC depends on X86 || ARM] On 25/06/2015
(Thu 10:44) Javier Martinez Canillas wrote:
Hello Lee,
On 06/25/2015 10:38 AM, Lee Jones wrote:
On Thu, 25 Jun
On 2015년 07월 22일 11:02, Joonyoung Shim wrote:
On 07/21/2015 10:19 PM, Krzysztof Kozlowski wrote:
Hi,
Today's linux-next (next-20150721) encounters boot failures on Exynos
Octa (Exynos5422) based boards. The boards hangs. I bisected it to:
d80167b85024982c5f18d0481a5c248100360118
On 07/21/2015 10:19 PM, Krzysztof Kozlowski wrote:
Hi,
Today's linux-next (next-20150721) encounters boot failures on Exynos
Octa (Exynos5422) based boards. The boards hangs. I bisected it to:
d80167b85024982c5f18d0481a5c248100360118 is the first bad commit
commit
On Tue, Jul 21, 2015 at 10:14:11AM +0200, Michal Suchanek wrote:
Or alternatively we could publish the limitations of the channel using
capabilities so SPI knows I have a dmaengine channel and it can transfer
max N
length transfers so would be able to break rather than guessing it or
On Thu, Jun 25, 2015 at 02:20:42AM +0200, Javier Martinez Canillas wrote:
The Chrome platform support depends on X86 || ARM because there are
only Chromebooks using those architectures. But only some drivers
depend on a given architecture, and the ones that do already have
a dependency on
On Tue, Jul 21, 2015 at 6:13 PM, Paul Gortmaker
paul.gortma...@windriver.com wrote:
[Re: [PATCH 2/3] mfd: Remove MFD_CROS_EC depends on X86 || ARM] On 25/06/2015
(Thu 10:44) Javier Martinez Canillas wrote:
Hello Lee,
On 06/25/2015 10:38 AM, Lee Jones wrote:
On Thu, 25 Jun 2015, Javier
On Thu, Jun 25, 2015 at 10:44:28AM +0200, Javier Martinez Canillas wrote:
Hello Lee,
On 06/25/2015 10:38 AM, Lee Jones wrote:
On Thu, 25 Jun 2015, Javier Martinez Canillas wrote:
A dependency on X86 || ARM for MFD_CROS_EC was added to fix the warning:
(MFD_CROS_EC) selects
[Re: [PATCH 2/3] mfd: Remove MFD_CROS_EC depends on X86 || ARM] On 25/06/2015
(Thu 10:44) Javier Martinez Canillas wrote:
Hello Lee,
On 06/25/2015 10:38 AM, Lee Jones wrote:
On Thu, 25 Jun 2015, Javier Martinez Canillas wrote:
A dependency on X86 || ARM for MFD_CROS_EC was added to
On Sat 18-07-15 12:14:12, Inki Dae wrote:
On 2015년 07월 17일 19:31, Hans Verkuil wrote:
On 07/17/2015 12:29 PM, Inki Dae wrote:
On 2015년 07월 17일 19:20, Hans Verkuil wrote:
On 07/13/2015 04:55 PM, Jan Kara wrote:
From: Jan Kara j...@suse.cz
Convert g2d_userptr_get_dma_addr() to pin pages
Hi Kukjin,
On Tue, Jul 21, 2015 at 12:40:04PM +0900, Kukjin Kim wrote:
Hi,
Please pull samsung fixes for v4.2.
Thanks,
Kukjin
The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
are available in the git
On 06/12, Krzysztof Kozlowski wrote:
The TSADC gate clock was used in Exynos4x12 DTSI for exynos-adc driver.
However TSADC is present only on Exynos4210 so on Trats2 board (with
Exynos4412 SoC) the exynos-adc driver could not be probed:
ERROR: could not get clock /adc@126C:adc(0)
On 22.07.2015 07:42, Stephen Boyd wrote:
On 06/12, Krzysztof Kozlowski wrote:
The TSADC gate clock was used in Exynos4x12 DTSI for exynos-adc driver.
However TSADC is present only on Exynos4210 so on Trats2 board (with
Exynos4412 SoC) the exynos-adc driver could not be probed:
ERROR: could
On 21.07.2015 14:21, Krzysztof Kozlowski wrote:
2015-07-21 14:13 GMT+09:00 Krzysztof Kozlowski k.kozlow...@samsung.com:
2015-07-21 14:02 GMT+09:00 Kukjin Kim kg...@kernel.org:
Krzysztof Kozlowski wrote:
Dear Kukjin,
Exynos mach-code related improvements. Description along with a tag.
You
Hello,
On 21 July 2015 at 06:29, Vinod Koul vinod.k...@intel.com wrote:
On Sun, Jul 19, 2015 at 09:01:34PM +0200, Michal Suchanek wrote:
Hello,
On 15 July 2015 at 17:59, Brian Norris computersforpe...@gmail.com wrote:
Hi Michal,
On Wed, Jul 15, 2015 at 01:52:27PM +0200, Marek Vasut
Hi Punit,
On Fri, Jul 17, 2015 at 12:14:36PM +0100, Punit Agrawal wrote:
Hi Sascha,
Sascha Hauer s.ha...@pengutronix.de writes:
The thermal code uses int, long and unsigned long for temperatures
in different places.
Using an unsigned type limits the thermal framework to positive
Hi Sascha,
Sascha Hauer s.ha...@pengutronix.de writes:
The thermal code uses int, long and unsigned long for temperatures
in different places.
Using an unsigned type limits the thermal framework to positive
temperatures without need. Also several drivers currently will report
temperatures
Hi,
Today's linux-next (next-20150721) encounters boot failures on Exynos
Octa (Exynos5422) based boards. The boards hangs. I bisected it to:
d80167b85024982c5f18d0481a5c248100360118 is the first bad commit
commit d80167b85024982c5f18d0481a5c248100360118
Author: Joonyoung Shim jy0922.s
17 matches
Mail list logo
